@accelerationguy/accel 1.0.0

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

@@ -0,0 +1,175 @@
+<objective>
+Manage Drive project configuration and integrations. Create or update .drive/config.md at any point in the project lifecycle.
+</objective>
+
+<when_to_use>
+- Enable SonarQube after project init
+- Disable an integration
+- View current configuration
+- Change project settings
+</when_to_use>
+
+<process>
+
+**Step 1: Check for existing config**
+
+```bash
+ls .drive/config.md 2>/dev/null
+```
+
+**If config exists:**
+```
+Current configuration:
+
+[Display config.md contents]
+
+What would you like to do?
+[1] Enable/disable integration
+[2] View full config
+[3] Reset to defaults
+```
+
+**If config doesn't exist:**
+```
+No configuration found.
+
+Would you like to set up project configuration?
+[1] Yes, create config
+[2] Cancel
+```
+
+**Step 2: Handle user choice**
+
+**For new config or "Enable/disable integration":**
+
+```
+Available integrations:
+
+[1] SonarQube - Code quality scanning
+    Status: [enabled/disabled/not configured]
+[2] Enterprise Plan Audit - Architectural review gate
+    Status: [enabled/disabled/not configured]
+
+[3] Done - save and exit
+```
+
+**If user selects SonarQube:**
+
+```
+SonarQube integration:
+
+Current: [enabled/disabled/not configured]
+
+[1] Enable
+[2] Disable
+[3] Back
+```
+
+**If enabling:**
+- Prompt for project_key (default: directory name)
+- Create/update config.md with sonarqube.enabled = true
+
+**If disabling:**
+- Update config.md with sonarqube.enabled = false
+
+**If user selects Enterprise Plan Audit:**
+
+```
+Enterprise Plan Audit:
+
+Current: [enabled/disabled/not configured]
+
+[1] Enable
+[2] Disable
+[3] Back
+```
+
+**If enabling:**
+- Create/update config.md with enterprise_plan_audit.enabled = true
+- Inform: "After /drive:plan, you'll be prompted to run /drive:audit before APPLY."
+
+**If disabling:**
+- Update config.md with enterprise_plan_audit.enabled = false
+- Inform: "Plans will go directly from PLAN to APPLY without audit suggestion."
+
+**Step 3: Write config**
+
+Create or update `.drive/config.md`:
+
+```markdown
+# Project Config
+
+**Project:** [project_name]
+**Updated:** [timestamp]
+
+## Project Settings
+
+```yaml
+project:
+  name: [project_name]
+  version: [version or "0.0.0"]
+```
+
+## Integrations
+
+### SonarQube
+
+```yaml
+sonarqube:
+  enabled: [true/false]
+  project_key: [key]
+```
+
+### Enterprise Plan Audit
+
+```yaml
+enterprise_plan_audit:
+  enabled: [true/false]
+```
+
+## Preferences
+
+```yaml
+preferences:
+  auto_commit: false
+  verbose_output: false
+```
+
+---
+*Config updated: [timestamp]*
+```
+
+**Step 4: Confirm**
+
+```
+════════════════════════════════════════
+CONFIG UPDATED
+════════════════════════════════════════
+
+Integrations:
+  SonarQube: [enabled/disabled]
+  Enterprise Plan Audit: [enabled/disabled]
+
+Config saved to: .drive/config.md
+
+────────────────────────────────────────
+[If SonarQube just enabled:]
+▶ NEXT: /drive:quality-gate
+  Run your first code quality scan.
+
+[If Enterprise Plan Audit just enabled:]
+▶ Enterprise audit will run between PLAN and APPLY.
+  After /drive:plan, you'll be prompted to run /drive:audit.
+
+[Otherwise:]
+Configuration complete.
+────────────────────────────────────────
+```
+
+</process>
+
+<output>
+- `.drive/config.md` created or updated
+- Integration status changed as requested
+- Clear next steps if applicable
+</output>

package/modules/drive/src/commands/consider-issues.md

