all-for-claudecode 2.1.0 → 2.2.0

package/commands/implement.md

@@ -141,7 +141,7 @@ TaskUpdate({ taskId: "T004", addBlockedBy: ["T002"] })  // if T004 depends on T0
 
 **Step 2 — Launch unblocked [P] tasks in a single message** (Claude Code executes multiple Task() calls in a single message concurrently, up to ~10):
 ```
-Task("T003: Create UserService", subagent_type: "afc-impl-worker",
+Task("T003: Create UserService", subagent_type: "afc:afc-impl-worker",
   isolation: "worktree",
   prompt: "Implement the following task:
 
@@ -164,7 +164,7 @@ Task("T003: Create UserService", subagent_type: "afc-impl-worker",
   - Key decisions: {any design choices made}
   - Issues: {blockers or concerns, if any}
   - Verification: {config.gate} result")
-Task("T004: Create AuthService", subagent_type: "afc-impl-worker", isolation: "worktree", ...)
+Task("T004: Create AuthService", subagent_type: "afc:afc-impl-worker", isolation: "worktree", ...)
 ```
 
 **Step 3 — Collect results and advance**: After all parallel agents return:
@@ -201,7 +201,7 @@ TaskUpdate({ taskId: "T008", addBlockedBy: ["T006"] })  // if dependency exists
 Instead of workers self-claiming (race-prone), the **orchestrator pre-assigns** tasks:
 ```
 // Orchestrator assigns: each worker gets a unique, non-overlapping task set
-Task("Worker 1: T007, T009, T011", subagent_type: "afc-impl-worker",
+Task("Worker 1: T007, T009, T011", subagent_type: "afc:afc-impl-worker",
   isolation: "worktree",
   prompt: "Implement these tasks in order:
   1. T007: {description} — `{file path}`
@@ -224,7 +224,7 @@ Task("Worker 1: T007, T009, T011", subagent_type: "afc-impl-worker",
   Return a structured summary per task (max 2000 chars total):
   - Files changed, key decisions, issues encountered per task.")
 
-Task("Worker 2: T008, T010, T012", subagent_type: "afc-impl-worker", isolation: "worktree", ...)
+Task("Worker 2: T008, T010, T012", subagent_type: "afc:afc-impl-worker", isolation: "worktree", ...)
 ```
 
 **Step 3 — Collect and reconcile**:

package/commands/init.md

@@ -1,8 +1,7 @@
 ---
 name: afc:init
 description: "Project initial setup"
-argument-hint: "[preset: nextjs-fsd | react-spa | express-api | monorepo]"
-disable-model-invocation: true
+argument-hint: "[additional context]"
 allowed-tools:
   - Read
   - Write
@@ -18,9 +17,7 @@ model: haiku
 
 ## Arguments
 
-- `$ARGUMENTS` — (optional) Template preset name (e.g., `nextjs-fsd`)
-  - If not specified: analyzes project structure and auto-infers
-  - If preset specified: uses `${CLAUDE_PLUGIN_ROOT}/templates/afc.config.{preset}.md`
+- `$ARGUMENTS` — (optional) Additional context or hints for project analysis
 
 ## Execution Steps
 
@@ -55,64 +52,76 @@ If `.claude/afc.config.md` already exists:
 - Ask user: "Config file already exists. Do you want to overwrite it?"
 - If declined: **abort**
 
-### 3. Preset Branch
+### 3. Analyze Project Structure
 
-#### A. Preset Specified (`$ARGUMENTS` provided)
-
-1. Verify `${CLAUDE_PLUGIN_ROOT}/templates/afc.config.{$ARGUMENTS}.md` exists
-2. If found: copy that file to `.claude/afc.config.md`
-3. If not found: print "Preset `{$ARGUMENTS}` not found. Available: {list}" then **abort**
-
-#### B. Auto-Infer (`$ARGUMENTS` not provided)
-
-Analyze project structure and auto-infer configuration:
+Analyze the project and auto-infer configuration. Use `$ARGUMENTS` as additional context if provided.
 
 **Step 1. Package Manager / Script Detection**
 - Read `package.json` → extract CI-related commands from `scripts` field
