ai-workflow-init 6.6.1 → 7.1.0

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

@@ -1,247 +0,0 @@
----
-name: beads-status
-description: Shows epic progress overview with task status, dependencies, and metrics.
----
-
-## Goal
-
-Display a comprehensive overview of the current epic's progress, including task status, dependency graph, and completion metrics.
-
-## Workflow Alignment
-
-- Provide clear, visual progress reporting.
-- Show actionable information (what's ready, what's blocked).
-- Quick command for status checks without claiming tasks.
-
----
-
-## Step 1: Determine Which Epic to Show
-
-### Option A: Current Epic Context Exists
-
-**Read:** `.beads/current-epic.json`
-
-If exists:
-- Use epic_id from context
-- Proceed to Step 2
-
-### Option B: No Current Context
-
-**Run:** `bd list --type epic --json`
-
-If single epic exists:
-- Use that epic automatically
-
-If multiple epics exist:
-
-```
-AskUserQuestion(questions=[{
-  question: "Which epic would you like to see status for?",
-  header: "Select Epic",
-  options: [
-    { label: "{epic-1-id}: {title}", description: "{X}/{Y} tasks complete" },
-    { label: "{epic-2-id}: {title}", description: "{X}/{Y} tasks complete" },
-    { label: "Show all epics", description: "Overview of all epics" }
-  ],
-  multiSelect: false
-}])
-```
-
-If no epics exist:
-
-```
-No epics found.
-
-To create an epic:
-  /beads-breakdown "feature description"
-  /beads-breakdown @docs/ai/requirements/req-xxx.md
-```
-
----
-
-## Step 2: Load Epic Data
-
-### 2a: Get Epic Details
-
-**Run:** `bd show {epic-id} --json`
-
-Extract:
-- Epic title, description
-- Creation date
-- Total tasks count
-
-### 2b: Get All Tasks
-
-**Run:** `bd list --parent {epic-id} --json`
-
-For each task, extract:
-- Task ID, title, priority
-- Status (open, in_progress, closed)
-- Blocked by (dependencies)
-- Assignee (if any)
-
-### 2c: Load Epic Plan (if exists)
-
-**Read:** `docs/ai/planning/epic-{name}.md`
-
-If exists:
-- Extract task-to-plan-doc mapping from Task Breakdown table
-- Note any architectural updates
-
----
-
-## Step 3: Calculate Metrics
-
-```javascript
-// Metrics calculation
-const total = tasks.length;
-const closed = tasks.filter(t => t.status === 'closed').length;
-const inProgress = tasks.filter(t => t.status === 'in_progress').length;
-const open = tasks.filter(t => t.status === 'open').length;
-const ready = tasks.filter(t => t.status === 'open' && t.blockedBy.length === 0).length;
-const blocked = tasks.filter(t => t.status === 'open' && t.blockedBy.length > 0).length;
-
-const completionPercent = Math.round((closed / total) * 100);
-```
-
----
-
-## Step 4: Display Status Report
-
-```
-═══════════════════════════════════════════════════════════════════
-                    EPIC STATUS: {epic-id}
-═══════════════════════════════════════════════════════════════════
-
-📋 {Epic Title}
-
-{If epic plan exists:}
-📄 Epic Plan: docs/ai/planning/epic-{name}.md
-{If requirement exists:}
-📝 Requirement: docs/ai/requirements/req-{name}.md
-
-───────────────────────────────────────────────────────────────────
-                         PROGRESS
-───────────────────────────────────────────────────────────────────
-
-[████████████░░░░░░░░] {completionPercent}% Complete
-
-  ✅ Completed:    {closed}/{total} tasks
-  🔄 In Progress:  {inProgress} tasks
-  📋 Open:         {open} tasks
-    ├─ Ready:      {ready} tasks
-    └─ Blocked:    {blocked} tasks
-
-───────────────────────────────────────────────────────────────────
-                         TASK LIST
-───────────────────────────────────────────────────────────────────
-
-{Group by status:}
-
-✅ COMPLETED ({closed})
-{For each closed task:}
-  ✓ {task-id} "{title}"
-    └─ Plan: {plan-doc or "N/A"}
-
-🔄 IN PROGRESS ({inProgress})
-{For each in_progress task:}
-  → {task-id} "{title}" (P{n})
-    ├─ Plan: {plan-doc or "Not created"}
-    └─ Blocks: {list of dependent tasks or "None"}
-
-📋 READY ({ready})
-{For each ready task:}
-  ○ {task-id} "{title}" (P{n})
-
-🚫 BLOCKED ({blocked})
-{For each blocked task:}
-  ✗ {task-id} "{title}" (P{n})
-    └─ Waiting for: {blocker-id} "{blocker-title}"
-
-───────────────────────────────────────────────────────────────────
-                      DEPENDENCY GRAPH
-───────────────────────────────────────────────────────────────────
-
-{ASCII dependency graph}
-
-✅ = completed, → = in_progress, ○ = ready, ✗ = blocked
-
-Example:
-✅ bd-auth.1 ──────────────────────┐
-                                   ▼
-○ bd-auth.3 ───▶ → bd-auth.2 ───▶ ✗ bd-auth.4
-                        │
-                        └──────▶ ✗ bd-auth.5
-
-───────────────────────────────────────────────────────────────────
-                       NEXT ACTIONS
-───────────────────────────────────────────────────────────────────
-
-{Based on current state:}
-
-{If in_progress exists:}
-Continue current work:
-  /execute-plan     → Resume {in-progress-task-id}
-  /beads-done       → Complete {in-progress-task-id}
-
-{If ready tasks exist:}
-Start new task:
-  /beads-next       → Claim from {ready} ready tasks
-
-{If all blocked:}
-Unblock tasks:
-  Review blocked tasks and their dependencies
-  Complete blocking tasks first
-
-{If all complete:}
-🎉 Epic complete! Close with:
-  bd close {epic-id} --reason "All tasks complete"
-
-═══════════════════════════════════════════════════════════════════
-```
-
----
-
-## Step 5: Optional Details
-
-If user wants more details:
-
-```
-AskUserQuestion(questions=[{
-  question: "Would you like more details?",
-  header: "Details",
-  options: [
-    { label: "View specific task", description: "Show full details of a task" },
-    { label: "View epic plan", description: "Open the epic plan document" },
-    { label: "Refresh status", description: "Reload latest status from Beads" },
-    { label: "Done", description: "Exit status view" }
-  ],
-  multiSelect: false
-}])
-```
-
----
-
-## Notes
-
-- **Quick overview**: Designed for fast status checks
-- **Visual progress**: Progress bar makes completion visible at a glance
-- **Actionable**: Always shows what can be done next
-- **Dependency awareness**: Shows blocking relationships clearly
-
-### Progress Bar Legend
-
-```
-[████████████░░░░░░░░] 60%
- └── Filled = Completed
-            └── Empty = Remaining
-```
-
-### Status Icons
-
-| Icon | Meaning |
-|------|---------|
-| ✅ / ✓ | Completed |
-| 🔄 / → | In Progress |
-| 📋 / ○ | Ready (open, not blocked) |
-| 🚫 / ✗ | Blocked |

