What problem does it solve? After a plan is approved, teams still need to split the work across frontend, backend, devops, and mobile owners, run the tests, and produce an honest implementation report. Doing this by hand risks missed files, unverified claims of success, and lost cross-layer contract notes. ## Core Features & Use Cases - Scope-based routing: Reads the plan's affected_files and matches each file to the executing agent defined in the project's AGENTS.md table, asking the user when no owner matches. - Parallel agent orchestration: Spawns one Task call per matched executing agent, passing contract notes between dependent layers (e.g., backend api_changes to frontend). - Verified reporting: Refuses to claim success when any agent reports status: blocked or a failing test, and writes a per-agent build report to swarm-report/<slug>-build.md. - Use Case: After running /code-plan for a feature touching API and UI, invoke /code-build <slug> to have backend and frontend agents implement their scopes in parallel and receive a test-backed build report. ## Quick Start Run /code-build with the slug of an existing approved plan, for example by asking the assistant to execute /code-build user-auth after the plan file exists in swarm-report.