-- Determine package manager from lockfile (yarn.lock / pnpm-lock.yaml / package-lock.json)
-- Reflect detected scripts in `CI Commands` section
+- Determine package manager from lockfile:
+
+| Lockfile | Package Manager |
+|----------|----------------|
+| `pnpm-lock.yaml` | pnpm |
+| `yarn.lock` | yarn |
+| `bun.lockb` or `bun.lock` | bun |
+| `package-lock.json` | npm |
+
+- If no lockfile: check `packageManager` field in `package.json`
+- Non-JS projects: check `pyproject.toml` (Python), `Cargo.toml` (Rust), `go.mod` (Go)
 
 **Step 2. Framework Detection**
 - Determine from `package.json` dependencies/devDependencies:
-  - `next` → Next.js (App Router/Pages Router determined by presence of `app/` directory)
-  - `nuxt` → Nuxt
-  - `@sveltejs/kit` → SvelteKit
-  - `vite` → Vite
-  - etc.
+
+| Dependency | Framework |
+|-----------|-----------|
+| `next` | Next.js (App Router if `app/` dir exists, else Pages Router) |
+| `nuxt` | Nuxt |
+| `@sveltejs/kit` | SvelteKit |
+| `@remix-run/react` | Remix |
+| `astro` | Astro |
+| `@angular/core` | Angular |
+| `vite` (alone) | Vite SPA |
+| `hono` | Hono |
+| `fastify` | Fastify |
+| `express` | Express |
+
+- Non-JS: `pyproject.toml` → Django/FastAPI/Flask, `Cargo.toml` → Rust project, `go.mod` → Go project
 - Presence of `tsconfig.json` → TypeScript indicator
 
 **Step 3. Architecture Detection**
 - Analyze directory structure:
-  - `src/app/`, `src/features/`, `src/entities/`, `src/shared/` → FSD
+  - FSD: requires **at least 3** of `features/`, `entities/`, `shared/`, `widgets/`, `pages/` under `src/`
   - `src/domain/`, `src/application/`, `src/infrastructure/` → Clean Architecture
   - `src/modules/` → Modular
   - Other → Layered
-- `paths` in `tsconfig.json` → extract path_alias
-
-**Step 4. State Management Detection**
-- From dependencies:
-  - `zustand` → Zustand
-  - `@reduxjs/toolkit` → Redux Toolkit
-  - `@tanstack/react-query` → React Query
-  - `swr` → SWR
-  - `pinia` → Pinia
-
-**Step 5. Styling / Testing Detection**
-- `tailwindcss` → Tailwind CSS
-- `styled-components` → styled-components
-- `jest` / `vitest` / `playwright` → mapped respectively
-
-**Step 6. Code Style Detection**
-- Check `.eslintrc*` / `eslint.config.*` → identify lint rules
-- `strict` in `tsconfig.json` → strict_mode
+- `paths` in `tsconfig.json` → extract path alias
+
+**Step 4. State / Styling / Testing / DB Detection**
+- State management: `zustand`, `@reduxjs/toolkit`, `@tanstack/react-query`, `swr`, `pinia`, `jotai`, `recoil`
+- Styling: `tailwindcss`, `styled-components`, `@emotion/react`, `sass`, CSS Modules (check for `*.module.css`)
+- Testing: `jest`, `vitest`, `playwright`, `@testing-library/*`, `cypress`
+- Linter: `.eslintrc*` / `eslint.config.*` / `biome.json` / `biome.jsonc`
+- DB/ORM: `prisma` (check `prisma/schema.prisma`), `drizzle-orm`, `typeorm`, `@prisma/client`
+
+**Step 5. Code Style Detection**
+- Check linter config → identify key rules
+- `strict` in `tsconfig.json` → strict mode
 - Read 2-3 existing code samples to verify naming patterns
 
 ### 4. Generate Config File
 
