afc:auto

/afc:auto — Full Auto Pipeline

Runs clarify? → spec → plan → implement → review → clean fully automatically from a single feature description. Tasks are generated automatically at implement start (no separate tasks phase). Critic Loop runs at each phase (unified safety cap: 5). Convergence terminates early when quality is sufficient. Pre-implementation gates (clarify, TDD pre-gen, blast-radius) run conditionally. Skill Advisor: 5 checkpoints (A–E) at phase boundaries; max 5 auxiliary invocations per pipeline. See skills/auto/skill-advisor.md for details.

Arguments

• $ARGUMENTS — (required) Feature description in natural language

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. Values referenced as {config.*}:

• {config.ci} — full CI command
• {config.gate} — phase gate command
• {config.test} — test command
• {config.architecture} — architecture rules
• {config.code_style} — code style rules

If config missing: ask user to run /afc:init. If declined → abort.

---

Critic Loop Rules

Always read ${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md before running any Critic pass. Core: minimum 1 concern per criterion + mandatory Adversarial failure scenario each pass + quantitative evidence required. "PASS" as a single word is prohibited. On ESCALATE: pause and present options via AskUserQuestion even in auto mode.

---

Execution Steps

Phase 0: Preparation

1. If $ARGUMENTS is empty → print "Please enter a feature description." and abort
2. Check current branch → BRANCH_NAME. Determine feature name (2-3 keywords, kebab-case).
3. Preflight Check:

   "${CLAUDE_SKILL_DIR}/../../scripts/afc-preflight-check.sh"
   

   Exit 1 → abort. Warnings (exit 0) → print and continue.
4. Activate Pipeline Flag:

   "${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" start {feature}
   

   Creates afc/pre-auto safety snapshot, activates Stop Gate Hook, starts change tracking.
5. Create .claude/afc/specs/{feature}/ → record as PIPELINE_ARTIFACT_DIR
6. Initialize Skill Advisor: ADVISOR_COUNT = 0, ADVISOR_TRANSFORM_USED = false

   afc_state_write "advisorCount" "0"
   afc_state_write "advisorTransformUsed" "false"
   

7. Start notification:

   Auto pipeline started: {feature}
   ├─ Clarify? → 1/5 Spec → 2/5 Plan → 3/5 Implement → 4/5 Review → 5/5 Clean
   └─ Running fully automatically (tasks auto-generated, pre-implementation gates conditional)