Java Code One Task Group

This documentation was generated with the assistance of AI. Please report any inaccuracies.

Implement one bucket of Java tasks from a plan’s task group end to end: capture a single pre-change quality baseline, run iru-java-code-one-task once per task (in parallel when the group allows it), then validate the entire bucket once — license headers, Javadoc, scoped tests, coverage, a full-suite run, and a code-quality regression check.

Purpose

iru-java-code-one-task-group is where this catalog’s per-task validation cost was consolidated to once per group. It captures one pre-change quality baseline covering every class the bucket’s tasks are expected to touch, then implements each task via iru-java-code-one-task (concurrently, in a single batch of Agent calls, when the plan marks the group Parallelizable: yes; one at a time otherwise), checking off each task’s box in implementation_plan.md and notifying the user as its implementation lands — before group-wide validation runs. Once every task in the bucket has landed, it validates the whole bucket in one pass instead of once per task: license headers, Javadoc, the affected test classes, coverage, the full suite, and a quality-regression check against its one baseline. A failure traced to a specific task sends that task back for a fix and a re-run of the affected checks, rather than re-validating the whole bucket. It is the Java/Maven counterpart to iru-dotnet-code-one-task-group.

Purpose group

Java Development Tooling

Invocation

/iru-java-code-one-task-group <bucket text>

Inputs

Argument Required Description Default

Bucket text

Yes

Every Java-tagged task/sub-task in the bucket, each with its own text, plus the group’s Parallelizable verdict and any relevant "Current code state" context.

None — this skill is always invoked with a specific bucket’s text, by iru-code-one-task-group.

Outputs

  • Source and test files created/modified per task, via iru-java-code-one-task.

  • License headers and Javadoc kept current across every file/class the bucket touched, checked once for the whole bucket rather than once per task.

  • Tests achieving at least 80% line coverage for the bucket’s changed/new classes, verified against the real coverage report.

  • implementation_plan.md with each task’s (and sub-task’s) checkbox checked and a progress note — first an "implemented, group validation pending" note as each task lands, then replaced with the final coverage/quality outcome once bucket-wide validation passes.

  • User-facing notifications at both phases: per task as its implementation lands, and once when group validation completes.

  • A summary handed back to the caller (iru-code-one-task-group): per task, files touched, tests added/updated, coverage achieved, code-quality outcome, and any task that stopped on a blocker.

Execution flow

flowchart TD A[Start /iru-java-code-one-task-group] --> B["Step 1: capture one pre-change\nquality baseline for the whole bucket\n(iru-java-code-quality, via iru-gate-runner)"] B --> C{Bucket Parallelizable?} C -- yes --> D["Step 2: invoke java-code-one-task\nfor every task concurrently"] C -- no --> E["Step 2: invoke java-code-one-task\nfor each task, one at a time"] D --> F["Check off each task's box +\nnote 'validation pending'; notify user"] E --> F F --> G["Step 3: validate the whole bucket once —\nlicense headers, Javadoc, scoped tests,\ncoverage, full suite, quality vs. baseline"] G -- failure traced to a task --> H["Fix that task's implementation;\nre-run the affected check(s)"] H --> G G -- clean --> I["Step 4: finalize each task's note\nwith final outcome; notify user"] I --> J["Step 5: report the bucket's\noutcome to the caller"]

Dependencies

Invokes

  • Java Code One Task — Step 2, once per task in the bucket (concurrently or sequentially per the group’s Parallelizable verdict), via the iru-isolated-skill-executor agent — that skill implements exactly what the task specifies and writes/updates its tests, nothing more.

Each of the following is invoked via the iru-gate-runner agent rather than directly, so verbose report output stays out of this skill’s own context:

  • Java Code Quality — Step 1 (pre-change baseline for the bucket) and Step 3 (final regression check against that baseline).

  • Check License — Step 3, license headers for every file the bucket touched.

  • Java Javadoc — Step 3, Javadoc for every class the bucket touched.

  • Java Test — Step 3, scoped tests for every class the bucket affected, plus a full-suite run.

  • Java Coverage — Step 3, coverage for every changed/new class in the bucket.

Invoked by

  • Code One Task Group — Step 2, once for the whole bucket of tasks tagged (or defaulted to) java, via a direct Skill call.

Related agents

  • iru-isolated-skill-executor — spawned once per task in the bucket (Step 2), potentially many at once when the group is parallelizable, so each task’s own implementation transcript doesn’t accumulate in this skill’s context.

  • iru-gate-runner — spawned for the baseline capture (Step 1) and every validation check (Step 3), keeping full reports out of this skill’s context.

Source

SKILL.md on GitHub — the file this page was generated from.