.NET Code One Task

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

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

Purpose

iru-dotnet-code-one-task is the .NET-specific implementation worker iru-dotnet-code-one-task-group calls once per task. Given one task’s own text (what to build, the named file(s)/type(s)/method(s), the described behavior, its exact implementation_plan.md checkbox line(s), and any sub-tasks), it re-checks the current code state, implements exactly what’s specified, and writes/updates tests in whichever framework this project already uses. If the task didn’t stop on a blocker, it then immediately checks off that task’s own checkbox (and its sub-tasks') in implementation_plan.md with a "group validation pending" note, before reporting back — so an interrupted run doesn’t re-attempt work that already landed, even if the interruption happens before the group’s own validation runs. License headers, XML doc comments, scoped tests, coverage, the full suite, code-quality regression checks, and replacing the pending note with the final validation outcome no longer happen here; they moved to iru-dotnet-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 captures a quality baseline or runs any test/coverage/quality check itself.

Purpose group

.NET Development Tooling

Invocation

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

Inputs

Argument Required Description Default

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)/type(s)/ method(s), the described behavior, its exact `implementation_plan.md` checkbox line(s) for itself and its sub-tasks, and any sub-tasks, plus any relevant "Current code state" context. Normally supplied by `iru-dotnet-code-one-task-group` dispatching one task in a bucket at a time.	None — this skill has nothing to do without a task description.

task description

Yes

The task’s full text as written in implementation_plan.md — what to build, the named file(s)/type(s)/ method(s), the described behavior, its exact implementation_plan.md checkbox line(s) for itself and its sub-tasks, and any sub-tasks, plus any relevant "Current code state" context. Normally supplied by iru-dotnet-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 (target framework/language version, var/nullable reference types only where already used, full XML doc comments, ArgumentException/ArgumentNullException for invalid arguments, no new NuGet dependencies).
Tests added/updated in this project’s existing test framework, covering the new/changed behavior — not run by this skill; the caller runs them once for the whole bucket.
implementation_plan.md with this task’s own checkbox (and its sub-tasks') checked off and a "group validation pending" note, written immediately once the task finishes cleanly — before this skill reports back, and before the caller’s own group-wide validation runs. Left untouched if the task stopped on a blocker.
A short summary handed back to the caller: file(s) touched, tests added/updated, and whether the run stopped on a blocker.

Execution flow

flowchart TD A["Start /dotnet-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 tests\n(xUnit/NUnit/MSTest; not run here)"] D --> E{"Ambiguous, or approach\ninfeasible against real code?"} E -- yes --> F["Step 4: stop; leave checkbox\nunchecked; report blocker to caller"] E -- no --> G["Step 5: check off this task's\ncheckbox + 'validation pending' note"] G --> H["Step 6: report outcome\nto caller: files, tests"]

Dependencies

Invokes

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

Invoked by

.NET 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 including its exact checkbox line(s). That caller re-reads implementation_plan.md afterward to confirm the checkbox this skill already flipped landed, backfilling it only if a rare concurrent-write race clobbered it, then replaces the "pending" note with the final validation outcome once the whole bucket’s validation passes.

Related agents

iru-dotnet-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.