all-for-claudecode 2.0.0 → 2.1.0

package/.claude-plugin/marketplace.json

@@ -5,15 +5,15 @@
     "email": "relee6203@gmail.com"
   },
   "metadata": {
-    "description": "Automated pipeline for Claude Code — spec → plan → tasks → implement → review → clean",
-    "version": "2.0.0"
+    "description": "Automated pipeline for Claude Code — spec → plan → implement → review → clean",
+    "version": "2.1.0"
   },
   "plugins": [
     {
       "name": "afc",
       "source": "./",
-      "description": "Automated pipeline for Claude Code. Automates the full development cycle: spec → plan → tasks → implement → review → clean.",
-      "version": "2.0.0",
+      "description": "Automated pipeline for Claude Code. Automates the full development cycle: spec → plan → implement → review → clean.",
+      "version": "2.1.0",
       "category": "automation",
       "tags": ["pipeline", "automation", "spec", "plan", "implement", "review", "critic-loop"]
     }

package/.claude-plugin/plugin.json

@@ -1,12 +1,11 @@
 {
   "name": "afc",
-  "version": "2.0.0",
-  "description": "Automated pipeline for Claude Code. Automates the full development cycle: spec → plan → tasks → implement → review → clean.",
+  "version": "2.1.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/",
-  "hooks": "./hooks/hooks.json"
+  "commands": "./commands/"
 }

package/MIGRATION.md

@@ -2,7 +2,7 @@
 
 ## v2.0 — Rebrand: selfish-pipeline → all-for-claudecode
 
-> All-for-ClaudeCode v2.0 renames the package, plugin prefix, scripts, agents, and state files from `selfish` to `afc`.
+> all-for-claudecode v2.0 renames the package, plugin prefix, scripts, agents, and state files from `selfish` to `afc`.
 
 ### What Changed
 
@@ -13,7 +13,7 @@
 | Command prefix | `/selfish:spec` | `/afc:spec` |
 | Script prefix | `selfish-*.sh` | `afc-*.sh` |
 | Agent names | `selfish-architect`, `selfish-security` | `afc-architect`, `afc-security` |
-| State files | `.selfish-active`, `.selfish-phase`, etc. | `.afc-active`, `.afc-phase`, etc. |
+| State files | `.selfish-active`, `.selfish-phase`, etc. | `.claude/.afc-state.json` (single consolidated file) |
 | Config file | `selfish.config.md` | `afc.config.md` |
 | Git tags | `selfish/pre-auto` | `afc/pre-auto` |
 | CLAUDE.md block | `SELFISH:START` / `SELFISH:END` | `AFC:START` / `AFC:END` |
@@ -55,15 +55,18 @@ Replace the `SELFISH:START` / `SELFISH:END` block in your project's CLAUDE.md:
 
 Or simply run `/afc:init` to regenerate the block.
 
-#### 4. Rename state files (if pipeline was active)
+#### 4. Migrate state files (if pipeline was active)
+
+v2.0 consolidated multiple state flag files (`.selfish-active`, `.selfish-phase`, `.selfish-ci-passed`, `.selfish-changes.log`) into a single JSON file (`.claude/.afc-state.json`). If you had an active pipeline:
 
 ```bash
 cd .claude
-for f in .selfish-*; do
-  [ -f "$f" ] && mv "$f" "${f/.selfish-/.afc-}"
-done
+# Remove old individual flag files
+rm -f .selfish-active .selfish-phase .selfish-ci-passed .selfish-changes.log
+# Rename directories
 [ -d selfish ] && mv selfish afc
 [ -f selfish.config.md ] && mv selfish.config.md afc.config.md
+# Note: .afc-state.json is created automatically on next pipeline start
 ```
 
 #### 5. Update git tags
@@ -159,9 +162,9 @@ For new projects, you can auto-generate it with `/afc:init`.
 ## What Stays the Same
 
 - `.claude/afc.config.md` file format and path
-- `.afc-*` state file paths
 - `git tag afc/pre-*` safety tags
 - Internal logic of hook scripts
+- Pipeline state concept (now consolidated in `.claude/.afc-state.json`)
 
 ## What Changed (v1.2.2+)
 

package/README.md

@@ -1,18 +1,18 @@
-# All-for-ClaudeCode
+# all-for-claudecode
 
-**Claude Code plugin that automates the full development cycle — spec → plan → tasks → implement → review → clean.**
+**Claude Code plugin that automates the full development cycle — spec → plan → implement → review → clean.**
 
 [![npm version](https://img.shields.io/npm/v/all-for-claudecode)](https://www.npmjs.com/package/all-for-claudecode)
 [![license](https://img.shields.io/github/license/jhlee0409/all-for-claudecode)](./LICENSE)
-[![test](https://img.shields.io/badge/tests-161%20passed-brightgreen)](#how-it-works)
+[![test](https://img.shields.io/badge/tests-125%20passed-brightgreen)](#how-it-works)
 [![hooks](https://img.shields.io/badge/hooks-15%20events-blue)](#15-hook-events)
 [![commands](https://img.shields.io/badge/commands-18-orange)](#18-slash-commands)
 
-> Zero-dependency automation pipeline for Claude Code. One command (`/afc:auto`) runs the entire cycle: write specs, design plans, break into tasks, implement code, review quality, and clean up — all with built-in CI gates and critic loops.
+> Zero-dependency automation pipeline for Claude Code. One command (`/afc:auto`) runs the entire cycle: write specs, design plans, implement code, review quality, and clean up — all with built-in CI gates and critic loops.
 
-## What is All-for-ClaudeCode?
+## What is all-for-claudecode?
 
-All-for-ClaudeCode is a **Claude Code plugin** that transforms your development workflow into a fully automated pipeline. Instead of manually prompting Claude through each development phase, you run a single command and the pipeline handles everything — from writing feature specifications to final code review.
+all-for-claudecode is a **Claude Code plugin** that transforms your development workflow into a fully automated pipeline. Instead of manually prompting Claude through each development phase, you run a single command and the pipeline handles everything — from writing feature specifications to final code review.
 
 - **18 slash commands** for every phase of development
 - **15 hook events** with 3 handler types (shell scripts, LLM prompts, subagents)
@@ -55,11 +55,10 @@ claude plugin install afc@all-for-claudecode --scope user
 
 That's it. The pipeline will:
 1. Write a feature spec with acceptance criteria
-2. Design an implementation plan with file change map
-3. Break the plan into parallelizable tasks
-4. Implement each task with CI verification
-5. Run a code review with security scan
-6. Clean up artifacts and prepare for commit
+2. Design an implementation plan with file change map and dependency graph
+3. Implement each task with CI verification (tasks auto-generated from plan)
+4. Run a code review with security scan
+5. Clean up artifacts and prepare for commit
 
 ## Features
 
@@ -69,10 +68,10 @@ That's it. The pipeline will:
 /afc:auto "feature description"
 ```
 
-Runs all 6 phases automatically with **Critic Loop** quality checks at each gate:
+Runs all 5 phases automatically with **Critic Loop** quality checks at each gate:
 
 ```
-Spec (1/6) → Plan (2/6) → Tasks (3/6) → Implement (4/6) → Review (5/6) → Clean (6/6)
+Spec (1/5) → Plan (2/5) → Implement (3/5) → Review (4/5) → Clean (5/5)
 ```
 
 ### 18 Slash Commands
@@ -81,7 +80,7 @@ Spec (1/6) → Plan (2/6) → Tasks (3/6) → Implement (4/6) → Review (5/6)
 
 | Command | Description |
 |---|---|
-| `/afc:auto` | Full Auto pipeline — runs all 6 phases |
+| `/afc:auto` | Full Auto pipeline — runs all 5 phases |
 | `/afc:spec` | Write feature specification with acceptance criteria |
 | `/afc:plan` | Design implementation plan with file change map |
 | `/afc:implement` | Execute code implementation with CI gates |
@@ -106,7 +105,7 @@ Spec (1/6) → Plan (2/6) → Tasks (3/6) → Implement (4/6) → Review (5/6)
 
 | Command | Description |
 |---|---|
-| `/afc:tasks` | Break plan into parallelizable tasks |
+| `/afc:tasks` | Task decomposition (auto-generated by implement) |
 | `/afc:analyze` | Verify artifact consistency |
 | `/afc:clarify` | Resolve spec ambiguities |
 
@@ -165,12 +164,11 @@ Two custom agents that **learn across sessions**:
 ┌─────────────────────────────────────────────┐
 │  /afc:auto "Add feature X"              │
 ├─────────────────────────────────────────────┤
-│  Phase 1: Spec    → Critic Loop → Gate ✓    │
-│  Phase 2: Plan    → Critic Loop → Gate ✓    │
-│  Phase 3: Tasks   → Critic Loop → Gate ✓    │
-│  Phase 4: Implement → CI Gate → Gate ✓      │
-│  Phase 5: Review  → Security Scan → Gate ✓  │
-│  Phase 6: Clean   → Artifacts removed       │
+│  Phase 1: Spec      → Critic Loop → Gate ✓   │
+│  Phase 2: Plan      → Critic Loop → Gate ✓   │
+│  Phase 3: Implement → Tasks auto-gen → CI ✓  │
+│  Phase 4: Review    → 8 perspectives → Gate ✓│
+│  Phase 5: Clean     → Artifacts removed      │
 ├─────────────────────────────────────────────┤
 │  15 hooks run automatically at each step    │
 │  Stop/TaskCompleted gates block if CI fails │
@@ -194,7 +192,7 @@ This detects your tech stack and generates `.claude/afc.config.md` with:
 ## FAQ
 
 ### What is all-for-claudecode?
-A Claude Code plugin that automates the entire development cycle (spec → plan → tasks → implement → review → clean) through 18 slash commands and 15 hook events.
+A Claude Code plugin that automates the entire development cycle (spec → plan → implement → review → clean) through 18 slash commands and 15 hook events.
 
 ### How does it compare to manual Claude Code workflows?
 Instead of manually prompting each step, all-for-claudecode orchestrates the full cycle with built-in quality gates that physically prevent skipping CI or security checks.

package/agents/afc-architect.md

@@ -18,6 +18,22 @@ skills:
 
 You are an architecture analysis agent for the current project.
 
+## Pipeline Integration
+
+This agent is invoked automatically during the auto pipeline at two points:
+
+### Plan Phase — ADR Recording
+- **Input**: Architecture Decision + File Change Map sections from plan.md
+- **Task**: Check for conflicts with existing ADRs, record new decisions
+- **Output**: `{ decisions_recorded: N, conflicts: [{ existing: "...", new: "...", reason: "..." }] }`
+- If conflicts found: orchestrator ESCALATEs to user
+
+### Review Phase — Architecture Review (Perspective B)
+- **Input**: List of changed files from `git diff`
+- **Task**: Review files for architecture compliance, cross-reference with ADRs
+- **Output**: Findings as `severity (Critical/Warning/Info), file:line, issue, suggested fix`
+- Findings are merged into the consolidated review report
+
 ## Reference Documents
 
 Before performing analysis, read these shared reference documents:

package/agents/afc-impl-worker.md

@@ -0,0 +1,40 @@
+---
+name: afc-impl-worker
+description: "Parallel implementation worker — executes assigned tasks from the pipeline task pool with worktree isolation support."
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+model: sonnet
+---
+
+You are a parallel implementation worker for the all-for-claudecode pipeline.
+
+## Workflow
+
+The orchestrator pre-assigns tasks to you via the prompt. Do NOT self-claim tasks via TaskList/TaskUpdate — this avoids last-write-wins race conditions.
+
+1. Read the **Implementation Context** section in your prompt first — this contains the feature objective, constraints, edge cases, and prohibitions from the original spec/plan
+2. Read the task list provided in your prompt (orchestrator pre-assigned)
+3. For each assigned task, in order:
+   a. Read all files you need to modify BEFORE making changes
+   b. Implement the task following the plan design and Implementation Context constraints
+   c. Verify with the project's gate command if applicable
+4. Return a structured summary of completed work:
+   - Files changed (with paths)
+   - Key decisions made during implementation
+   - Issues encountered or concerns
+   - Gate command result
+5. Do NOT call TaskList or TaskUpdate — the orchestrator handles task state management
+
+## Rules
+
+- Always read existing files before modifying them
+- Follow the project's shell script conventions: `set -euo pipefail`, `trap cleanup EXIT`, jq-first parsing
+- Use `printf '%s\n' "$VAR"` instead of `echo "$VAR"` for external data
+- All scripts must pass shellcheck
+- Do not modify files outside your assigned task's scope
+- If a task fails, report the error and move to the next task

package/agents/afc-security.md

@@ -18,6 +18,17 @@ skills:
 
 You are a security scanning agent for the current project.
 
+## Pipeline Integration
+
+This agent is invoked automatically during the auto pipeline:
+
+### Review Phase — Security Review (Perspective C)
+- **Input**: List of changed files from `git diff`
+- **Task**: Scan for security vulnerabilities, filter known false positives from memory
+- **Output**: Findings as `severity (Critical/Warning/Info), file:line, issue, suggested fix`
+- Findings are merged into the consolidated review report
+- Check for: command injection, path traversal, unvalidated input, sensitive data exposure, shell escaping issues
+
 ## Reference Documents
 
 Before performing scans, read these shared reference documents:

package/bin/cli.mjs

@@ -40,7 +40,7 @@ function run(cmd) {
 
 async function main() {
   console.log();
-  console.log("  All-for-ClaudeCode — Claude Code Plugin Installer");
+  console.log("  all-for-claudecode — Claude Code Plugin Installer");
   console.log("  ===================================================");
   console.log();
 

package/commands/analyze.md

@@ -123,4 +123,4 @@ Analysis complete
 
 - **Read-only**: Do not modify any files. Report only.
 - **Avoid false positives**: Do not over-flag ambiguity. Consider context.
-- **Optional**: Not required in the pipeline. Can proceed plan → tasks → implement directly.
+- **Optional**: Not required in the pipeline. Can proceed plan → implement directly.