@@ -0,0 +1,41 @@
+---
+name: drive:consider-issues
+description: Review deferred issues with codebase context, triage and route
+allowed-tools: [Read, Bash, Grep, Glob, Edit, AskUserQuestion]
+---
+
+<objective>
+Review all open issues from ISSUES.md and phase-scoped UAT files with current codebase context. Identify resolved, urgent, and waiting issues. Prevents issue pile-up.
+
+**When to use:** Periodically or before milestone completion.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/consider-issues.md
+</execution_context>
+
+<context>
+@.drive/ISSUES.md (if exists)
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+**Follow workflow: @~/.claude/drive-framework/workflows/consider-issues.md**
+
+The workflow implements:
+1. Find all issue files (ISSUES.md, phase-scoped UAT files)
+2. Parse open issues (ISS-NNN, UAT-NNN format)
+3. Analyze each against codebase (resolved? urgent? natural-fit?)
+4. Present categorized report
+5. Offer actions (close resolved, insert urgent, note for planning)
+6. Update files as needed
+</process>
+
+<success_criteria>
+- [ ] All open issues analyzed against current codebase
+- [ ] Each issue categorized (resolved/urgent/natural-fit/can-wait)
+- [ ] Clear reasoning provided for each categorization
+- [ ] Actions offered based on findings
+- [ ] Files updated if user takes action
+</success_criteria>

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

@@ -0,0 +1,48 @@
+---
+name: drive:discover
+description: Research technical options before planning a phase
+argument-hint: "<phase or topic>"
+allowed-tools: [Read, Bash, Glob, Grep, WebSearch, WebFetch, Task, AskUserQuestion]
+---
+
+<objective>
+Execute discovery to inform planning decisions. Produces DISCOVERY.md with findings, recommendation, and confidence level.
+
+**When to use:** Before planning a phase with technical unknowns (library selection, architecture decisions, integration approaches).
+
+**Distinct from /drive:research:** Research is for gathering documentation/information. Discover is for making technical decisions.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/discovery.md
+@~/.claude/drive-framework/templates/DISCOVERY.md
+</execution_context>
+
+<context>
+$ARGUMENTS (phase number or topic)
+
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+**Follow workflow: @~/.claude/drive-framework/workflows/discovery.md**
+
+The workflow implements:
+1. Determine depth level (quick/standard/deep)
+2. Identify unknowns for the phase
+3. Research options using subagents
+4. Cross-verify findings
+5. Create DISCOVERY.md with recommendation
+6. Assign confidence level
+7. Route to planning when complete
+</process>
+
+<success_criteria>
+- [ ] Discovery depth determined
+- [ ] Unknowns identified
+- [ ] Options researched with sources
+- [ ] DISCOVERY.md created (for standard/deep)
+- [ ] Recommendation provided with confidence
+- [ ] Ready for /drive:plan
+</success_criteria>

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

@@ -0,0 +1,33 @@
+---
+name: drive:discuss-milestone
+description: Explore and articulate next milestone vision
+argument-hint: ""
+allowed-tools: [Read, Write, AskUserQuestion]
+---
+
+<objective>
+Facilitate vision discussion for the next milestone and create context handoff.
+
+**When to use:** Before creating a new milestone, when scope needs exploration.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/discuss-milestone.md
+</execution_context>
+
+<context>
+@.drive/PROJECT.md
+@.drive/STATE.md
+@.drive/ROADMAP.md
+@.drive/MILESTONES.md
+</context>
+
+<process>
+Follow workflow: @~/.claude/drive-framework/workflows/discuss-milestone.md
+</process>
+
+<success_criteria>
+- [ ] MILESTONE-CONTEXT.md created with vision
+- [ ] Key themes and goals articulated
+- [ ] Ready for /drive:milestone command
+</success_criteria>

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

