@accelerationguy/accel 1.0.0

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

@@ -0,0 +1,525 @@
+---
+name: drive:help
+description: Show available Drive commands and usage guide
+---
+
+<objective>
+Display the complete Drive command reference.
+
+Output ONLY the reference content below. Do NOT add:
+
+- Project-specific analysis
+- Git status or file context
+- Next-step suggestions
+- Any commentary beyond the reference
+</objective>
+
+<reference>
+# Drive Command Reference
+
+**Drive** (Plan-Apply-Unify Loop) is a structured AI-assisted development framework for Claude Code.
+
+## The Loop
+
+Every unit of work follows this cycle:
+
+```
+┌─────────────────────────────────────┐
+│  PLAN ──▶ APPLY ──▶ UNIFY          │
+│                                     │
+│  Define    Execute    Reconcile     │
+│  work      tasks      & close       │
+└─────────────────────────────────────┘
+```
+
+**Never skip UNIFY.** Every plan needs a summary.
+
+## Quick Start
+
+1. `/drive:init` - Initialize Drive in your project
+2. `/drive:plan` - Create a plan for your work
+3. `/drive:apply` - Execute the approved plan
+4. `/drive:unify` - Close the loop with summary
+
+## Commands Overview
+
+| Category | Commands |
+|----------|----------|
+| Core Loop | init, plan, apply, unify, help, status |
+| Session | pause, resume, progress, handoff |
+| Roadmap | add-phase, remove-phase |
+| Milestone | milestone, complete-milestone, discuss-milestone |
+| Pre-Planning | discuss, assumptions, discover, consider-issues |
+| Research | research, research-phase |
+| Specialized | flows, config, map-codebase |
+| Quality | verify, plan-fix, audit |
+
+---
+
+## Core Loop Commands
+
+### `/drive:init`
+Initialize Drive in a project.
+
+- Creates `.drive/` directory structure
+- Creates PROJECT.md, STATE.md, ROADMAP.md
+- Prompts for project context and phases
+- Optionally configures integrations (SonarQube, etc.)
+
+Usage: `/drive:init`
+
+---
+
+### `/drive:plan [phase]`
+Enter PLAN phase - create an executable plan.
+
+- Reads current state from STATE.md
+- Creates PLAN.md with tasks, acceptance criteria, boundaries
+- Populates skills section from SPECIAL-FLOWS.md (if configured)
+- Updates loop position
+
+Usage: `/drive:plan` (auto-detects next phase)
+Usage: `/drive:plan 3` (specific phase)
+
+---
+
+### `/drive:apply [plan-path]`
+Execute an approved PLAN.md file.
+
+- **Blocks if required skills not loaded** (from SPECIAL-FLOWS.md)
+- Validates plan exists and hasn't been executed
+- Executes tasks sequentially
+- Handles checkpoints (decision, human-verify, human-action)
+- Reports completion and prompts for UNIFY
+
+Usage: `/drive:apply`
+Usage: `/drive:apply .drive/phases/01-foundation/01-01-PLAN.md`
+
+---
+
+### `/drive:unify [plan-path]`
+Reconcile plan vs actual and close the loop.
+
+- Creates SUMMARY.md documenting what was built
+- Audits skill invocations (if SPECIAL-FLOWS.md configured)
+- Records decisions made, deferred issues
+- Updates STATE.md with loop closure
+- **Required** - never skip this step
+
+Usage: `/drive:unify`
+Usage: `/drive:unify .drive/phases/01-foundation/01-01-PLAN.md`
+
+---
+
+### `/drive:help`
+Show this command reference.
+
+Usage: `/drive:help`
+
+---
+
+### `/drive:status` *(deprecated)*
+> Use `/drive:progress` instead.
+
+Shows current loop position. Deprecated in favor of `/drive:progress` which provides better routing.
+
+---
+
+## Session Commands
+
+### `/drive:pause [reason]`
+Create handoff file and prepare for session break.
+
+- Creates HANDOFF.md with complete context
+- Updates STATE.md session continuity section
+- Designed for context limits or multi-session work
+
+Usage: `/drive:pause`
+Usage: `/drive:pause "switching to other project"`
+
+---
+
+### `/drive:resume [handoff-path]`
+Restore context from handoff and continue work.
+
+- Reads STATE.md and any HANDOFF files
+- Determines current loop position
+- Suggests exactly ONE next action
+- Archives consumed handoffs
+
+Usage: `/drive:resume`
+Usage: `/drive:resume .drive/HANDOFF-context.md`
+
+---
+
+### `/drive:progress [context]`
+Smart status with routing - suggests ONE next action.
+
+- Shows milestone and phase progress visually
+- Displays current loop position
+- Suggests exactly ONE next action (prevents decision fatigue)
+- Accepts optional context to tailor suggestion
+- Warns about context limits
+
+Usage: `/drive:progress`
+Usage: `/drive:progress "I only have 30 minutes"`
+
+---
+
+### `/drive:handoff [context]`
+Generate comprehensive session handoff document.
+
+- Creates detailed handoff for complex session breaks
+- Captures decisions, progress, blockers, next steps
+- More thorough than `/drive:pause`
+
+Usage: `/drive:handoff`
+Usage: `/drive:handoff "phase10-audit"`
+
+---
+
+## Roadmap Commands
+
+### `/drive:add-phase <description>`
+Append a new phase to the roadmap.
+
+- Adds phase to end of ROADMAP.md
+- Updates phase numbering
+- Records in STATE.md decisions
+
+Usage: `/drive:add-phase "API Authentication Layer"`
+
+---
+
+### `/drive:remove-phase <number>`
+Remove a future (not started) phase from roadmap.
+
+- Cannot remove completed or in-progress phases
+- Renumbers subsequent phases
+- Updates ROADMAP.md
+
+Usage: `/drive:remove-phase 5`
+
+---
+
+## Milestone Commands
+
+### `/drive:milestone <name>`
+Create a new milestone with phases.
+
+- Guides through milestone definition
+- Creates phase structure
+- Updates ROADMAP.md with milestone grouping
+
+Usage: `/drive:milestone "v2.0 API Redesign"`
+
+---
+
+### `/drive:complete-milestone [version]`
+Archive milestone, tag, and reorganize roadmap.
+
+- Verifies all phases complete
+- Creates git tag (if configured)
+- Archives milestone to MILESTONES.md
+- Evolves PROJECT.md for next milestone
+
+Usage: `/drive:complete-milestone`
+Usage: `/drive:complete-milestone v0.3`
+
+---
+
+### `/drive:discuss-milestone`
+Explore and articulate vision before starting a milestone.
+
+- Conversational exploration of goals
+- Creates milestone context document
+- Prepares for `/drive:milestone`
+
+Usage: `/drive:discuss-milestone`
+
+---
+
+## Pre-Planning Commands
+
+### `/drive:discuss <phase>`
+Articulate vision and explore approach before planning.
+
+- Conversational discussion of phase goals
+- Creates CONTEXT.md capturing vision
+- Prepares for `/drive:plan`
+
+Usage: `/drive:discuss 3`
+Usage: `/drive:discuss "authentication layer"`
+
+---
+
+### `/drive:assumptions <phase>`
+Surface Claude's assumptions about a phase before planning.
+
+- Shows what Claude would do if given free rein
+- Identifies gaps in understanding
+- Prevents misaligned planning
+
+Usage: `/drive:assumptions 3`
+
+---
+
+### `/drive:discover <topic>`
+Research technical options before planning a phase.
+
+- Explores codebase for relevant patterns
+- Documents findings for planning reference
+- Lightweight alternative to full research
+
+Usage: `/drive:discover "authentication patterns"`
+
+---
+
+### `/drive:consider-issues [source]`
+Review deferred issues with codebase context, triage and route.
+
+- Reads deferred issues from STATE.md or specified source
+- Analyzes with current codebase context
+- Suggests routing: fix now, defer, or close
+
+Usage: `/drive:consider-issues`
+
+---
+
+## Research Commands
+
+### `/drive:research <topic>`
+Deploy research agents for documentation/web search.
+
+- Spawns subagents for parallel research
+- Gathers external documentation
+- Creates RESEARCH.md with findings
+- Main session vets and reviews results
+
+Usage: `/drive:research "JWT best practices 2026"`
+
+---
+
+### `/drive:research-phase <number>`
+Research unknowns for a phase using subagents.
+
+- Identifies unknowns in phase scope
+- Deploys research agents
+- Synthesizes findings for planning
+
+Usage: `/drive:research-phase 4`
+
+---
+
+## Specialized Commands
+
+### `/drive:flows`
+Configure specialized workflow integrations.
+
+- Creates/updates SPECIAL-FLOWS.md
+- Defines required skills per work type
+- Skills are enforced at APPLY time
+
+Usage: `/drive:flows`
+
+---
+
+### `/drive:config`
+View or modify Drive configuration.
+
+- Shows current config.md settings
+- Allows toggling integrations
+- Manages project-level settings
+
+Usage: `/drive:config`
+
+---
+
+### `/drive:map-codebase`
+Generate codebase map for context.
+
+- Creates structured overview of project
+- Identifies key files and patterns
+- Useful for research and planning
+
+Usage: `/drive:map-codebase`
+
+---
+
+## Quality Commands
+
+### `/drive:verify`
+Guide manual user acceptance testing of recently built features.
+
+- Generates verification checklist from SUMMARY.md
+- Guides through manual testing
+- Records verification results
+
+Usage: `/drive:verify`
+
+---
+
+### `/drive:audit [plan-path]`
+Run enterprise-grade architectural audit on a plan.
+
+- Performs senior engineer + compliance review
+- Auto-applies must-have and strongly-recommended findings to plan
+- Creates AUDIT.md report in phase directory
+- Optional: enabled via `enterprise_plan_audit` in config
+
+Usage: `/drive:audit`
+Usage: `/drive:audit .drive/phases/20-ai-schema/20-01-PLAN.md`
+
+---
+
+### `/drive:plan-fix`
+Plan fixes for UAT issues from verify.
+
+- Reads issues identified during verify
+- Creates targeted fix plan
+- Smaller scope than full phase plan
+
+Usage: `/drive:plan-fix`
+
+---
+
+## Files & Structure
+
+```
+.drive/
+├── PROJECT.md           # Project context and value prop
+├── ROADMAP.md           # Phase breakdown and milestones
+├── STATE.md             # Loop position and session state
+├── config.md            # Optional integrations config
+├── SPECIAL-FLOWS.md     # Optional skill requirements
+├── MILESTONES.md        # Completed milestone archive
+└── phases/
+    ├── 01-foundation/
+    │   ├── 01-01-PLAN.md
+    │   ├── 01-01-AUDIT.md    (if enterprise audit enabled)
+    │   └── 01-01-SUMMARY.md
+    └── 02-features/
+        ├── 02-01-PLAN.md
+        ├── 02-01-AUDIT.md    (if enterprise audit enabled)
+        └── 02-01-SUMMARY.md
+```
+
+## PLAN.md Structure
+
+```markdown
+---
+phase: 01-foundation
+plan: 01
+type: execute
+autonomous: true
+---
+
+<objective>
+Goal, Purpose, Output
+</objective>
+
+<context>
+@-references to relevant files
+</context>
+
+<skills>
+Required skills from SPECIAL-FLOWS.md
+</skills>
+
+<acceptance_criteria>
+Given/When/Then format
+</acceptance_criteria>
+
+<tasks>
+<task type="auto">...</task>
+</tasks>
+
+<boundaries>
+DO NOT CHANGE, SCOPE LIMITS
+</boundaries>
+
+<verification>
+Completion checks
+</verification>
+```
+
+## Task Types
+
+| Type | Use For |
+|------|---------|
+| `auto` | Fully autonomous execution |
+| `checkpoint:decision` | Choices requiring human input |
+| `checkpoint:human-verify` | Visual/functional verification |
+| `checkpoint:human-action` | Manual steps (rare) |
+
+## Common Workflows
+
+**Starting a new project:**
+```
+/drive:init
+/drive:plan
+# Approve plan
+/drive:apply
+/drive:unify
+```
+
+**Enterprise workflow (with audit enabled):**
+```
+/drive:plan        # Create plan
+/drive:audit       # Audit + auto-fix plan
+# Approve audited plan
+/drive:apply       # Execute
+/drive:unify       # Close loop
+```
+
+**Checking where you are:**
+```
+/drive:progress   # State + ONE next action (recommended)
+```
+
+**Resuming work (new session):**
+```
+/drive:resume     # Restores context, suggests next action
+```
+
+**Pausing work (before break):**
+```
+/drive:pause      # Creates handoff, updates state
+```
+
+**Pre-planning exploration:**
+```
+/drive:discuss 3       # Articulate vision
+/drive:assumptions 3   # See Claude's assumptions
+/drive:research "topic"  # Gather external info
+/drive:plan 3          # Now create the plan
+```
+
+**Managing roadmap:**
+```
+/drive:add-phase "New Feature"    # Add phase
+/drive:remove-phase 5             # Remove future phase
+/drive:milestone "v2.0"           # Create milestone
+/drive:complete-milestone         # Archive milestone
+```
+
+## Key Principles
+
+1. **Loop must complete** - PLAN -> APPLY -> UNIFY, no shortcuts
+2. **Commands are thin** - Logic lives in workflows
+3. **State is tracked** - STATE.md knows where you are
+4. **Boundaries are real** - Respect DO NOT CHANGE sections
+5. **Acceptance criteria first** - Define done before starting
+6. **Skills are enforced** - Required skills block APPLY until loaded
+
+## Getting Help
+
+- Run `/drive:progress` to see where you are and what to do next
+- Read `.drive/PROJECT.md` for project context
+- Read `.drive/STATE.md` for current position
+- Check `.drive/ROADMAP.md` for phase overview
+
+---
+
+*Drive Framework v0.4+ | 26 commands | Last updated: 2026-01-29*
+</reference>

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

