code-factory

Use this agent when executing-plans exhausts max-3 remediation cycles. Receives spec, failed requirements, and current code with FRESH context (no prior failed attempts). Produces root-cause analysis and either a targeted fix plan or a blocking verdict.

Use this agent at phase boundaries to verify that implementation matches the plan — checks logic correctness, completeness, edge case handling, and boundary violations.

Use this agent to convert a design spec into a multi-file phased task plan. Produces plan.md (TOC + coverage), standards.md (one-time codebase context), and phase files under phases/ — Phase 1 and Verification fully elaborated; intermediate phases as sketches for just-in-time elaboration. Uses behavior-focused verification: TDD for behavior-bearing code and direct verification for mechanical artifact work. Runs codebase exploration in its own context so the main agent stays clean.

Use this agent at phase boundaries to review code organization, patterns, naming, and reuse opportunities. Absorbs simplify's concerns (reuse detection, deduplication, complexity reduction) without project-specific opinions.

Use this agent to implement a single task from a decomposed task list. Takes inline task text with context and produces working code with tests and verification.

Use when you have a design spec from writing-specs and need to break it into an implementable, phased task plan with behavior-focused verification before writing any code

Use when you have a plan directory from decomposing-specs and need to execute it — loads phases on demand, dispatches phase-elaborator for sketched phases, runs implementers with size-scaled phase reviews, and validates the full spec at the end

Use when a GitHub issue receives new comments during autonomous work — decides whether to update the spec and re-decompose, or just make the change inline

Use when configuring a repository to run with Code Factory — creates `.code-factory/config.toml`, sets up a devcontainer if missing, and validates that build/lint/test work inside it. Triggers on "setup code factory", "configure code factory", "onboard this repo to code factory".

Use when starting any feature, system change, or bugfix that requires architectural decisions — before writing implementation plans or code. Triggers on new projects, multi-component changes, API design, or when the user says "design", "spec", or "architecture".