ai-workflow-init 6.6.1 → 7.0.0

package/.claude/commands/create-plan.md

@@ -15,47 +15,6 @@ Generate a single planning doc at `docs/ai/planning/feature-{name}.md` using the
 
 ---
 
-## Step 0: Check Beads Context (Optional Integration)
-
-> **Purpose**: Detect if this plan is for a Beads task. If so, link to epic and inherit context.
-
-**Read:** `.beads/current-task.json`
-
-**If file exists (Beads workflow active):**
-
-```json
-{
-  "task_id": "bd-auth.1",
-  "task_title": "Setup JWT infrastructure",
-  "epic_id": "bd-auth",
-  "epic_title": "User Authentication System",
-  "epic_plan": "docs/ai/planning/epic-auth-system.md"
-}
-```
-
-Set internal flags:
-- `BEADS_MODE = true`
-- `beads_task = task_id`
-- `beads_epic = epic_id`
-- `suggested_title = task_title`
-- `epic_plan_path = epic_plan`
-
-**If epic_plan exists:**
-- Read epic plan for architecture context
-- Extract relevant sections:
-  - Architecture overview (for codebase context)
-  - Key decisions (for constraints)
-  - Data flow (for understanding)
-- Use as additional context in Step 3 (Explore)
-
-**If file does not exist:**
-- `BEADS_MODE = false`
-- Proceed with normal workflow (no Beads integration)
-
-**Output:** Internal state set. No user-visible output for this step.
-
----
-
 ## Step 1: Analyze User Prompt
 
 **Parse user request to identify:**
@@ -339,38 +298,19 @@ Create the file automatically:
 
 - `docs/ai/planning/feature-{name}.md` - Use complete structure from `feature-template.md`
 
-**If BEADS_MODE = true:**
-- Add frontmatter with Beads metadata:
-  ```yaml
-  ---
-  beads_task: {task_id}
-  beads_epic: {epic_id}
-  epic_plan: {epic_plan_path}
-  ---
-  ```
-- Update Beads task with plan doc reference:
-  ```bash
-  bd update {task_id} --notes "plan: docs/ai/planning/feature-{name}.md"
-  ```
-
 **Notify user:** "Created plan with X phases: [Phase 1], [Phase 2], ..."
 
 ## Step 8: Next Actions
 
-**If BEADS_MODE = true:**
+**Suggest next command:**
+
 ```
 ✓ Created plan: docs/ai/planning/feature-{name}.md
-✓ Linked to Beads task: {task_id}
 
 Next steps:
-  /execute-plan    → Implement this task
-  /beads-status    → View epic progress
+  /execute-plan    → Implement this feature
 ```
 
-**If normal mode:**
-
-Suggest: `/execute-plan` to begin implementation.
-
 Implementation will be driven from `docs/ai/planning/feature-{name}.md`.
 
 Note: Test documentation will be created separately using the `writing-test` command.

package/.claude/commands/execute-plan.md

@@ -40,36 +40,6 @@ Expected speedup: 30-40% for context loading phase.
 
 ---
 
-## Step 0: Check Beads Context (Optional Integration)
-
-> **Purpose**: Detect if this plan is for a Beads task. If so, track for final suggestions.
-
-**Read:** `.beads/current-task.json`
-
-**If file exists (Beads workflow active):**
-
-```json
-{
-  "task_id": "bd-auth.1",
-  "task_title": "Setup JWT infrastructure",
-  "epic_id": "bd-auth",
-  "epic_title": "User Authentication System"
-}
-```
-
-Set internal flags:
-- `BEADS_MODE = true`
-- `beads_task_id = task_id`
-- `beads_task_title = task_title`
-
-**If file does not exist:**
-- `BEADS_MODE = false`
-- Proceed with normal workflow (no Beads integration)
-
-**Output:** Internal state set. No user-visible output for this step.
-
----
-
 ## Step 1: Gather Context
 
 **Tools:**
@@ -254,31 +224,20 @@ Only run after ALL phases are marked complete. If incomplete phases remain, skip
 
 ## Step 6: Next Actions
 