@@ -0,0 +1,54 @@
+---
+name: drive:init
+description: Initialize Drive in a project with conversational setup
+argument-hint:
+allowed-tools: [Read, Write, Bash, Glob, AskUserQuestion]
+---
+
+<objective>
+Initialize the `.drive/` structure in a project directory through conversational setup.
+
+**When to use:** Starting a new project with Drive, or adding Drive to an existing codebase.
+
+Creates PROJECT.md, STATE.md, and ROADMAP.md populated from conversation - user does not manually edit templates.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/init-project.md
+@~/.claude/drive-framework/templates/PROJECT.md
+@~/.claude/drive-framework/templates/STATE.md
+@~/.claude/drive-framework/templates/ROADMAP.md
+</execution_context>
+
+<context>
+Current directory state (check for existing .drive/)
+</context>
+
+<process>
+**Follow workflow: @~/.claude/drive-framework/workflows/init-project.md**
+
+The workflow implements conversational setup:
+
+1. Check for existing .drive/ (route to resume if exists)
+2. Create directory structure
+3. Ask: "What's the core value this project delivers?"
+4. Ask: "What are you building?"
+5. Confirm project name (infer from directory)
+6. Populate PROJECT.md, ROADMAP.md, STATE.md from answers
+7. Display ONE next action: `/drive:plan`
+
+**Key behaviors:**
+- Ask ONE question at a time
+- Wait for response before next question
+- Populate files from answers (user doesn't edit templates)
+- End with exactly ONE next action
+- Build momentum into planning phase
+</process>
+
+<success_criteria>
+- [ ] .drive/ directory created
+- [ ] PROJECT.md populated with core value and description from conversation
+- [ ] STATE.md initialized with correct loop position
+- [ ] ROADMAP.md initialized (phases TBD until planning)
+- [ ] User presented with ONE clear next action
+</success_criteria>

package/modules/drive/src/commands/map-codebase.md

@@ -0,0 +1,34 @@
+<objective>
+Analyze existing codebase and create structured documentation in .drive/codebase/
+
+Spawns parallel Explore agents to analyze technology stack, architecture, conventions, testing patterns, external integrations, and areas of concern.
+</objective>
+
+<execution_context>
+@src/workflows/map-codebase.md
+</execution_context>
+
+<process>
+**Follow workflow:** @src/workflows/map-codebase.md
+
+The workflow implements:
+1. Check if .drive/codebase/ exists (offer refresh/update/skip)
+2. Create directory structure
+3. Spawn 4 parallel Explore agents:
+   - Agent 1: Stack + Integrations (Technology Focus)
+   - Agent 2: Architecture + Structure (Organization Focus)
+   - Agent 3: Conventions + Testing (Quality Focus)
+   - Agent 4: Concerns (Issues Focus)
+4. Collect and aggregate agent findings
+5. Write 7 codebase documents from templates
+6. Verify and commit
+7. Offer next steps
+</process>
+
+<success_criteria>
+- [ ] .drive/codebase/ directory created
+- [ ] All 7 documents populated with findings
+- [ ] Documents include actual file paths (actionable)
+- [ ] Codebase map committed
+- [ ] User informed of next steps
+</success_criteria>

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

@@ -0,0 +1,34 @@
+---
+name: drive:milestone
+description: Create a new milestone in the project
+argument-hint: "[milestone-name]"
+allowed-tools: [Read, Write, Edit, Bash, Glob, AskUserQuestion]
+---
+
+<objective>
+Create a new milestone with defined scope and phases.
+
+**When to use:** Starting a new milestone cycle after completing the previous one.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/create-milestone.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+
+@.drive/PROJECT.md
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+Follow workflow: @~/.claude/drive-framework/workflows/create-milestone.md
+</process>
+
+<success_criteria>
+- [ ] Milestone created in MILESTONES.md
+- [ ] ROADMAP.md updated with milestone grouping
+- [ ] STATE.md reflects new milestone
+</success_criteria>

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

@@ -0,0 +1,44 @@
+---
+name: drive:pause
+description: Create handoff file and prepare for session break
+argument-hint: [reason]
+allowed-tools: [Read, Write, Bash, AskUserQuestion]
+---
+
+<objective>
+Create a HANDOFF.md file capturing current context and update STATE.md for session continuity.
+
+**When to use:** Before ending a session, switching context, or when context limit is approaching.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/pause-work.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+
+@.drive/STATE.md
+@.drive/PROJECT.md
+</context>
+
+<process>
+**Follow the pause-work workflow** from `@~/.claude/drive-framework/workflows/pause-work.md`.
+
+The workflow handles:
+1. Detecting current position
+2. Gathering session context (ask user if needed)
+3. Creating HANDOFF-{date}.md with populated content
+4. Updating STATE.md session continuity
+5. Optional WIP commit
+6. Confirmation display
+
+If `[reason]` argument provided, include it in handoff status.
+</process>
+
+<success_criteria>
+- [ ] HANDOFF.md created with complete context (no placeholders)
+- [ ] STATE.md updated with session continuity
+- [ ] Next action is clear and actionable
+- [ ] Resume instructions provided
+</success_criteria>