← ClaudeAtlas

stage-implementlisted

Pipeline stage: build the change under the approach the plan stage committed to, test-first. Reached only through a resolved pipeline; not for direct invocation.
m4ttstack/skills · ★ 0 · Code & Development · score 76
Install: claude install-skill m4ttstack/skills
# stage: implement {{stage.fields}} ## Run state Contracts v2 and v3 (authoritative text: the parameterized-skills skill's convention reference). - First action: `rt runs stage-start --stage implement` - Read consumed fields with `rt runs field get <key>` before deriving or asking for them. - Write each declared produce the moment it exists: `rt runs field set <key> <value> --stage implement` - Last action on success: `rt runs stage-done --stage implement`; on failure: `rt runs stage-fail --stage implement --reason "<what actually failed>"` before you report it. Honor `approach` exactly: - **trivial**: make the change; no test because there is no runtime behavior. If you find yourself testing anyway, the triage was wrong -- stop and tell the orchestrator to re-run the plan stage. - **direct-tdd**: invoke superpowers:test-driven-development and run RED -> GREEN -> REFACTOR inline, starting from the FAILING TEST the plan stage named. No spec doc, no subagents. - **superpowers**: run the chain -- superpowers:brainstorming -> spec -> superpowers:writing-plans -> subagent execution. TDD still holds inside every task. When dispatching sub-agents, apply the orchestrator's resolved tiering skill if it announced one. Work only inside `worktree`, commit incrementally on `branch`, never push from this stage. Finish by writing `commits` (the new commit shas, `git log --format=%h` since the branch point).