@accelerationguy/accel 1.0.0

package/modules/drive/src/commands/plan-fix.md

@@ -0,0 +1,216 @@
+---
+name: drive:plan-fix
+description: Plan fixes for UAT issues from verify
+argument-hint: "<plan, e.g., '04-02'>"
+allowed-tools: [Read, Bash, Write, Glob, Grep, AskUserQuestion]
+---
+
+<objective>
+Create FIX.md plan from UAT issues found during verify.
+
+**When to use:** After `/drive:verify` logs issues to phase-scoped UAT file.
+
+**Output:** `{plan}-FIX.md` in the phase directory, ready for execution.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/references/plan-format.md
+@~/.claude/drive-framework/references/checkpoints.md
+</execution_context>
+
+<context>
+Plan number: $ARGUMENTS (required - e.g., "04-02" or "10-01")
+
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+
+<step name="parse">
+**Parse plan argument:**
+
+$ARGUMENTS should be a plan number like "04-02" or "10-01".
+Extract phase number (XX) and plan number (NN).
+
+If no argument provided:
+```
+Error: Plan number required.
+
+Usage: /drive:plan-fix 04-02
+
+This creates a fix plan from .drive/phases/XX-name/{plan}-UAT.md
+```
+Exit.
+</step>
+
+<step name="find">
+**Find UAT.md file:**
+
+Search for matching UAT file:
+```bash
+ls .drive/phases/*/{plan}-UAT.md 2>/dev/null
+```
+
+If not found:
+```
+No UAT.md found for plan {plan}.
+
+UAT.md files are created by /drive:verify when testing finds issues.
+If no issues were found during testing, no fix plan is needed.
+```
+Exit.
+</step>
+
+<step name="read">
+**Read issues:**
+
+Read the UAT.md file.
+Parse each issue:
+- ID (UAT-NNN)
+- Title
+- Severity (Blocker/Major/Minor/Cosmetic)
+- Description/steps to reproduce
+- AC reference
+
+Count total issues by severity.
+</step>
+
+<step name="plan">
+**Create fix tasks:**
+
+For each issue (or logical group):
+- Create one task per issue OR
+- Group related minor issues into single task
+
+Task structure:
+```xml
+<task type="auto">
+  <name>Fix UAT-001: [issue title]</name>
+  <files>[affected files from issue]</files>
+  <action>
+[What to fix based on issue description]
+[Reference original acceptance criteria]
+  </action>
+  <verify>[Test that issue is resolved]</verify>
+  <done>[Issue acceptance criteria met]</done>
+</task>
+```
+
+Prioritize: Blocker → Major → Minor → Cosmetic
+</step>
+
+<step name="write">
+**Write FIX.md:**
+
+Create `.drive/phases/XX-name/{plan}-FIX.md`:
+
+```markdown
+---
+phase: XX-name
+plan: {plan}-FIX
+type: fix
+wave: 1
+depends_on: []
+files_modified: [files from issues]
+autonomous: true
+---
+
+<objective>
+## Goal
+Fix {N} UAT issues from plan {plan}.
+
+## Purpose
+Address issues discovered during user acceptance testing.
+
+## Output
+All issues resolved, ready for re-verification.
+
+Source: {plan}-UAT.md
+Priority: {blocker count} blocker, {major count} major, {minor count} minor, {cosmetic count} cosmetic
+</objective>
+
+<context>
+@.drive/STATE.md
+@.drive/ROADMAP.md
+
+**Issues being fixed:**
+@.drive/phases/XX-name/{plan}-UAT.md
+
+**Original plan for reference:**
+@.drive/phases/XX-name/{plan}-PLAN.md
+</context>
+
+<acceptance_criteria>
+[Generate AC from issues - each issue becomes an AC]
+</acceptance_criteria>
+
+<tasks>
+[Generated fix tasks]
+</tasks>
+
+<boundaries>
+## DO NOT CHANGE
+- Files not related to the issues
+- Core functionality that passed testing
+
+## SCOPE LIMITS
+- Only fix issues from {plan}-UAT.md
+- No scope creep or additional improvements
+</boundaries>
+
+<verification>
+Before declaring plan complete:
+- [ ] All blocker issues fixed
+- [ ] All major issues fixed
+- [ ] Minor/cosmetic issues fixed or documented as deferred
+- [ ] Original acceptance criteria from issues met
+</verification>
+
+<success_criteria>
+- All UAT issues from {plan}-UAT.md addressed
+- Ready for re-verification with /drive:verify
+</success_criteria>
+
+<output>
+After completion, create `.drive/phases/XX-name/{plan}-FIX-SUMMARY.md`
+</output>
+```
+</step>
+
+<step name="offer">
+**Offer execution:**
+
+```
+════════════════════════════════════════
+FIX PLAN CREATED
+════════════════════════════════════════
+
+{plan}-FIX.md — {N} issues to fix
+
+| Severity | Count |
+|----------|-------|
+| Blocker  | {n}   |
+| Major    | {n}   |
+| Minor    | {n}   |
+| Cosmetic | {n}   |
+
+────────────────────────────────────────
+Continue to APPLY?
+
+[1] Approved, run APPLY | [2] Review first | [3] Pause here
+────────────────────────────────────────
+```
+
+Use AskUserQuestion to get response.
+If approved: `/drive:apply .drive/phases/XX-name/{plan}-FIX.md`
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] UAT.md found and parsed
+- [ ] Fix tasks created for each issue (or grouped)
+- [ ] FIX.md written with proper Drive structure
+- [ ] User offered to execute or review
+</success_criteria>