@@ -0,0 +1,34 @@
+---
+name: drive:discuss
+description: Explore and articulate phase vision before planning
+argument-hint: "<phase-number>"
+allowed-tools: [Read, Write, AskUserQuestion]
+---
+
+<objective>
+Facilitate vision discussion for a specific phase and create context handoff.
+
+**When to use:** Before planning a phase, when goals and approach need exploration.
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/discuss-phase.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS (required)
+
+@.drive/PROJECT.md
+@.drive/STATE.md
+@.drive/ROADMAP.md
+</context>
+
+<process>
+Follow workflow: @~/.claude/drive-framework/workflows/discuss-phase.md
+</process>
+
+<success_criteria>
+- [ ] CONTEXT.md created in phase directory
+- [ ] Goals and approach articulated
+- [ ] Ready for /drive:plan command
+</success_criteria>

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

@@ -0,0 +1,73 @@
+---
+name: drive:flows
+description: Configure specialized workflow integrations
+argument-hint: "[add|audit|list]"
+allowed-tools: [Read, Write, Bash, Glob]
+---
+
+<objective>
+Configure, amend, or audit specialized skill integrations for a Drive project.
+
+**When to use:**
+- Setting up skill dependencies for a new project
+- Adding a skill mapping to an existing project
+- Checking if required skills were used in current phase
+- Viewing current skill configuration
+
+**Subcommands:**
+- (no argument): Full interactive configuration
+- `add`: Quick-add single skill mapping
+- `audit`: Check current phase against declared flows
+- `list`: Display current configuration
+</objective>
+
+<execution_context>
+@~/.claude/drive-framework/workflows/configure-special-flows.md
+@~/.claude/drive-framework/references/specialized-workflow-integration.md
+</execution_context>
+
+<context>
+Subcommand: $ARGUMENTS (optional)
+
+@.drive/PROJECT.md
+@.drive/STATE.md
+@.drive/SPECIAL-FLOWS.md (if exists)
+</context>
+
+<process>
+**Route based on argument:**
+
+**No argument (full configuration):**
+1. Follow @workflows/configure-special-flows.md
+2. Interactive skill discovery and mapping
+3. Generate .drive/SPECIAL-FLOWS.md
+4. Update PROJECT.md with quick reference
+
+**`add` (quick add):**
+1. Ask for skill name
+2. Ask for work type trigger
+3. Ask for priority (required/optional)
+4. Append to SPECIAL-FLOWS.md table
+5. Confirm addition
+
+**`audit` (check current phase):**
+1. Read .drive/SPECIAL-FLOWS.md
+2. Read .drive/STATE.md for current phase
+3. Check ROADMAP.md for phase skill requirements
+4. Display required skills for this phase
+5. Remind: "Verify invocations before UNIFY"
+
+**`list` (display configuration):**
+1. Read .drive/SPECIAL-FLOWS.md
+2. Display formatted summary:
+   - Project-level skills (with priority)
+   - Phase overrides
+   - Templates/assets count
+</process>
+
+<success_criteria>
+- [ ] SPECIAL-FLOWS.md created or updated (for config/add)
+- [ ] PROJECT.md quick reference updated (for config)
+- [ ] Current phase skills displayed (for audit)
+- [ ] Configuration summary shown (for list)
+</success_criteria>

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

