afc:implement

/afc:implement — Execute Code Implementation

Executes implementation phase by phase with dependency-aware scheduling. Generates tasks.md automatically from plan.md if absent. Swarm mode activates for high-parallelism phases.

Arguments

• $ARGUMENTS — (optional) Specific task ID or phase to run (e.g., T005, phase3)

Project Config (auto-loaded)

!cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] .claude/afc.config.md not found. Create it with /afc:init."

Config Load

Always read .claude/afc.config.md first (read manually if not auto-loaded above).

If config file is missing:

1. Ask the user: ".claude/afc.config.md not found. Run /afc:init to set up the project?"
2. If user accepts → run /afc:init, then restart this command with the original $ARGUMENTS
3. If user declines → abort

Execution Steps

0. Safety Snapshot

Before starting implementation, create a rollback point:

git tag -f afc/pre-implement

• On failure: immediately rollback with git reset --hard afc/pre-implement
• Tag is automatically overwritten on the next /afc:implement run
• Skip if running inside /afc:auto pipeline (the afc/pre-auto tag already exists)

Standalone safety activation (skip if inside /afc:auto): If no active pipeline state exists, activate it for the duration of this command:

"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" start {feature-name-from-plan.md}
"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase implement

This enables Stop Gate and CI Gate hooks during standalone implementation. Release on completion (Step 7) or failure rollback.

1. Load Context

1. Current branch → BRANCH_NAME
2. Load from .claude/afc/specs/{feature}/:
   • plan.md (required) — abort if missing: "plan.md not found. Run /afc:plan first."
   • spec.md (for reference)
   • research.md (if present)
   • tasks.md (if present — may be generated in Step 1.3)
3. Recent changes: run git log --oneline -20
4. Smoke test: run {config.gate} before starting:
   • Fails → diagnose before implementing (fix first or report to user)
5. Baseline test (if {config.test} is non-empty): run {config.test}:
   • Fails → ask user: "(1) Proceed anyway (2) Fix first (3) Abort"
   • Empty → skip