package/modules/drive/src/commands/plan.md

@@ -0,0 +1,36 @@
+---
+name: drive:plan
+description: Enter PLAN phase for current or new plan
+argument-hint: "[phase-plan]"
+allowed-tools: [Read, Write, Glob, AskUserQuestion]
+---
+
+<objective>
+Create or continue a PLAN for the specified phase.
+
+**When to use:** Starting new work or resuming incomplete plan.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/plan-phase.md
+@~/.claude/drive-framework/templates/PLAN.md
+@~/.claude/drive-framework/references/plan-format.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+
+@.drive/PROJECT.md
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+Follow workflow: @~/.claude/drive-framework/workflows/plan-phase.md
+</process>
+
+<success_criteria>
+- [ ] PLAN.md created in correct phase directory
+- [ ] All acceptance criteria defined
+- [ ] STATE.md updated with loop position
+</success_criteria>

package/modules/drive/src/commands/progress.md

@@ -0,0 +1,138 @@
+---
+name: drive:progress
+description: Smart status with routing - suggests ONE next action
+argument-hint: "[context]"
+allowed-tools: [Read]
+---
+
+<objective>
+Show current progress and **route to exactly ONE next action**. Prevents decision fatigue by suggesting a single best path.
+
+**When to use:**
+- Mid-session check on progress
+- After `/drive:resume` for more context
+- When unsure what to do next
+- To get a tailored suggestion based on your current focus
+</objective>
+
+<execution_context>
+</execution_context>
+
+<context>
+$ARGUMENTS
+
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+
+<step name="load_state">
+Read `.drive/STATE.md` and `.drive/ROADMAP.md`:
+- Current phase and total phases
+- Current plan (if any)
+- Loop position (PLAN/APPLY/UNIFY markers)
+- Roadmap progress
+- Performance metrics (if tracked)
+- Blockers or concerns
+
+Also check `.drive/config.md` (if exists):
+- Is `enterprise_plan_audit: enabled: true`?
+- If plan is at "created, awaiting approval" stage: check if STATE.md mentions "audited"
+- Store `audit_enabled` and `audit_completed` flags for routing
+</step>
+
+<step name="calculate_progress">
+Determine overall progress:
+
+**Milestone Progress:**
+- Phases complete: X of Y
+- Current phase progress: Z%
+
+**Current Loop:**
+- Position: PLAN/APPLY/UNIFY
+- Status: [what's happening]
+</step>
+
+<step name="consider_user_context">
+**If `[context]` argument provided:**
+
+User has given additional context about their current focus or constraint.
+Factor this into routing decision:
+- "I need to fix a bug first" → prioritize that over planned work
+- "I only have 30 minutes" → suggest smaller scope
+- "I want to finish this phase" → stay on current path
+- "I'm stuck on X" → suggest debug or research approach
+
+**If no argument:** Use default routing based on state alone.
+</step>
+
+<step name="determine_routing">
+Based on state (+ user context if provided), determine **ONE** next action:
+
+**Default routing (no user context):**
+
+| Situation | Single Suggestion |
+|-----------|-------------------|
+| No plan exists | `/drive:plan` |
+| Plan awaiting approval (audit enabled, not yet audited) | `/drive:audit [path]` |
+| Plan awaiting approval (audit complete or not enabled) | "Approve plan to proceed" |
+| Plan approved, not executed | `/drive:apply [path]` |
+| Applied, not unified | `/drive:unify [path]` |
+| Loop complete, more phases | `/drive:plan` (next phase) |
+| Milestone complete | "Create next milestone or ship" |
+| Blockers present | "Address blocker: [specific]" |
+| Context at DEEP/CRITICAL | `/drive:pause` |
+
+**With user context:** Adjust suggestion to align with stated intent.
+
+**IMPORTANT:** Suggest exactly ONE action. Not multiple options.
+</step>
+
+<step name="display_progress">
+Show progress with single routing:
+
+```
+════════════════════════════════════════
+Drive PROGRESS
+════════════════════════════════════════
+
+Milestone: [name] - [X]% complete
+├── Phase 1: [name] ████████████ Done
+├── Phase 2: [name] ████████░░░░ 70%
+├── Phase 3: [name] ░░░░░░░░░░░░ Pending
+└── Phase 4: [name] ░░░░░░░░░░░░ Pending
+
+Current Loop: Phase 2, Plan 02-03
+┌─────────────────────────────────────┐
+│  PLAN ──▶ APPLY ──▶ UNIFY          │
+│    ✓        ✓        ○             │
+└─────────────────────────────────────┘
+
+────────────────────────────────────────
+▶ NEXT: /drive:unify .drive/phases/02-features/02-03-PLAN.md
+  Close the loop and update state.
+────────────────────────────────────────
+
+Type "yes" to proceed, or provide context for a different suggestion.
+```
+</step>
+
+<step name="context_advisory">
+If context is at DEEP or CRITICAL bracket:
+
+```
+⚠️ Context Advisory: Session at [X]% capacity.
+   Recommended: /drive:pause before continuing.
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Overall progress displayed visually
+- [ ] Current loop position shown
+- [ ] Exactly ONE next action suggested (not multiple)
+- [ ] User context considered if provided
+- [ ] Context advisory shown if needed
+</success_criteria>

package/modules/drive/src/commands/register.md

@@ -0,0 +1,29 @@
+---
+name: drive:register
+description: Generate drive.json for an existing Drive project that predates v1.1 satellite manifest support
+argument-hint:
+allowed-tools: [Read, Write, Bash]
+---
+
+<objective>
+Generate `.drive/drive.json` for an existing project that has a `.drive/` directory but no satellite manifest.
+
+**When to use:** Projects initialized before drive-framework v1.1 that are missing `drive.json`. Required for Momentum satellite auto-detection to discover and register the project.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/register-manifest.md
+</execution_context>
+
+<context>
+Current directory (check for .drive/ and existing drive.json)
+</context>
+
+<process>
+Follow workflow: @~/.claude/drive-framework/workflows/register-manifest.md
+</process>
+
+<success_criteria>
+- [ ] .drive/drive.json created with correct project name and current state
+- [ ] User confirmed Momentum will detect the project on next session start
+</success_criteria>

package/modules/drive/src/commands/remove-phase.md

@@ -0,0 +1,37 @@
+---
+name: drive:remove-phase
+description: Remove a future (not started) phase
+argument-hint: "<phase-number-or-name>"
+allowed-tools: [Read, Write, Edit, Bash]
+---
+
+<objective>
+Remove a future phase from the roadmap and clean up its directory.
+
+**When to use:** Scope reduction, removing phases that haven't started.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/roadmap-management.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+
+@.drive/PROJECT.md
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+Follow workflow: @~/.claude/drive-framework/workflows/roadmap-management.md
+
+Execute: **remove-phase** operation
+</process>
+
+<success_criteria>
+- [ ] Phase removed from ROADMAP.md
+- [ ] Phase directory cleaned up (if empty)
+- [ ] Subsequent phases renumbered
+- [ ] STATE.md updated
+</success_criteria>

package/modules/drive/src/commands/research-phase.md

@@ -0,0 +1,209 @@
+---
+name: drive:research-phase
+description: Research unknowns for a phase using subagents
+argument-hint: "<phase-number>"
+allowed-tools: [Read, Task, Bash, Write]
+---
+
+<objective>
+Analyze a phase for unknowns and research them using subagents.
+
+**When to use:** Before planning a phase when there are technical unknowns that need investigation.
+
+**Distinction from /drive:research:**
+- `/drive:research <topic>`: User knows what to research
+- `/drive:research-phase <N>`: Claude identifies what needs researching
+
+**Subagent orchestration:** Spawns multiple research agents in parallel for independent unknowns.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/research.md
+@~/.claude/drive-framework/references/subagent-criteria.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS (required)
+
+@.drive/PROJECT.md
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+
+<step name="validate_phase" priority="first">
+1. Parse phase number from $ARGUMENTS
+
+**If argument missing:**
+```
+Error: Phase number required.
+
+Usage: /drive:research-phase <phase-number>
+Example: /drive:research-phase 10
+```
+Exit workflow.
+
+2. Validate phase exists in ROADMAP.md
+3. Extract phase scope, goals, and description
+
+**If phase not found:**
+```
+Error: Phase {N} not found in roadmap.
+
+Available phases:
+[list incomplete phases from roadmap]
+```
+Exit workflow.
+</step>
+
+<step name="analyze_unknowns">
+Analyze the phase for research needs:
+
+1. Read ROADMAP.md phase description
+2. Read PROJECT.md for context
+3. Check for existing CONTEXT.md in phase directory
+
+**Identify unknowns in these categories:**
+
+| Category | Examples |
+|----------|----------|
+| **Codebase** | "How does X work in this project?", patterns to follow |
+| **Web/Docs** | Library features, API patterns, best practices |
+| **Comparison** | "Should we use X or Y?", tradeoff analysis |
+| **Architecture** | Design patterns, integration approaches |
+
+**Classification logic:**
+- Codebase unknowns → Explore agent
+- Web/docs unknowns → general-purpose agent
+
+**Filter for substantial unknowns:**
+- Only include items that need 15+ min research
+- Trivial lookups handled in main session
+- Max 3 parallel research agents (token efficiency)
+
+**Present findings:**
+```
+════════════════════════════════════════
+PHASE UNKNOWNS ANALYSIS
+════════════════════════════════════════
+
+Phase: {N} — {phase_name}
+
+Identified unknowns:
+1. {unknown_1} [{codebase|web}]
+2. {unknown_2} [{codebase|web}]
+3. {unknown_3} [{codebase|web}]
+
+{If more than 3:}
+Additional unknowns (will research after initial batch):
+4. {unknown_4}
+5. {unknown_5}
+
+────────────────────────────────────────
+Proceed with research? [yes/no/modify list]
+────────────────────────────────────────
+```
+
+Wait for user confirmation.
+</step>
+
+<step name="spawn_research_agents">
+**Subagent criteria validation (from subagent-criteria.md):**
+
+| Criterion | Check |
+|-----------|-------|
+| Task Independence | Each unknown is self-contained ✓ |
+| Clear Scope | Unknown defines research question ✓ |
+| Parallel Value | Multiple agents run simultaneously ✓ |
+| Complexity Sweet Spot | Each 15-30 min expected ✓ |
+| Token Efficiency | Batch spawn, consolidated return ✓ |
+| State Compatibility | No blocking checkpoints ✓ |
+
+**Spawn agents in parallel:**
+
+Use multiple Task tool calls in single message:
+
+```
+Task 1 (Codebase unknowns):
+- subagent_type: Explore
+- description: "Research: {unknown}"
+- run_in_background: true (if multiple)
+- prompt: [research prompt]
+
+Task 2 (Web unknowns):
+- subagent_type: general-purpose
+- description: "Research: {unknown}"
+- run_in_background: true (if multiple)
+- prompt: [research prompt]
+```
+
+Display:
+```
+Spawning {N} research agents...
+
+Agent 1: {unknown_1} (Explore)
+Agent 2: {unknown_2} (general-purpose)
+Agent 3: {unknown_3} (Explore)
+
+Researching in parallel. This may take a few minutes...
+```
+</step>
+
+<step name="consolidate_findings">
+When all agents complete:
+
+1. Create research directory for phase:
+   ```bash
+   mkdir -p .drive/phases/{NN}-{name}/research
+   ```
+
+2. Save individual findings:
+   - `.drive/phases/{NN}-{name}/research/{unknown-slug}.md`
+
+3. Create consolidated RESEARCH.md:
+   - `.drive/phases/{NN}-{name}/RESEARCH.md`
+   - Summarizes all findings
+   - Links to individual research files
+
+4. Present summary:
+```
+════════════════════════════════════════
+PHASE RESEARCH COMPLETE
+════════════════════════════════════════
+
+Phase: {N} — {phase_name}
+Unknowns researched: {count}
+
+Summary:
+1. {unknown_1}: {key finding}
+2. {unknown_2}: {key finding}
+3. {unknown_3}: {key finding}
+
+Detailed findings:
+- .drive/phases/{NN}-{name}/RESEARCH.md (consolidated)
+- .drive/phases/{NN}-{name}/research/*.md (individual)
+
+────────────────────────────────────────
+Review the findings above. This research informs but does not
+automatically integrate into plans.
+
+What's next?
+[1] Review consolidated findings
+[2] Plan this phase (/drive:plan)
+[3] Discuss this phase (/drive:discuss)
+[4] Done for now
+────────────────────────────────────────
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Phase validated against ROADMAP.md
+- [ ] Unknowns identified and classified
+- [ ] User confirmed research list
+- [ ] Appropriate agents spawned in parallel
+- [ ] Findings consolidated into phase RESEARCH.md
+- [ ] Summary presented for review
+</success_criteria>