-1. Generate config based on `${CLAUDE_PLUGIN_ROOT}/templates/afc.config.template.md`
-2. Fill in blanks with auto-inferred values
-3. For items that cannot be inferred: keep template defaults + mark with `# TODO: Adjust for your project`
-4. Save to `.claude/afc.config.md`
+Generate `.claude/afc.config.md` in **free-form markdown** format:
+
+1. **CI Commands** section: YAML code block with `ci`, `gate`, `test` keys (fixed format, scripts parse these)
+2. **Architecture** section: describe detected architecture style, layers, import rules, path aliases in free-form prose/lists
+3. **Code Style** section: describe detected language, strictness, naming conventions, lint rules in free-form prose/lists
+4. **Project Context** section: describe framework, state management, styling, testing, DB/ORM, risks, and any other relevant project characteristics in free-form prose/lists
+
+Reference `${CLAUDE_PLUGIN_ROOT}/templates/afc.config.template.md` for the section structure.
+Write sections as natural descriptions — **no YAML code blocks** except for CI Commands.
+For items that cannot be inferred: note `TODO: Adjust for your project` inline.
+Save to `.claude/afc.config.md`.
 
 ### 5. Scan Global CLAUDE.md and Detect Conflicts
 
@@ -214,10 +223,12 @@ IMPORTANT: For requests matching the afc skill routing table below, always invok
 | Spec | `afc:spec` | spec, specification |
 | Tasks | `afc:tasks` | break down tasks, decompose |
 | Research | `afc:research` | research, investigate |
+| Ideate | `afc:ideate` | idea, brainstorm, what to build, product brief |
 | Ambiguous | `afc:clarify` | auto-triggered when requirements are unclear |
 | Full auto | `afc:auto` | do it automatically, auto-run |
 
 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
@@ -268,7 +279,6 @@ all-for-claudecode initialization complete
 
 - **Overwrite caution**: If config file already exists, always confirm with user.
 - **Inference limits**: Auto-inference is best-effort. User may need to review and adjust.
-- **Preset path**: Presets are loaded from the `templates/` directory inside the plugin.
 - **`.claude/` directory**: Created automatically if it does not exist.
 - **Global CLAUDE.md principles**:
   - Never modify content outside the `<!-- AFC:START/END -->` markers (the `AFC` prefix in markers is a compact technical identifier)

package/commands/launch.md

