all-for-claudecode 2.5.0 → 2.7.0

package/.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Automated pipeline for Claude Code — spec → plan → implement → review → clean",
-    "version": "2.5.0"
+    "version": "2.7.0"
   },
   "plugins": [
     {
       "name": "afc",
       "source": "./",
       "description": "Automated pipeline for Claude Code. Automates the full development cycle: spec → plan → implement → review → clean.",
-      "version": "2.5.0",
+      "version": "2.7.0",
       "category": "automation",
       "tags": ["pipeline", "automation", "spec", "plan", "implement", "review", "critic-loop"]
     }

package/.claude-plugin/plugin.json

@@ -1,11 +1,13 @@
 {
   "name": "afc",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "description": "Automated pipeline for Claude Code. Automates the full development cycle: spec → plan → implement → review → clean.",
   "author": { "name": "jhlee0409", "email": "relee6203@gmail.com" },
   "homepage": "https://github.com/jhlee0409/all-for-claudecode",
   "repository": "https://github.com/jhlee0409/all-for-claudecode",
   "license": "MIT",
   "keywords": ["pipeline", "automation", "spec", "plan", "implement", "review", "critic-loop"],
-  "commands": "./commands/"
+  "commands": "./commands/",
+  "agents": "./agents/",
+  "hooks": "./hooks/hooks.json"
 }

package/README.md

@@ -108,6 +108,7 @@ Performance: ✓ no N+1 queries
 | `/afc:implement` | Execute code implementation with CI gates |
 | `/afc:test` | Test strategy planning and test writing |
 | `/afc:review` | Code review with architecture/security scanning |
+| `/afc:clean` | Pipeline artifact cleanup and codebase hygiene |
 | `/afc:research` | Technical research with persistent storage |
 | `/afc:debug` | Bug diagnosis and fix |
 | `/afc:init` | Project setup — detects stack and generates config |
@@ -122,7 +123,11 @@ Performance: ✓ no N+1 queries
 | `/afc:launch` | Generate release artifacts (changelog, tag, publish) |
 | `/afc:validate` | Verify artifact consistency |
 | `/afc:analyze` | General-purpose code and component analysis |
+| `/afc:qa` | Project quality audit — test confidence, error resilience, code health |
 | `/afc:consult` | Expert consultation (backend, infra, PM, design, marketing) |
+| `/afc:triage` | Analyze open PRs and issues in parallel |
+| `/afc:pr-comment` | Generate structured PR review comments |
+| `/afc:release-notes` | Generate release notes from git history |
 | `/afc:clarify` | Resolve spec ambiguities |
 
 ### Individual Command Examples
@@ -142,6 +147,12 @@ Performance: ✓ no N+1 queries
 
 # Explore and structure a product idea
 /afc:ideate "real-time collaboration feature"
+
+# Triage open PRs and issues
+/afc:triage              # all open PRs + issues
+/afc:triage --pr         # PRs only
+/afc:triage --deep       # deep analysis with diff review
+/afc:triage 42 99        # specific items by number
 ```
 
 ## Hook Events
@@ -161,7 +172,7 @@ Every hook fires automatically — no configuration needed after install.
 | `Notification` | Desktop alerts (macOS/Linux) |
 | `TaskCompleted` | CI gate (shell) + acceptance criteria verification (LLM) |
 | `SubagentStop` | Tracks subagent completion in pipeline log |
-| `UserPromptSubmit` | Injects Phase/Feature context per prompt |
+| `UserPromptSubmit` | **Inactive**: detects intent keywords and suggests matching afc skill. **Active**: injects Phase/Feature context + drift checkpoint at threshold prompts |
 | `PermissionRequest` | Auto-allows CI commands during implement/review |
 | `ConfigChange` | Audits/blocks settings changes during active pipeline |
 | `TeammateIdle` | Prevents Agent Teams idle during implement/review |
@@ -176,7 +187,8 @@ Handler types: `command` (shell scripts, all events), `prompt` (LLM single-turn,
 |---|---|
 | `afc-architect` | Remembers ADR decisions and architecture patterns across sessions. Auto-invoked during Plan (ADR recording) and Review (architecture compliance). |
 | `afc-security` | Remembers vulnerability patterns and false positives across sessions. Auto-invoked during Review (security scanning). Runs in isolated worktree. |
-| `afc-impl-worker` | Parallel implementation worker. Receives pre-assigned tasks from orchestrator. Ephemeral (no memory). |
+| `afc-impl-worker` | Parallel implementation worker. Receives pre-assigned tasks from orchestrator. Ephemeral (no memory). Max 50 turns, auto-approve edits. |
+| `afc-pr-analyst` | PR deep analysis worker for triage. Runs in isolated worktree with diff access. Max 15 turns. |
 
 ## Expert Consultation
 
@@ -248,7 +260,7 @@ No. Pure markdown commands + bash hook scripts. No npm packages are imported at
 Debug-based RCA: traces the error, forms a hypothesis, applies a targeted fix. Halts after 3 failed attempts with full diagnosis.
 
 ### Can I run individual phases?
-Yes. Each phase has its own command (`/afc:spec`, `/afc:plan`, `/afc:implement`, `/afc:review`). `/afc:auto` runs them all.
+Yes. Each phase has its own command (`/afc:spec`, `/afc:plan`, `/afc:implement`, `/afc:review`, `/afc:clean`). `/afc:auto` runs them all.
 
 ### What are Critic Loops?
 Convergence-based quality checks after each phase. They evaluate output against criteria and auto-fix issues until stable. 4 verdicts: PASS, FAIL, ESCALATE (asks user), DEFER.

package/agents/afc-architect.md

@@ -7,7 +7,7 @@ tools:
   - Grep
   - Glob
   - Bash
-  - Task
+  - Agent
   - WebSearch
 model: sonnet
 memory: project

package/agents/afc-security.md

@@ -6,7 +6,7 @@ tools:
   - Grep
   - Glob
   - Bash
-  - Task
+  - Agent
   - WebSearch
 disallowedTools:
   - Write

package/commands/analyze.md

@@ -1,6 +1,6 @@
 ---
 name: afc:analyze
-description: "General-purpose code and component analysis"
+description: "General-purpose code and component analysis — use when the user asks to analyze code, trace a flow, audit consistency, understand how something works, or inspect components"
 argument-hint: "<analysis target or question>"
 user-invocable: true
 context: fork

package/commands/architect.md

@@ -1,6 +1,6 @@
 ---
 name: afc:architect
-description: "Architecture analysis and design advice"
+description: "Architecture analysis and design advice — use when the user asks about architecture, system design, layer boundaries, or wants structural design review"
 argument-hint: "[analysis target or design question]"
 context: fork
 agent: afc-architect

package/commands/auto.md

@@ -1,6 +1,6 @@
 ---
 name: afc:auto
-description: "Full auto pipeline"
+description: "Full auto pipeline — use when the user asks to run the full afc pipeline automatically or automate the spec-to-clean cycle"
 argument-hint: "[feature description in natural language]"
 ---
 
@@ -499,7 +499,7 @@ Artifact cleanup and codebase hygiene check after implementation and review:
      ```
    - Create `.claude/afc/memory/quality-history/` directory if it does not exist
 6. **Checkpoint reset**:
-   - Clear `.claude/afc/memory/checkpoint.md` **and** `~/.claude/projects/{ENCODED_PATH}/auto-memory/checkpoint.md` (pipeline complete = session goal achieved, dual-delete prevents stale checkpoint in either location; `ENCODED_PATH` = project path with `/` replaced by `-`)
+   - Clear `.claude/afc/memory/checkpoint.md` **and** `~/.claude/projects/{ENCODED_PATH}/memory/checkpoint.md` (pipeline complete = session goal achieved, dual-delete prevents stale checkpoint in either location; `ENCODED_PATH` = project path with `/` replaced by `-`)
 7. **Timeline finalize**:
    ```bash
    "${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" log pipeline-end "Pipeline complete: {feature}"

package/commands/checkpoint.md

@@ -1,6 +1,6 @@
 ---
 name: afc:checkpoint
-description: "Save session state"
+description: "Save session state — use when the user asks to save progress, checkpoint the session, or preserve current work state"
 argument-hint: "[checkpoint message]"
 model: haiku
 allowed-tools:

package/commands/clarify.md

@@ -1,6 +1,6 @@
 ---
 name: afc:clarify
-description: "Resolve spec ambiguities"
+description: "Resolve spec ambiguities — auto-triggered when requirements are unclear to ask clarifying questions before proceeding"
 argument-hint: "[focus area: security, performance, UI flow]"
 user-invocable: false
 allowed-tools:

package/commands/clean.md

@@ -0,0 +1,126 @@
+---
+name: afc:clean
+description: "Pipeline artifact cleanup and codebase hygiene — use when the user asks to clean up artifacts, remove pipeline files, or finalize after implementation"
+argument-hint: "[feature name — defaults to current pipeline feature]"
+model: haiku
+---
+
+# /afc:clean — Pipeline Cleanup
+
+> Runs the clean phase independently: artifact cleanup, dead code scan, CI verification, memory update, and pipeline flag release.
+> Equivalent to Phase 5 of `/afc:auto`. Use after manually running spec/plan/implement/review phases.
+
+## Arguments
+
+- `$ARGUMENTS` — (optional) Feature name to clean up. Defaults to the currently active pipeline feature.
+
+## Prerequisites
+
+- Pipeline must be active (`afc_state_is_active`) OR a feature name must be provided
+- If pipeline is active, the current phase should be `review` or later
+
+## Execution Steps
+
+### 1. Resolve Feature
+
+```bash
+"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase clean
+```
+
+- If pipeline is active: read feature from state
+- If `$ARGUMENTS` provides a feature name: use that (for manual cleanup without active pipeline)
+- If neither: exit with error — `"No active pipeline and no feature specified. Usage: /afc:clean [feature-name]"`
+
+Set `PIPELINE_ARTIFACT_DIR` = `.claude/afc/specs/{feature}/`
+
+### 2. Artifact Cleanup (scope-limited)
+
+- **Delete only the `.claude/afc/specs/{feature}/` directory created by the current pipeline**
+- If other `.claude/afc/specs/` subdirectories exist, **do not delete them** (only inform the user of their existence)
+- Do not leave pipeline intermediate artifacts in the codebase
+
+### 3. Dead Code Scan
+
+- Detect unused imports from the implementation process (check with `{config.ci}`)
+- Remove empty directories from moved/deleted files
+- Detect unused exports (re-exports of moved code from original locations etc.)
+
+### 4. Final CI Gate
+
+- Run `{config.ci}` final execution
+- Auto-fix on failure (max 2 attempts)
+
+### 5. Memory Update
+
+- Reusable patterns found during pipeline -> record in `.claude/afc/memory/`
+- If there were `[AUTO-RESOLVED]` items -> record decisions in `.claude/afc/memory/decisions/`
+- **If retrospective.md exists** -> record as patterns missed by the Plan phase Critic Loop in `.claude/afc/memory/retrospectives/` (reuse as RISK checklist items in future runs)
+- **If review-report.md exists** -> copy to `.claude/afc/memory/reviews/{feature}-{date}.md` before .claude/afc/specs/ deletion
+- **If research.md exists** and was not already persisted in Plan phase -> copy to `.claude/afc/memory/research/{feature}.md`
+- **Agent memory consolidation**: check each agent's MEMORY.md line count -- if either exceeds 100 lines, invoke the respective agent to self-prune:
+  ```
+  Task("Memory cleanup: afc-architect", subagent_type: "afc:afc-architect",
+    prompt: "Your MEMORY.md exceeds 100 lines. Read it, prune old/redundant entries, and rewrite to under 100 lines following your size limit rules.")
+  ```
+  (Same pattern for afc-security if needed. Skip if both are under 100 lines.)
+- **Memory rotation**: for each memory subdirectory, check file count and prune oldest files if over threshold:
+  | Directory | Threshold | Action |
+  |-----------|-----------|--------|
+  | `quality-history/` | 30 files | Delete oldest files beyond threshold |
+  | `reviews/` | 40 files | Delete oldest files beyond threshold |
+  | `retrospectives/` | 30 files | Delete oldest files beyond threshold |
+  | `research/` | 50 files | Delete oldest files beyond threshold |
+  | `decisions/` | 60 files | Delete oldest files beyond threshold |
+  - Sort by filename ascending (oldest first), delete excess
+  - Log: `"Memory rotation: {dir} pruned {N} files"`
+  - Skip directories that do not exist or are under threshold
+
+### 6. Quality Report
+
+Generate `.claude/afc/memory/quality-history/{feature}-{date}.json` with pipeline metrics (if pipeline was active):
+```json
+{
+  "feature": "{feature}",
+  "date": "{YYYY-MM-DD}",
+  "totals": { "changed_files": N }
+}
+```
+Create `.claude/afc/memory/quality-history/` directory if it does not exist.
+
+### 7. Checkpoint Reset
+
+Clear `.claude/afc/memory/checkpoint.md` **and** `~/.claude/projects/{ENCODED_PATH}/memory/checkpoint.md` (pipeline complete = session goal achieved; `ENCODED_PATH` = project path with `/` replaced by `-`).
+
+### 8. Timeline Finalize
+
+```bash
+"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" log pipeline-end "Pipeline complete: {feature}"
+```
+
+### 9. Release Pipeline Flag
+
+```bash
+"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" end
+```
+
+- Stop Gate Hook deactivated
+- Change tracking log deleted
+- Safety tag removed (successful completion)
+- Phase rollback tags removed (handled automatically by pipeline end)
+
+### 10. Output Summary
+
+```
+Clean complete: {feature}
+├─ Artifacts: {N} files deleted from .claude/afc/specs/{feature}/
+├─ Dead code: {N} items removed
+├─ CI: PASSED
+├─ Memory: {N} files persisted, {N} rotated
+└─ Pipeline flag: released
+```
+
+## Notes
+
+- This command is safe to run multiple times (idempotent -- skips already-deleted artifacts)
+- If no pipeline is active and no feature is specified, the command exits with an informative error
+- When run standalone (not as part of auto), the quality report captures only the information available at clean time

package/commands/consult.md

@@ -1,6 +1,6 @@
 ---
 name: afc:consult
-description: "Expert consultation — get advice from backend, infra, PM, design, marketing, legal, security, or tech advisor specialists"
+description: "Expert consultation — use when the user asks for expert advice, wants to consult a specialist, or needs domain-specific guidance on backend, infra, PM, design, marketing, legal, or tech decisions"
 argument-hint: "[domain?] \"[question]\" [brief|deep]"
 model: sonnet
 ---

package/commands/debug.md

@@ -1,6 +1,6 @@
 ---
 name: afc:debug
-description: "Bug diagnosis and fix"
+description: "Bug diagnosis and fix — use when the user reports a bug, error, crash, exception, broken behavior, or something not working and wants root-cause analysis and a targeted fix"
 argument-hint: "[bug description, error message, or reproduction steps]"
 allowed-tools:
   - Read

package/commands/doctor.md

@@ -1,6 +1,6 @@
 ---
 name: afc:doctor
-description: "Diagnose project health and plugin setup"
+description: "Diagnose project health and plugin setup — use when the user asks for a health check, wants to diagnose project issues, or verify plugin installation"
 argument-hint: "[--verbose]"
 allowed-tools:
   - Read
@@ -59,7 +59,7 @@ Run ALL checks regardless of earlier failures. Do not short-circuit.
 |-------|-----|------|------|
 | Global CLAUDE.md exists | Read `~/.claude/CLAUDE.md` | File exists | ⚠ Warning: no global CLAUDE.md. all-for-claudecode skills won't auto-trigger from intent. Fix: run `/afc:init` |
 | all-for-claudecode block present | Grep for `<!-- AFC:START -->` and `<!-- AFC:END -->` in `~/.claude/CLAUDE.md` | Both markers found | Fix: run `/afc:init` to inject all-for-claudecode block |
-| all-for-claudecode block version | Extract version from `<!-- AFC:VERSION:X.Y.Z -->` in CLAUDE.md. Then read `${CLAUDE_PLUGIN_ROOT}/package.json` to get the actual plugin version. Compare the two. | Block version ≥ plugin version | ⚠ Warning: all-for-claudecode block is outdated (found {block_version}, current {plugin_version}). Fix: run `/afc:init` to update |
+| all-for-claudecode block version | Extract version from `<!-- AFC:VERSION:X.Y.Z -->` in CLAUDE.md. Read `${CLAUDE_PLUGIN_ROOT}/package.json` (`.version`) to get the actual plugin version. Compare the two. | Block version = plugin version | ⚠ Warning: all-for-claudecode block is outdated (found {block_version}, current {plugin_version}). Fix: run `/afc:init` to update |
 | No conflicting routing | Grep for conflicting agent patterns (`executor`, `deep-executor`, `debugger`, `code-reviewer`) outside all-for-claudecode block that could intercept afc intents | No conflicts or conflicts are inside other tool blocks | ⚠ Warning: found agent routing that may conflict with afc skills. Review `~/.claude/CLAUDE.md` |
 
 ### Category 4: Legacy Migration (v1.x → v2.0)
@@ -112,36 +112,56 @@ Run ALL checks regardless of earlier failures. Do not short-circuit.
 
 | Check | How | Pass | Fail |
 |-------|-----|------|------|
-| Version triple match | Compare versions in `package.json`, `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json` (both `metadata.version` and `plugins[0].version`) | All identical | ✗ Fix: update mismatched files to the same version |
+| Version triple match | Compare versions in `package.json` (`.version`), `.claude-plugin/plugin.json` (`.version`), `.claude-plugin/marketplace.json` (`.metadata.version` and `.plugins[0].version`) | All identical | ✗ Fix: update mismatched files to the same version |
 | Cache in sync | Compare `commands/auto.md` content between source and `~/.claude/plugins/cache/all-for-claudecode/afc/{version}/commands/auto.md` | Content matches | ⚠ Warning: plugin cache is stale. Fix: copy source files to cache directory |
 
+### Category 9: Command Definitions (development only)
+
+> Only run if current directory is the all-for-claudecode source repo (same condition as Category 8).
+
+| Check | How | Pass | Fail |
+|-------|-----|------|------|
+| Frontmatter exists | Each `commands/*.md` file has opening and closing `---` block | All files have frontmatter | ✗ Fix: add YAML frontmatter block to `commands/{file}.md` |
+| Required fields | Each command frontmatter contains `name:` and `description:` | All files have both fields | ✗ Fix: add missing `name:` or `description:` to `commands/{file}.md` |
+| Name-filename match | `name:` value follows `afc:{filename}` pattern (e.g. `auto.md` → `name: afc:auto`) | All names match filenames | ✗ Fix: rename `name:` field in `commands/{file}.md` to `afc:{filename}` |
+| Fork-agent reference | Commands with `context: fork` and `agent:` field reference a file that exists in `agents/` (e.g. `agent: afc-architect` → `agents/afc-architect.md` exists) | All agent references resolve | ✗ Fix: create missing agent file `agents/{name}.md` or fix `agent:` field in `commands/{file}.md` |
+
+### Category 10: Agent Definitions (development only)
+
+> Only run if current directory is the all-for-claudecode source repo (same condition as Category 8).
+
+| Check | How | Pass | Fail |
+|-------|-----|------|------|
+| Frontmatter exists | Each `agents/*.md` file has opening and closing `---` block | All files have frontmatter | ✗ Fix: add YAML frontmatter block to `agents/{file}.md` |
+| Required fields | Each agent frontmatter contains `name:`, `description:`, and `model:` | All files have all 3 fields | ✗ Fix: add missing field to `agents/{file}.md` |
+| Name-filename match | `name:` value equals the filename without extension (e.g. `afc-architect.md` → `name: afc-architect`) | All names match filenames | ✗ Fix: rename `name:` field in `agents/{file}.md` to match filename |
+| Expert memory | All 8 expert consultation agents (`afc-backend-expert`, `afc-infra-expert`, `afc-pm-expert`, `afc-design-expert`, `afc-marketing-expert`, `afc-legal-expert`, `afc-appsec-expert`, `afc-tech-advisor`) have `memory: project` | All experts have memory field | ✗ Fix: add `memory: project` to `agents/{name}.md` frontmatter |
+| Worker maxTurns | `afc-impl-worker` and `afc-pr-analyst` have `maxTurns:` field | Both workers have maxTurns | ✗ Fix: add `maxTurns:` to `agents/{name}.md` frontmatter |
+
+### Category 11: Doc References (development only)
+
+> Only run if current directory is the all-for-claudecode source repo (same condition as Category 8).
+
+| Check | How | Pass | Fail |
+|-------|-----|------|------|
+| Referenced docs exist | Scan commands and agents for file references to `docs/` (e.g. `docs/critic-loop-rules.md`, `docs/phase-gate-protocol.md`). Each referenced file must exist. | All referenced docs found | ✗ Fix: create missing `docs/{file}.md` or fix the reference |
+| Domain adapters exist | `docs/domain-adapters/` directory contains at least one `.md` file | ≥ 1 adapter file found | ✗ Fix: add domain adapter files to `docs/domain-adapters/` |
+
 ---
 
 ## Execution
 
-1. Print header:
+1. Run the automated health check script:
    ```
-   all-for-claudecode Doctor
-   =======================
+   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-doctor.sh" $ARGUMENTS
    ```
+   This covers Categories 1-8 automatically.
 
-2. Run each category in order. For each check:
-   - Print `  ✓ {check name}` on pass
-   - Print `  ⚠ {check name}: {brief reason}` on warning
-   - Print `  ✗ {check name}: {brief reason}` on fail
-   - On fail/warning, print `    Fix: {command}` indented below
+2. Print the script's stdout output as-is (already formatted with pass/warn/fail markers).
 
-3. If `--verbose` is in `$ARGUMENTS`:
-   - Print additional details for each check (command output, file paths, versions found)
+3. If in the source repo (package.json `name` = `"all-for-claudecode"`), continue with Categories 9-11 manually using the check tables above.
 
-4. Print summary:
-   ```
-   ─────────────────────────
-   Results: {pass} passed, {warn} warnings, {fail} failures
-   ```
-   - If all pass: `No issues found!`
-   - If warnings only: `{N} warnings found. Non-blocking but review recommended.`
-   - If any failures: `{N} issues need attention. Run the Fix commands above.`
+4. Print combined summary (script summary + any additional findings from Categories 9-11).
 
 ## Example Output
 
@@ -178,8 +198,29 @@ Hook Health
   ✓ All scripts exist
   ✓ All scripts executable
 
+Version Sync (dev)
+  ✓ Version triple match
+  ✓ Cache in sync
+
+Command Definitions (dev)
+  ✓ Frontmatter exists (25 files)
+  ✓ Required fields present
+  ✓ Name-filename match
+  ✓ Fork-agent references valid
+
+Agent Definitions (dev)
+  ✓ Frontmatter exists (12 files)
+  ✓ Required fields present
+  ✓ Name-filename match
+  ✓ Expert memory configured (8/8)
+  ✓ Worker maxTurns configured (2/2)
+
+Doc References (dev)
+  ✓ Referenced docs exist
+  ✓ Domain adapters exist (3 files)
+
 ─────────────────────────
-Results: 14 passed, 2 warnings, 0 failures
+Results: 28 passed, 2 warnings, 0 failures
 2 warnings found. Non-blocking but review recommended.
 ```
 
@@ -189,4 +230,4 @@ Results: 14 passed, 2 warnings, 0 failures
 - **Always run all checks**: do not stop on first failure. The full picture is the value.
 - **Actionable fixes**: every non-pass result must include a Fix line. Never report a problem without a solution.
 - **Fast execution**: skip CI/gate command checks if `--fast` is in arguments (these are the slowest checks).
-- **Development checks**: Category 7 (Version Sync) only runs when inside the all-for-claudecode source repo.
+- **Development checks**: Categories 8–11 (Version Sync, Command Definitions, Agent Definitions, Doc References) only run when inside the all-for-claudecode source repo.

package/commands/ideate.md

@@ -1,6 +1,6 @@
 ---
 name: afc:ideate
-description: "Explore and structure a product idea"
+description: "Explore and structure a product idea — use when the user wants to brainstorm, ideate, explore what to build, or create a product brief from a rough concept"
 argument-hint: "[rough idea or problem statement]"
 allowed-tools:
   - Read

package/commands/implement.md

@@ -1,6 +1,6 @@
 ---
 name: afc:implement
-description: "Execute code implementation"
+description: "Execute code implementation — use when the user asks to implement a feature, execute a planned refactor, modify code from a plan, or build something"
 argument-hint: "[task ID or phase specification]"
 ---
 

package/commands/init.md

@@ -1,6 +1,6 @@
 ---
 name: afc:init
-description: "Project initial setup"
+description: "Project initial setup — use when the user asks to set up the project, initialize afc, configure the plugin, or detect the tech stack"
 argument-hint: "[additional context]"
 allowed-tools:
   - Read
@@ -41,10 +41,12 @@ Before anything else, detect and migrate v1.x (selfish-pipeline) artifacts:
   - Rename: `mv .claude/selfish .claude/afc`
   - Print: `Migrated: .claude/selfish/ → .claude/afc/`
 
-**D. Git tag migration**
-- Check `git tag -l 'selfish/pre-*' 'selfish/phase-*'`
-- If any found: rename each tag (`git tag afc/... selfish/... && git tag -d selfish/...`)
-- Print: `Migrated: {count} git tags (selfish/* → afc/*)`
+**D. Git tag cleanup**
+- Check `git tag -l 'selfish/*'`
+- If any found:
+  - Known patterns (`selfish/pre-*`, `selfish/phase-*`): rename to `afc/` equivalent (`git tag afc/... selfish/... && git tag -d selfish/...`)
+  - All remaining `selfish/*`: delete (`git tag -d`)
+- Print: `Migrated: {renamed} renamed, {deleted} deleted`
 
 ### 2. Check for Existing Config
 
@@ -237,9 +239,11 @@ Classify the user's intent and route to the matching skill. Use semantic underst
 | Test | `afc:test` | User wants to write tests, improve coverage, or verify behavior |
 | Validate | `afc:validate` | User wants to check consistency or validate existing pipeline artifacts |
 | Analyze | `afc:analyze` | User wants to understand, explore, or audit existing code without modifying it |
+| QA Audit | `afc:qa` | User wants project quality audit, test confidence check, or runtime quality gaps |
 | Research | `afc:research` | User wants deep investigation of external tools, libraries, APIs, or technical concepts |
 | Ideate | `afc:ideate` | User wants to brainstorm ideas, explore possibilities, or draft a product brief |
 | Consult | `afc:consult` | User wants expert advice on a decision: library choice, architecture direction, legal/security/infra guidance |
+| Launch | `afc:launch` | User wants to prepare a release — generate changelog, release notes, version bump, or tag |
 | Tasks | `afc:tasks` | User explicitly wants to decompose work into a task breakdown |
 | Ambiguous | `afc:clarify` | User's request is too vague or underspecified to route confidently |
 
@@ -250,13 +254,13 @@ Classify the user's intent and route to the matching skill. Use semantic underst
 3. **Design-first**: When scope is non-trivial (multiple files, architectural decisions needed), prefer `afc:auto` or `afc:plan` over direct `afc:implement`.
 
 User-only (not auto-triggered — inform user on request):
-- `afc:launch` — inform user when release artifact generation is requested
 - `afc:doctor` — inform user when health check is requested
 - `afc:architect` — inform user when architecture review is requested
 - `afc:security` — inform user when security scan is requested
 - `afc:checkpoint` — inform user when session save is requested
 - `afc:resume` — inform user when session restore is requested
 - `afc:principles` — inform user when project principles management is requested
+- `afc:clean` — inform user when pipeline cleanup is requested (artifact cleanup, dead code scan, pipeline flag release)
 - `afc:triage` — inform user when parallel PR/issue triage is requested
 - `afc:pr-comment` — inform user when posting PR review comments to GitHub is requested
 - `afc:release-notes` — inform user when generating release notes from git history is requested

package/commands/launch.md

@@ -1,6 +1,6 @@
 ---
 name: afc:launch
-description: "Generate release artifacts"
+description: "Generate release artifacts — use when the user asks to prepare a release, bump version, publish a package, or create release tags"
 argument-hint: "[version tag or 'auto']"
 allowed-tools:
   - Read

package/commands/plan.md

@@ -1,6 +1,6 @@
 ---
 name: afc:plan
-description: "Implementation design"
+description: "Implementation design — use when the user asks to plan, design an implementation, create a file change map, or figure out how to implement something"
 argument-hint: "[additional context or constraints]"
 allowed-tools:
   - Read

package/commands/pr-comment.md

@@ -1,6 +1,6 @@
 ---
 name: afc:pr-comment
-description: "Post PR review comments to GitHub"
+description: "Post PR review comments to GitHub — use when the user asks to comment on a PR, post review feedback, or submit structured PR review comments"
 argument-hint: "<PR number> [--severity critical,warning,info]"
 allowed-tools:
   - Read

package/commands/principles.md

@@ -1,6 +1,6 @@
 ---
 name: afc:principles
-description: "Manage project principles"
+description: "Manage project principles — use when the user asks to add, remove, or view project coding principles and conventions"
 argument-hint: "[action: add, remove, init]"
 allowed-tools:
   - Read