-**If BEADS_MODE = true AND all phases complete:**
+**If all phases complete:**
 
 ```
-✓ All phases complete for Beads task: {beads_task_id} "{beads_task_title}"
+✓ All phases complete!
 
 Next steps:
-  /beads-done           → Close task, sync to git, see next ready tasks
-  /beads-status         → View epic progress
-
-Optional quality checks:
   /code-review          → Verify against standards
   /writing-test         → Add test coverage
   /check-implementation → Validate alignment with plan
 ```
 
-**If BEADS_MODE = false AND all phases complete:**
-
-- Suggest running `code-review` to verify against standards
-- Suggest running `writing-test` if edge cases need coverage
-- Suggest running `check-implementation` to validate alignment with planning entries
-
-**If phases remain (both modes):**
+**If phases remain:**
 
 - User runs `/execute-plan` again; Phase detection (Step 1d) will resume correctly
-- **If BEADS_MODE = true:** Remind user task is still in_progress in Beads
 
 ## Notes
 

package/README.md

@@ -6,7 +6,7 @@ A standardized AI workflow system for modern AI coding assistants. Initialize st
 
 - **Multi-Platform Support**: Works with Cursor, GitHub Copilot, Claude Code, OpenCode, and Factory Droid
 - **Structured Workflows**: Plan → Implement → Test → Review methodology
-- **14 Pre-built Commands**: Create plans, execute tasks, run tests, code reviews, and more
+- **9 Pre-built Commands**: Create plans, execute tasks, run tests, code reviews, and more
 - **7 Reusable Skills**: Design fundamentals, accessibility, theme generation, quality checks
 - **Universal Standards**: `AGENTS.md` works across all AI tools
 - **Smart Installation**: Protected files, selective updates, no data loss
@@ -297,80 +297,9 @@ User: /sync-workflow
 
 ---
 