package/.claude/commands/init-chat.md

@@ -1,38 +0,0 @@
----
-name: init-chat
-description: Initializes chat by loading and aligning to AGENTS.md project rules.
----
-
-## Goal
-
-Initialize a new chat by loading and aligning to `CLAUDE.md` so the AI agent consistently follows project rules (workflow, tooling, communication, language mirroring) from the first message.
-
-## What this command does
-
-1. Read `CLAUDE.md` and extract the actionable rules.
-2. Summarize responsibilities and constraints the agent must follow in this session.
-3. Confirm language-mirroring: respond in the user's chat language; default to English if the user's language is unclear or ambiguous.
-4. Acknowledge the 4-phase workflow and TODO discipline for future commands.
-
-## Steps
-
-1. Open and read `CLAUDE.md` (project root).
-2. Read `docs/ai/project/CODE_CONVENTIONS.md` and `docs/ai/project/PROJECT_STRUCTURE.md` if they exist in the repository.
-3. Produce a short confirmation in the chat including:
-   - Workflow alignment: Plan → Implement → Test → Review
-   - Tooling strategy: semantic search first; parallelize independent steps
-   - Communication: minimal Markdown; status updates; high-signal summaries; mirror user language (default English if unclear)
-   - Code presentation: code references for existing code; fenced blocks for new code
-   - TODO policy: create/update todos; keep only one `in_progress`
-4. If any section is missing or unclear, ask a single concise clarification question; otherwise proceed silently in future commands.
-
-## Output format (concise)
-
-- Use the language of the triggering user message (mirror). If ambiguous, use English.
-- One short paragraph confirming alignment + a 4–6 bullet checklist of the above items.
-- No code unless strictly needed.
-
-## Notes
-
-- This command is idempotent—safe to re-run at the start of any chat.
-- It does not modify existing files; it only sets expectations for subsequent commands.

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

