Java Code One Task

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

Carry out a single task’s implementation and tests against the real codebase — nothing else. This is the narrowest execution unit in the iru-code pipeline: iru-java-code-one-task-group calls it once per task in a bucket (potentially many at once, in parallel agents).

Purpose

iru-java-code-one-task is the Java-specific implementation worker iru-java-code-one-task-group calls once per task. Given one task’s own text (what to build, the named file(s)/class(es)/method(s), the described behavior, and any sub-tasks), it re-checks the current code state, implements exactly what’s specified, and writes/updates JUnit tests — that’s all. License headers, Javadoc, scoped tests, coverage, the full suite, and code-quality regression checks no longer happen here; they moved to iru-java-code-one-task-group, which validates them once for the whole bucket of tasks instead of once per task, cutting the redundant tool invocations that used to happen here for every single task. It hands back only a short summary; it never reads or writes implementation_plan.md, captures a quality baseline, or runs any test/coverage/quality check itself.

Purpose group

Java Development Tooling

Invocation

/iru-java-code-one-task <task description>

Inputs

Argument Required Description Default

task description

Yes

The task’s full text as written in implementation_plan.md — what to build, the named file(s)/class(es)/ method(s), the described behavior, and any sub-tasks, plus any relevant "Current code state" context. Normally supplied by iru-java-code-one-task-group dispatching one task in a bucket at a time.

None — this skill has nothing to do without a task description.

Outputs

  • Source and test files created/modified per the task, following this repository’s conventions from CLAUDE.md (Java version, final/var type inference only where already used, full Javadoc, IllegalArgumentException for invalid arguments, no new runtime dependencies).

  • JUnit tests added/updated covering the new/changed behavior — not run by this skill; the caller runs them once for the whole bucket.

  • A short summary handed back to the caller: file(s) touched, tests added/updated, and whether the run stopped on a blocker.

  • implementation_plan.md is never read or written by this skill — checking off boxes is the caller’s job, as is capturing any quality baseline or running any validation check.

Execution flow

flowchart TD A["Start /java-code-one-task\n(task description)"] --> B["Step 1: re-check current\ncode state from disk"] B --> C["Step 2: implement exactly what\nthe task specifies"] C --> D["Step 3: write/update JUnit tests\n(not run here)"] D --> E{"Ambiguous, or approach\ninfeasible against real code?"} E -- yes --> F["Step 4: stop; report blocker\nto caller"] E -- no --> G["Step 5: report outcome\nto caller: files, tests"]

Dependencies

Invokes

None — iru-java-code-one-task is a leaf skill; it does not call any other skill in this catalog. License headers, Javadoc, scoped tests, coverage, and quality checks all moved to iru-java-code-one-task-group.

Invoked by

  • Java Code One Task Group — Step 2, once per task in a bucket (concurrently, in a single batch of Agent calls, when the group is marked Parallelizable: yes; one at a time otherwise), via the iru-isolated-skill-executor agent, passing that task’s full text. That skill checks off the task’s box in implementation_plan.md once the whole bucket’s validation passes.

Related agents

iru-java-code-one-task itself does not spawn any Agent — it only reads and edits the code/test files the task names.

Source

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