@@ -0,0 +1,181 @@
+---
+name: afc:launch
+description: "Generate release artifacts"
+argument-hint: "[version tag or 'auto']"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+model: sonnet
+---
+
+# /afc:launch — Generate Release Artifacts
+
+> Generates release artifacts (CHANGELOG entry, README updates, GitHub Release notes) from git history and optional spec context.
+> This is a **standalone utility** — not part of the auto pipeline.
+> Works with or without a prior afc pipeline run.
+
+## Arguments
+
+- `$ARGUMENTS` — (optional) One of:
+  - Version tag: `"v2.2.0"` — uses this as the release version
+  - `"auto"` — auto-detects version from package.json/Cargo.toml/pyproject.toml
+  - Not specified: prompts for version
+
+## Execution Steps
+
+### 1. Detect Project Context
+
+1. **Version detection**:
+   - If `$ARGUMENTS` is a version string (matches `v?\d+\.\d+\.\d+`): use it
+   - If `$ARGUMENTS` = `"auto"`: read version from package.json → Cargo.toml → pyproject.toml → setup.py (first found)
+   - If not specified: check package.json etc. for current version, present to user, confirm or override
+
+2. **Previous version detection**:
+   ```bash
+   git describe --tags --abbrev=0 2>/dev/null || echo "none"
+   ```
+   - If a previous tag exists: diff range = `{previous_tag}..HEAD`
+   - If no tags: diff range = all commits (warn user: "No previous release tag found. Including all history.")
+
+3. **Changelog detection**:
+   - Check for existing: `CHANGELOG.md` → `CHANGES.md` → `HISTORY.md`
+   - If found: will prepend new entry
+   - If not found: will create `CHANGELOG.md`
+
+### 2. Gather Change Context
+
+Collect all available context for high-quality release notes:
+
+1. **Git history** (required):
+   ```bash
+   git log {previous_tag}..HEAD --pretty=format:"%h %s" --no-merges
+   ```
+
+2. **Changed files summary** (required):
+   ```bash
+   git diff --stat {previous_tag}..HEAD
+   ```
+
+3. **Spec context** (optional — enhances quality):
+   - Glob `.claude/afc/specs/*/spec.md` — if any exist, read Overview and User Stories sections
+   - This provides **intent context** that raw commit messages lack
+   - If no specs found: rely on git history only (still produces good output)
+
+4. **Review context** (optional):
+   - Glob `.claude/afc/memory/reviews/*` — if any exist from this version cycle, note key findings
+   - Skip if not found
+
+5. **Breaking change detection**:
+   - Grep commit messages for: `BREAKING`, `breaking change`, `!:` (conventional commits)
+   - Grep diffs for: deleted public exports, renamed public APIs, changed function signatures
+   - Flag any findings as breaking changes in the output
+
+### 3. Generate CHANGELOG Entry
+
+Prepend a new entry to the changelog file:
+
+1. **Duplicate check**: Grep the changelog for `## [{version}]`. If an entry for this version already exists:
+   - Ask user: "CHANGELOG already has an entry for {version}. (1) Overwrite (2) Abort"
+   - If overwrite: replace the existing entry (from `## [{version}]` to the next `## [` line)
+   - If abort: skip CHANGELOG generation
+
+2. Follow the existing format if one exists; otherwise use [Keep a Changelog](https://keepachangelog.com/) format:
+
+```markdown
+## [{version}] - {YYYY-MM-DD}
+
+### Added
+- {new features, described from user perspective}
+
+### Changed
+- {modifications to existing functionality}
+
+### Fixed
+- {bug fixes}
+
+### Removed
+- {removed features or deprecated items}
+
+### Breaking Changes
+- {if any — empty section omitted}
+```
+
+**Quality rules**:
+- Write from **user perspective**, not developer perspective ("Add dark mode support" not "Add ThemeProvider component")
+- Group related changes into single entries (don't list every file)
+- If spec context is available: use feature names from specs, not commit message fragments
+- Omit empty sections (if no fixes, don't include "### Fixed")
+
+### 4. Update README (conditional)
+
+Only update README if meaningful changes warrant it:
+
+1. **Check triggers**:
+   - New CLI commands or API endpoints added?
+   - Installation process changed?
+   - New dependencies or requirements?
+   - Feature that users need to know about?
+
+2. **If no triggers match**: skip README update entirely (print: "README: no updates needed")
+
+3. **If triggers match**: read current README, identify the relevant section, apply minimal targeted edit
+   - Do NOT rewrite the entire README
+   - Do NOT add badges, shields, or decorative elements
+   - Only update sections directly affected by changes
+
+### 5. Generate GitHub Release Notes
+
+Create `.claude/afc/release-notes.md` (draft for `gh release create`):
+
+```markdown
+# {version}
+
+{2-3 sentence summary of this release — what's the headline?}
+
+## Highlights
+
+- {top 1-3 user-facing changes, expanded with context}
+
+## What's Changed
+
+{CHANGELOG entry content, reformatted for GitHub}
+
+## Breaking Changes
+
+{if any — clear migration instructions}
+
+**Full Changelog**: {previous_tag}...{version}
+```
+
+### 6. Present Summary and Next Steps
+
+```
+Release artifacts generated: {version}
+├─ CHANGELOG.md: entry prepended ({N} items across {M} categories)
+├─ README.md: {updated section / no updates needed}
+├─ .claude/afc/release-notes.md: draft created
+├─ Breaking changes: {count or "none"}
+├─ Commits included: {N} (since {previous_tag})
+└─ Specs referenced: {N or "none (git-only mode)"}
+
+Next steps:
+  git add CHANGELOG.md README.md
+  git commit -m "docs: prepare release {version}"
+  git tag {version}
+  gh release create {version} --notes-file .claude/afc/release-notes.md
+```
+
+**Do NOT execute these commands automatically.** Present them for the user to review and run.
+
+## Notes
+
+- **Not part of the auto pipeline**. Launch is a standalone utility invoked when you're ready to release, not after every feature.
+- **Non-destructive**: only creates/edits CHANGELOG and README (conditionally). Does not push, tag, or create releases automatically.
+- **Git history is the source of truth**. Spec context enhances quality but is never required.
+- **Conventional Commits awareness**: if the project uses conventional commits (`feat:`, `fix:`, `chore:`), the generated CHANGELOG respects those categories.
+- **Idempotent**: running launch twice with the same version overwrites the release-notes.md draft and re-generates the CHANGELOG entry (warns before overwriting).
+- **No scope for `clean`**: release-notes.md in `.claude/afc/` is a draft file. The user decides whether to keep or delete it after the release.

package/commands/plan.md

@@ -109,13 +109,7 @@ Create `.claude/afc/specs/{feature}/plan.md`. **Must** follow the structure belo
 {summary of core requirements from spec + technical approach, 3-5 sentences}
 
 ## Technical Context
-{summary of project settings loaded from afc.config.md}
-- **Language**: {config.code_style.language}
-- **Framework**: {config.framework.name}
-- **State**: {config.state_management summary}
-- **Architecture**: {config.architecture.style}
-- **Styling**: {config.styling.framework}
-- **Testing**: {config.testing.framework}
+{Summarize key project settings from afc.config.md — Architecture, Code Style, and Project Context sections}
 - **Constraints**: {constraints extracted from spec}
 
 ## Principles Check

package/commands/principles.md

@@ -2,7 +2,6 @@
 name: afc:principles
 description: "Manage project principles"
 argument-hint: "[action: add, remove, init]"
-disable-model-invocation: true
 allowed-tools:
   - Read
   - Write

package/commands/resume.md

@@ -2,7 +2,6 @@
 name: afc:resume
 description: "Restore session"
 argument-hint: "[no arguments]"
-disable-model-invocation: true
 model: haiku
 allowed-tools:
   - Read

package/commands/review.md

@@ -127,12 +127,12 @@ For each changed file, examine from the following perspectives:
 - Startup/response latency concerns
 - Unnecessary computation or redundant operations
 - Resource management (memory, file handles, connections, subprocesses)
-- {config.framework}-specific performance patterns
+- Framework-specific performance patterns (from Project Context)
 
 #### E. Project Pattern Compliance
 - {config.code_style} naming and structure conventions
 - {config.architecture} layer rules and boundaries
-- {config.framework}-specific idioms and best practices
+- Framework-specific idioms and best practices (from Project Context)
 
 #### F. Reusability
 - Duplicate or near-duplicate logic across files

package/commands/security.md

@@ -2,7 +2,6 @@
 name: afc:security
 description: "Security scan (read-only)"
 argument-hint: "[scan scope: file/directory path or full]"
-disable-model-invocation: true
 context: fork
 agent: afc-security
 allowed-tools:
@@ -27,16 +26,14 @@ model: sonnet
 
 ## Config Load
 
-Read the following settings from `CLAUDE.md` or `.claude/CLAUDE.md` at the project root and assign to the `config` variable:
+**Always** read `.claude/afc.config.md` first. This file contains free-form markdown sections:
+- `## Project Context` — framework, state management, testing, etc. (primary source for framework info)
+- `## Architecture` — architecture pattern, layers, import rules
+- `## Code Style` — language, naming conventions, lint rules
 
-```
-config.framework  = the framework used in the project
-                    (e.g., "Next.js", "Nuxt", "SvelteKit", "Express", "NestJS")
-                    → Framework specified in CLAUDE.md. Assume "unknown" if not present.
-config.auditCmd   = dependency audit command
-                    (e.g., "yarn audit", "npm audit", "pnpm audit")
-                    → Infer from the packageManager field in package.json or the lockfile.
-```
+If config file is missing: read `CLAUDE.md` for framework info. Assume "unknown" if neither source has it.
+
+For dependency audit command: infer from `packageManager` field in `package.json` or the lockfile (e.g., `npm audit`, `yarn audit`, `pnpm audit`).
 
 ## Execution Steps
 
@@ -67,7 +64,7 @@ Task("Security scan: src/shared/api/", subagent_type: general-purpose)
 - Session management vulnerabilities
 
 #### C. Sensitive Data Exposure (A02:2021)
-- `.env` values exposed to the client (check framework-specific public env variables for {config.framework})
+- `.env` values exposed to the client (check framework-specific public env variables from Project Context)
 - Sensitive information printed via console.log
 - Internal details exposed in error messages
 
@@ -108,7 +105,7 @@ Task("Security scan: src/shared/api/", subagent_type: general-purpose)
 - **Mitigation**: {how to fix}
 
 ### Dependency Audit
-{config.auditCmd} result summary — if executable
+{dependency audit command result summary — if executable}
 
 ### Recommended Actions
 {prioritized fix suggestions}
@@ -128,4 +125,4 @@ Security scan complete
 - **Read-only**: Does not modify code. Reports security issues only.
 - **Minimize false positives**: Account for React's default XSS defenses. Report only genuinely dangerous patterns.
 - **Handle sensitive data carefully**: Do not include actual token or password values in scan results.
-- **Consider context**: Reflect security specifics for the {config.framework} environment.
+- **Consider context**: Reflect security specifics for the project's framework environment (from Project Context).

package/commands/test.md

@@ -34,9 +34,9 @@ If config file is missing:
 3. If user declines → **abort**
 
 Values used from config:
-- `{config.testing}` — test framework (jest, vitest, playwright, etc.)
-- `{config.architecture}` — architecture pattern
-- `{config.gate}` — CI validation command
+- `{config.gate}` — CI validation command (from `## CI Commands` YAML)
+- `{config.architecture}` — architecture pattern (from `## Architecture` section)
+- Test framework info — from `## Project Context` section
 
 ## Execution Steps
 
@@ -63,7 +63,7 @@ Values used from config:
 ```markdown
 ### Test Strategy
 - Target: {file/feature}
-- Framework: {config.testing}
+- Framework: {test framework from Project Context}
 - Test types:
   - [ ] Unit tests: {list of target functions/methods}
   - [ ] Integration tests: {component interactions}

package/docs/phase-gate-protocol.md

@@ -17,7 +17,7 @@ After each Phase completes, perform **3-step verification** sequentially:
 
 ## Step 2. Mini-Review
 
-Quantitatively inspect `{config.mini_review}` items for files changed within the Phase:
+Quantitatively inspect changed files within the Phase against `{config.code_style}` and `{config.architecture}` rules:
 - List changed files and perform the inspection **for each file**
 - Output format:
   ```

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "all-for-claudecode",
-  "version": "2.1.0",
-  "description": "Claude Code plugin that automates the full dev cycle — spec, plan, tasks, implement, review, clean. 18 commands, 17 hooks, 5 presets.",
+  "version": "2.2.0",
+  "description": "Claude Code plugin that automates the full dev cycle — spec, plan, implement, review, clean.",
   "bin": {
     "all-for-claudecode": "bin/cli.mjs"
   },
@@ -34,7 +34,7 @@
     "url": "https://github.com/jhlee0409/all-for-claudecode/issues"
   },
   "scripts": {
-    "lint": "shellcheck -x --source-path=scripts scripts/*.sh && bash scripts/afc-schema-validate.sh --all",
+    "lint": "shellcheck -x --source-path=scripts scripts/*.sh && bash scripts/afc-schema-validate.sh --all && bash scripts/afc-consistency-check.sh",
     "test": "vendor/shellspec/shellspec",
     "test:all": "npm run lint && npm run test",
     "setup:test": "bash scripts/install-shellspec.sh"
@@ -46,19 +46,25 @@
     "claude-code",
     "claude-code-plugin",
     "claude-code-plugins",
-    "plugin",
+    "claude-plugin",
+    "anthropic",
     "pipeline",
     "automation",
+    "workflow-automation",
+    "development-workflow",
+    "sdlc-automation",
     "hooks",
     "slash-commands",
     "developer-tools",
     "ai-agents",
     "agentic-coding",
+    "ai-coding",
     "code-review",
-    "spec",
-    "plan",
-    "implement",
-    "review",
-    "critic-loop"
+    "code-generation",
+    "quality-gates",
+    "ci-gates",
+    "critic-loop",
+    "task-orchestration",
+    "spec-driven-development"
   ]
 }