@@ -1,208 +0,0 @@
----
-name: modify-plan
-description: Modify plan and code after implementation; support revert or apply new approach.
----
-
-## Goal
-
-Modify a feature plan after partial/full implementation. Support reverting to a previous git state or applying new requirement changes with both code and documentation sync.
-
-## Prerequisites
-
-- Feature name (kebab-case, e.g., `user-authentication`)
-- Planning doc exists: `docs/ai/planning/feature-{name}.md`
-- Git repo initialized (for tracking code state)
-
-## Workflow Alignment
-
-- Provide brief status updates (1–3 sentences) before/after important actions.
-- Update planning doc when making changes.
-- Do NOT auto-commit; user reviews all changes before pushing.
-
-## Step 1: Load Current State
-
-Ask for feature name (must be kebab-case).
-
-Load and summarize:
-
-1. **Planning doc**: Current goal, scope, implementation phases, completion status
-
-Display summary:
-
-```
-Feature: user-authentication
-Plan: Create user login + registration endpoints
-
-Implementation Progress:
-- Phase 1 (Database): Complete [x]
-  Files: src/db/schema.ts
-- Phase 2 (API Endpoints): In Progress [3/4]
-  Files: src/api/users.ts, src/api/auth.ts
-- Phase 3 (Frontend): Not Started [ ]
-  Files: src/components/Login.tsx
-
-Total files touched: 4
-```
-
-## Step 2: Scope of Change (Q&A)
-
-Ask user what's changing:
-
-**1. Type of modification:**
-a) Modify goal/scope (entire plan changes)
-b) Modify specific phase(s) (tactical change)
-c) Revert to previous approach (git reset)
-d) Other (describe)
-
-**2a. If modifying goal/scope:**
-
-- What's the new goal/scope?
-- How does it impact existing tasks?
-
-**2b. If modifying specific phase(s):**
-
-- Which phase(s)? (list by name)
-- What requirement/approach is changing?
-
-**2c. If reverting approach:**
-
-- Show last 5 commits; ask which to revert to
-- Or reset to specific phase (revert all code changes after phase X)?
-
-## Step 3: Apply Changes
-
-### Option A: Revert to Previous Git State
-
-If user selects revert:
-
-1. **Identify affected files & changes**:
-
-   - Parse planning doc; list all files modified in affected phase(s)
-   - Show file list that needs reverting:
-     ```
-     Files to revert (manual):
-     - src/api/users.ts (lines 45–120)
-     - src/db/schema.ts (lines 10–30)
-     - tests/api.test.ts (delete entire file)
-     ```
-
-2. **Manual revert guidance**:
-
-   - For MODIFIED files: show current state vs. target state (code snippets/line ranges)
-   - For DELETED files: ask user to delete manually
-   - Ask: "Ready to manually revert these files?"
-
-3. **If user confirms**:
-
-   - User manually reverts files (copy-paste old code back, undo in IDE, etc.)
-   - Update planning doc:
-
-     - Mark affected phases/tasks `[ ]` (reset to pending)
-     - Add "Modification History" entry:
-
-       ```
-       ## Modification History
-
-       ### Revert [Date]: {Reason}
-       - **Reverted phases**: Phase X, Y
-       - **Reason**: [user provided]
-       - **Files manually reverted**: [list]
-       - **Affected tasks reset**: [ ] Task 1, [ ] Task 2, ...
-       ```
-
-4. **Result**: Docs updated; tasks reset; ready to re-implement with new approach
-
-### Option B: Apply New Changes
-
-If user selects new approach:
-
-1. **Update planning doc**:
-
-   - Modify goal/scope section if changed
-   - Update affected task(s) with new approach
-   - Update pseudo-code to match new approach
-   - Add "Modification History" section:
-
-     ```
-     ## Modification History
-
-     ### Change [Date]: {Title}
-     - **Previous approach**: [original details]
-     - **New approach**: [new details]
-     - **Reason**: [user provided]
-     - **Affected phases**: Phase X, Y
-     ```
-
-2. **Update implementation phases**:
-
-   - For affected phases:
-     - Modify pseudo-code to match new approach
-     - Reset incomplete tasks `[ ]` (if approach changed significantly)
-   - Keep completed tasks as-is (do not re-implement)
-   - Update "Implementation Plan" section with new structure (files/logic outline)
-
-3. **Show git impact**:
-   - Highlight files that may need re-editing
-   - Ask: "Ready to re-implement with new approach?" (yes/no)
-
-## Step 4: Confirmation & Audit Trail
-
-Before finalizing, show:
-
-1. **Updated planning doc** snippet (modified sections)
-2. **Git state** (files that will be changed)
-
-Ask: **"Apply changes and update doc?"** (yes/no)
-
-If **yes**:
-
-- Save updated planning doc
-- If revert: `git status` shows reverted files (unstaged)
-- If new approach: doc updated; code changes staged for review
-
-If **no**:
-
-- Rollback changes to doc
-- Discard any temporary changes
-
-## Step 5: Next Actions
-
-**After manual revert**:
-
-- "Docs updated. Affected tasks reset to `[ ]`. Run `/execute-plan` to re-implement Phase X with new approach."
-
-**After apply new approach**:
-
-- If only pseudo-code/docs changed (no code revert needed): "Continue current phase with `/execute-plan`."
-- If code changes needed (revert old approach + implement new): "Manually update code files first, then run `/execute-plan`."
-- "When done, run `/code-review` to validate standards."
-
-## Important Notes
-
-- **Manual revert**: User manually reverts code files (no git reset); AI guides the process
-- **Multi-feature safe**: Works when implementing multiple features simultaneously (selective revert possible)
-- **Backward compatible**: Works with both phase-based and non-phase-based planning docs
-- **Audit trail**: "Modification History" section preserves decision rationale and affected files
-- **Idempotent**: Safe to re-run; modification history accumulates
-- **Safe defaults**: Asks confirmation before any changes; user always has final say
-
-## Example Flow
-
-```
-User: I want to modify plan
-Agent: Load state, show summary
-
-User: Revert Phase 2 (API Endpoints) - use different auth approach
-Agent: Identify affected files (src/api/users.ts, src/api/auth.ts)
-       Show current state vs. target state (pseudo-code + old implementation)
-       Ask: Ready to manually revert these files?
-
-User: Yes, I'll manually revert
-Agent: (User manually copies old code back or undoes changes in IDE)
-       Update planning doc:
-       - Mark Phase 2 tasks [ ] (reset)
-       - Add Modification History: Phase 2 reverted, reason: better auth strategy
-
-Agent: Phase 2 reset. Ready to re-implement with new auth approach?
-       Run: /execute-plan
-```