-## Beads Integration (Optional)
-
-[Beads](https://github.com/steveyegge/beads) is a lightweight issue tracker with first-class dependency support. This workflow integrates seamlessly with Beads for multi-session task management.
-
-### Setup Beads
-
-1. **Install Beads**: Follow the official docs at https://github.com/steveyegge/beads
-
-2. **Setup for Claude Code**:
-   ```bash
-   bd setup claude
-   ```
-
-3. **Verify installation**:
-   ```bash
-   bd doctor
-   ```
-
-### Beads Commands
-
-| Command | Description |
-|---------|-------------|
-| `/beads-breakdown` | Analyze feature → create epic with tasks and dependencies |
-| `/beads-create-epic-plan` | Create high-level epic plan document |
-| `/beads-next` | Show ready tasks, claim a task, set context |
-| `/beads-done` | Close task, sync to git, show next ready tasks |
-| `/beads-status` | Show epic progress, metrics, dependency graph |
-
----
-
 ## Workflow Examples
 
-### Workflow A: With Beads (Multi-session, Dependencies)
-
-Best for: Large features, team collaboration, work that spans multiple sessions.
-
-```
-┌──────────────┐    ┌───────────────────┐    ┌─────────────┐
-│ /beads-      │ → │ /beads-create-    │ → │ /beads-next │
-│ breakdown    │    │ epic-plan         │    │             │
-└──────────────┘    └───────────────────┘    └──────┬──────┘
-                                                    │
-┌──────────────┐    ┌───────────────────┐    ┌──────▼──────┐
-│ /beads-done  │ ← │ /execute-plan     │ ← │ /create-plan│
-│              │    │                   │    │             │
-└──────────────┘    └───────────────────┘    └─────────────┘
-       │
-       └──────→ Loop back to /beads-next for next task
-```
-
-```bash
-# 1. Break down feature into epic with tasks
-/beads-breakdown "User authentication with JWT"
-
-# 2. Create high-level epic plan (architecture, data flow)
-/beads-create-epic-plan
-
-# 3. Claim a ready task
-/beads-next
-
-# 4. Create detailed plan for claimed task
-/create-plan
-
-# 5. Implement the task
-/execute-plan jwt-infrastructure
-
-# 6. Complete task, sync, see next ready tasks
-/beads-done
-
-# 7. Repeat from step 3 for remaining tasks
-/beads-next
-```
-
-### Workflow B: Without Beads (Single-session)
+### Standard Workflow (Single-session)
 
 Best for: Small features, quick fixes, solo work.
 
@@ -396,20 +325,7 @@ Best for: Small features, quick fixes, solo work.
 /code-review
 ```
 
-### When to Use Which Workflow?
-
-| Scenario | Recommended Workflow |
-|----------|---------------------|
-| Feature takes < 1 session | **Without Beads** |
-| Feature spans multiple sessions | **With Beads** |
-| Multiple developers on same feature | **With Beads** |
-| Tasks have dependencies | **With Beads** |
-| Quick bug fix | **Without Beads** |
-| Complex epic with 5+ tasks | **With Beads** |
-
----
-
-### Example: Complex Requirements (Without Beads)
+### Example: Complex Requirements
 
 ```bash
 # 1. Clarify requirements first
@@ -425,7 +341,7 @@ Best for: Small features, quick fixes, solo work.
 /check-implementation checkout-flow
 ```
 
-### Example: Bug Fix with Tests (Without Beads)
+### Example: Bug Fix with Tests
 
 ```bash
 # 1. Quick plan for the fix

package/docs/ai/planning/epic-template.md

@@ -3,7 +3,6 @@
 Note: All content in this document must be written in English.
 
 ---
-beads_epic: {bd-xxx or null}
 requirement: {docs/ai/requirements/req-xxx.md or null}
 ---
 
@@ -46,15 +45,11 @@ requirement: {docs/ai/requirements/req-xxx.md or null}
 
 ## 3. Task Breakdown
 
-> **Note**: If using Beads, this table syncs with Beads via `bd` commands. If not using Beads, manage tasks manually.
-
 | # | Task | Priority | Status | Blocked By | Plan Doc |
 |---|------|----------|--------|------------|----------|
 | 1 | {Task title} | P{0-4} | {open/in_progress/closed} | {dependencies or -} | {feature-xxx.md or -} |
 | 2 | {Task title} | P{0-4} | {status} | Task 1 | {-} |
 
-<!-- If using Beads, replace # with Task ID (e.g., bd-xxx.1) -->
-
 ### Dependency Graph
 ```
 Task 1 ──────────────────────┐
@@ -62,8 +57,6 @@ Task 1 ──────────────────────┐
 Task 3 ───▶ Task 2 ───▶ Task 4
 ```
 
-<!-- If using Beads, replace Task # with bd-xxx.# -->
-
 ---
 
 ## 4. Data Flow

package/docs/ai/planning/feature-template.md

@@ -3,24 +3,9 @@
 Note: All content in this document must be written in English.
 
 ---
-beads_task: {bd-xxx.n or null}
-beads_epic: {bd-xxx or null}
 epic_plan: {docs/ai/planning/epic-xxx.md or null}
 ---
 
-## 0. Beads Context (Optional)
-
-> **Note**: This section is auto-generated when plan is created via `/beads-next` → `/create-plan` workflow. Delete if not using Beads.
-
-- **Epic**: {epic-id} "{Epic Title}"
-- **Task**: {task-id} "{Task Title}"
-- **Epic Plan**: [epic-{name}.md](epic-{name}.md)
-- **Status**: in_progress
-- **Blocked by**: {list or "none"}
-- **Blocks**: {list of dependent tasks or "none"}
-
----
-
 ## 0. Requirements Reference (Optional)
 
 - **Requirement Doc**: [req-{feature-name}.md](../requirements/req-{feature-name}.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-workflow-init",
-  "version": "6.6.1",
+  "version": "7.0.0",
   "description": "Initialize AI workflow docs & commands into any repo with one command",
   "bin": {
     "ai-workflow-init": "./cli.js"

package/.claude/commands/beads-breakdown.md

@@ -1,278 +0,0 @@
----
-name: beads-breakdown
-description: Analyzes feature/requirement and breaks down into Beads epic with tasks and dependencies.
----
-
-## Goal
-
-Analyze a feature description (user prompt, requirement file, or planning file) and break it down into a Beads epic with tasks and dependencies. Confirm with user before executing any `bd` commands.
-
-## Workflow Alignment
-
-- Provide brief status updates (1–3 sentences) before/after important actions.
-- ALWAYS confirm breakdown with user before executing `bd` commands.
-- Show exact commands that will be executed for transparency.
-
----
-
-## Step 1: Detect Input Source
-
-**Parse user input to identify source type:**
-
-1. **File reference detected** (starts with `@` or file path):
-   - Requirement file: `@docs/ai/requirements/req-{name}.md`
-   - Planning file: `@docs/ai/planning/feature-{name}.md`
-   - Read file and extract content
-
-2. **User prompt only**:
-   - Use prompt directly for analysis
-
-3. **Both file + prompt**:
-   - File provides base requirements
-   - Prompt provides additional context/focus
-
-**Tool:** Read(file_path=...) if file reference detected
-
-**Extract from file (if requirement doc):**
-- Problem Statement → Epic description
-- Functional Requirements (FR-xx) → Tasks
-- Non-Functional Requirements → Constraints/notes
-- Dependencies/Constraints → Task dependencies
-- Acceptance Criteria → Task acceptance criteria
-
-**Extract from file (if planning doc):**
-- Goal → Epic description
-- Implementation phases → Tasks
-- Phase dependencies → Task dependencies
-
----
-
-## Step 2: Analyze and Generate Breakdown
-
-**Generate epic structure:**
-
-1. **Epic title**: Concise name for the feature (e.g., "User Authentication System")
-
-2. **Tasks**: Break down into 3-10 tasks
-   - Each task should be independently plannable (1-3 phases when detailed)
-   - Task title: Action-oriented (e.g., "Setup JWT infrastructure")
-   - Priority: P0 (critical) to P4 (backlog)
-
-3. **Dependencies**: Identify blocking relationships
-   - Which tasks must complete before others can start?
-   - Which tasks can run in parallel?
-
-**Analysis guidelines:**
-- **Too granular**: If task takes < 1 hour → merge with related task
-- **Too large**: If task needs > 5 implementation phases → split further
-- **Parallel-friendly**: Maximize tasks that can run simultaneously
-
----
-
-## Step 3: Present Breakdown for Confirmation
-
-**Display proposed breakdown:**
-
-```
-## Proposed Epic Breakdown
-
-**Epic**: {Epic Title}
-**Source**: {file path or "user prompt"}
-**Description**: {1-2 sentence summary}
-
-### Tasks
-
-| # | Title | Priority | Blocked By | Notes |
-|---|-------|----------|------------|-------|
-| 1 | {Task title} | P{0-4} | - | {brief note} |
-| 2 | {Task title} | P{0-4} | Task 1 | {brief note} |
-| 3 | {Task title} | P{0-4} | - | {can parallel with 1} |
-| 4 | {Task title} | P{0-4} | Task 2 | {brief note} |
-
-### Dependency Graph
-
-```
-Task 1 ──────────────────────┐
-                             ▼
-Task 3 ───▶ Task 2 ───▶ Task 4
-```
-
-### Ready to Start (can run in parallel)
-- Task 1: {title}
-- Task 3: {title}
-
----
-
-### Commands to Execute
-
-```bash
-# Create Epic
-bd create "{Epic Title}" -p 0 --type epic
-
-# Create Tasks (after epic created, will use actual epic ID)
-bd create "{Task 1 title}" -p {priority} --parent {epic-id}
-bd create "{Task 2 title}" -p {priority} --parent {epic-id}
-bd create "{Task 3 title}" -p {priority} --parent {epic-id}
-bd create "{Task 4 title}" -p {priority} --parent {epic-id}
-
-# Set Dependencies
-bd dep add {task-2-id} {task-1-id}  # Task 2 blocked by Task 1
-bd dep add {task-4-id} {task-2-id}  # Task 4 blocked by Task 2
-
-# Sync to git
-bd sync
-```
-```
-
-**Ask for confirmation:**
-
-```
-AskUserQuestion(questions=[{
-  question: "Review the breakdown above. How would you like to proceed?",
-  header: "Confirm",
-  options: [
-    { label: "Execute breakdown", description: "Create epic and tasks in Beads with the structure shown above" },
-    { label: "Modify tasks", description: "I want to add, remove, or change tasks before creating" },
-    { label: "Cancel", description: "Don't create anything, I'll provide more context" }
-  ],
-  multiSelect: false
-}])
-```
-
----
-
-## Step 4: Handle User Response
-
-### If "Execute breakdown":
-
-Execute `bd` commands sequentially:
-
-```bash
-# 1. Create Epic
-bd create "{Epic Title}" -p 0 --type epic
-# Capture epic ID from output (e.g., bd-auth)
-
-# 2. Create Tasks (use actual epic ID)
-bd create "{Task 1}" -p {priority} --parent {epic-id}
-# Capture task ID (e.g., bd-auth.1)
-
-bd create "{Task 2}" -p {priority} --parent {epic-id}
-# Capture task ID (e.g., bd-auth.2)
-
-# ... repeat for all tasks
-
-# 3. Set Dependencies (use actual task IDs)
-bd dep add {task-2-id} {task-1-id}
-# ... repeat for all dependencies
-
-# 4. Sync
-bd sync
-```
-
-**Output summary:**
-
-```
-✓ Created Epic: {epic-id} "{Epic Title}"
-
-Tasks created:
-  ├── {task-1-id} "{Task 1}" [ready]
-  ├── {task-2-id} "{Task 2}" [blocked by {task-1-id}]
-  ├── {task-3-id} "{Task 3}" [ready]
-  └── {task-4-id} "{Task 4}" [blocked by {task-2-id}]
-
-Ready to start (parallel): {task-1-id}, {task-3-id}
-
-Next steps:
-  1. Run `/beads-create-epic-plan` to create high-level epic plan
-  2. Run `/beads-next` to claim a task and start working
-```
-
-### If "Modify tasks":
-
-Ask follow-up:
-
-```
-AskUserQuestion(questions=[{
-  question: "What would you like to modify?",
-  header: "Modify",
-  options: [
-    { label: "Add tasks", description: "Add more tasks to the breakdown" },
-    { label: "Remove tasks", description: "Remove some tasks" },
-    { label: "Change dependencies", description: "Modify blocking relationships" },
-    { label: "Change priorities", description: "Adjust task priorities" }
-  ],
-  multiSelect: true
-}])
-```
-
-Collect modifications and return to Step 3 with updated breakdown.
-
-### If "Cancel":
-
-```
-Breakdown cancelled.
-
-To try again with more context:
-  /beads-breakdown "more detailed description"
-  /beads-breakdown @docs/ai/requirements/req-{name}.md
-```
-
----
-
-## Step 5: Store Context for Next Commands
-
-After successful creation, store context for `/beads-create-epic-plan`:
-
-**File:** `.beads/current-epic.json`
-
-```json
-{
-  "epic_id": "{epic-id}",
-  "epic_title": "{Epic Title}",
-  "source_file": "{file path or null}",
-  "tasks": [
-    {
-      "id": "{task-1-id}",
-      "title": "{Task 1}",
-      "priority": 1,
-      "blocked_by": [],
-      "status": "open"
-    },
-    {
-      "id": "{task-2-id}",
-      "title": "{Task 2}",
-      "priority": 1,
-      "blocked_by": ["{task-1-id}"],
-      "status": "open"
-    }
-  ],
-  "created_at": "{ISO timestamp}"
-}
-```
-
----
-
-## Notes
-
-- **Confirmation required**: Never execute `bd` commands without user confirmation
-- **Idempotent**: Safe to re-run; will show current state if epic exists
-- **Source tracking**: Links back to requirement/planning doc if provided
-- **Parallel-friendly**: Breakdown should maximize parallel execution opportunities
-
-### Task Sizing Guidelines
-
-| Size | Description | When to use |
-|------|-------------|-------------|
-| Too small | < 1 hour, single function | Merge with related task |
-| Good | 2-8 hours, 1-3 phases | Ideal task size |
-| Too large | > 2 days, > 5 phases | Split into subtasks |
-
-### Priority Guidelines
-
-| Priority | Meaning | Use for |
-|----------|---------|---------|
-| P0 | Critical | Blockers, urgent fixes |
-| P1 | High | Core functionality |
-| P2 | Medium | Important but not blocking |
-| P3 | Low | Nice to have |
-| P4 | Backlog | Future consideration |