@@ -0,0 +1,201 @@
+---
+name: drive:handoff
+description: Generate comprehensive session handoff document
+argument-hint: "[context notes]"
+allowed-tools: [Read, Write]
+---
+
+<objective>
+Generate a comprehensive handoff document synthesizing session activity, decisions, gaps, and next actions.
+
+**When to use:** End of session, context break, or when decisions need documentation.
+
+**Smart context:** Uses conversation context for decisions/gaps. Optional argument for additional notes.
+</objective>
+
+<execution_context>
+@.drive/STATE.md
+</execution_context>
+
+<context>
+Optional notes: $ARGUMENTS (decisions, gaps, thoughts inline)
+
+Session context is primary source - extract:
+- What was accomplished (file changes, plans executed)
+- Decisions made (explicit or implicit in conversation)
+- Questions asked and answered
+- Gaps identified
+- User's stated intentions
+</context>
+
+<process>
+
+<step name="gather_session_context" priority="first">
+**From STATE.md:**
+- Current phase and plan
+- Loop position
+- Last activity
+- Session continuity notes
+
+**From conversation context:**
+- Files created/modified this session
+- Commands executed
+- Decisions discussed (look for "I want", "let's do", "decision:", user preferences)
+- Questions raised (look for "?", "should we", "what about")
+- Gaps identified (look for "missing", "need", "gap", "TODO")
+- User's stated approach/thoughts
+
+**From optional $ARGUMENTS:**
+- Additional context user provided inline
+- Override or supplement detected context
+</step>
+
+<step name="synthesize">
+Combine Claude's observations with user input:
+
+1. **Session Accomplishments:**
+   - What was built/completed
+   - Plans executed
+   - Files created
+
+2. **Decisions Made:**
+   - Explicit decisions from conversation
+   - Implicit decisions (choices made without discussion)
+   - Rationale where stated
+
+3. **Gap Analysis:**
+   - Issues identified
+   - User's decision on each gap
+   - Effort estimates if discussed
+
+4. **Open Questions:**
+   - Unresolved items
+   - Items needing more discussion
+
+5. **Reference Files:**
+   - Files mentioned that will be needed
+   - Source files for next session
+</step>
+
+<step name="generate_handoff">
+Create `.drive/HANDOFF-{date}-{context}.md`:
+
+```markdown
+# Drive Session Handoff
+
+**Session:** {date} {start_time} - {end_time}
+**Phase:** {current_phase}
+**Context:** {brief description}
+
+---
+
+## Session Accomplishments
+
+{bulleted list of what was done}
+
+---
+
+## Decisions Made
+
+| Decision | Rationale | Impact |
+|----------|-----------|--------|
+| {decision} | {why} | {effect} |
+
+---
+
+## Gap Analysis with Decisions
+
+### {Gap Name}
+**Status:** CREATE / DEFER / INTENTIONAL
+**Notes:** {user's decision and reasoning}
+**Effort:** {if discussed}
+**Reference:** `@{source_file}`
+
+---
+
+## Open Questions
+
+{items needing resolution}
+
+---
+
+## Reference Files for Next Session
+
+```
+{list of @-references}
+```
+
+---
+
+## Prioritized Next Actions
+
+| Priority | Action | Effort |
+|----------|--------|--------|
+| 1 | {action} | {effort} |
+
+---
+
+## State Summary
+
+**Current:** {phase, plan, loop position}
+**Next:** {recommended next action}
+**Resume:** `/drive:resume` then read this handoff
+
+---
+
+*Handoff created: {timestamp}*
+```
+
+Display confirmation:
+```
+════════════════════════════════════════
+HANDOFF CREATED
+════════════════════════════════════════
+
+Saved: .drive/HANDOFF-{date}-{context}.md
+
+Includes:
+- {N} accomplishments
+- {N} decisions documented
+- {N} gaps with your decisions
+- {N} prioritized next actions
+
+Next session: /drive:resume → read handoff
+════════════════════════════════════════
+```
+</step>
+
+</process>
+
+<smart_context_detection>
+**Decision indicators in conversation:**
+- "I want to..." / "Let's do..."
+- "Decision:" / "My decision:"
+- "We should..." / "Go with..."
+- User providing definitive answers
+- Approval signals ("yes", "approved", "do it")
+
+**Gap indicators:**
+- "Missing..." / "We need..."
+- "GAP" / "TODO"
+- Questions about what doesn't exist
+
+**Thought indicators:**
+- "I think..." / "My thoughts:"
+- "Here's my take..."
+- User explaining reasoning
+
+**Priority indicators:**
+- Numbered lists from user
+- "First..." / "Most important..."
+- Effort/impact discussions
+</smart_context_detection>
+
+<success_criteria>
+- [ ] STATE.md read for current position
+- [ ] Session context extracted (not just prompted)
+- [ ] User's inline input incorporated
+- [ ] Structured handoff generated
+- [ ] Reference files included
+- [ ] Next actions prioritized
+</success_criteria>