@accelerationguy/accel 1.0.0

package/modules/drive/src/workflows/resume-project.md

@@ -0,0 +1,200 @@
+<purpose>
+Resume Drive work after a session break. Reads STATE.md to restore context, determines current loop position, and routes to exactly ONE next action. Includes handoff lifecycle management.
+</purpose>
+
+<when_to_use>
+- Starting a new session on an existing Drive project
+- Context was cleared (new conversation)
+- Handoff from another session
+- User asks to "continue" or "resume" Drive work
+</when_to_use>
+
+<loop_context>
+Determined dynamically by reading STATE.md.
+This workflow figures out where we are, not assumes it.
+</loop_context>
+
+<philosophy>
+**Single next action:** Resume determines state and suggests exactly ONE action.
+No multiple options. Prevents decision fatigue. User can redirect if needed.
+
+**Handoff lifecycle:** Handoffs are consumed on resume, then archived or deleted.
+</philosophy>
+
+<required_reading>
+@.drive/STATE.md
+</required_reading>
+
+<references>
+@~/.claude/drive-framework/references/context-management.md
+@~/.claude/drive-framework/references/loop-phases.md
+</references>
+
+<process>
+
+<step name="verify_paul_exists" priority="first">
+1. Check for .drive/ directory:
+   ```bash
+   ls .drive/STATE.md 2>/dev/null
+   ```
+2. If not found:
+   - "No Drive project found. Run /drive:init first."
+   - Exit workflow
+3. If found: proceed with resume
+</step>
+
+<step name="detect_handoffs">
+**Check for handoff files:**
+
+1. Search for handoff files:
+   ```bash
+   ls -t .drive/HANDOFF*.md 2>/dev/null | head -5
+   ```
+
+2. If handoff argument provided ($ARGUMENTS):
+   - Use specified handoff path
+   - Validate it exists
+
+3. If no argument but handoffs found:
+   - Use most recent handoff (by modification time)
+   - Note: `.drive/HANDOFF-{context}.md` is standard pattern
+
+4. Track handoff for lifecycle:
+   - Store path for later archive/delete
+   - Will be consumed after resume proceeds
+</step>
+
+<step name="load_state">
+1. Read `.drive/STATE.md`
+2. Extract:
+   - Current Position (phase, plan, status)
+   - Loop Position (PLAN/APPLY/UNIFY markers)
+   - Last activity (what was happening)
+   - Session Continuity section:
+     - Stopped at
+     - Next action
+     - Resume file
+     - Resume context
+</step>
+
+<step name="load_resume_context">
+1. If handoff detected in previous step:
+   - Read handoff file content
+   - Present as "HANDOFF CONTEXT DETECTED" section
+   - Extract key information (decisions, gaps, next actions)
+
+2. If resume file specified in STATE.md (and no handoff):
+   - Read the resume file (PLAN, SUMMARY)
+
+3. Build mental picture of:
+   - What was accomplished
+   - What's in progress
+   - What's next
+   - Any decisions or gaps from handoff
+</step>
+
+<step name="determine_single_action">
+Based on loop position, determine **exactly ONE** next action:
+
+| Loop State | Single Next Action |
+|------------|-------------------|
+| PLAN ○ (no plan yet) | `/drive:plan` |
+| PLAN ✓, APPLY ○ (plan awaiting approval) | `/drive:apply [plan-path]` |
+| PLAN ✓, APPLY ✓, UNIFY ○ (executed, not reconciled) | `/drive:unify [plan-path]` |
+| All ✓ (loop complete) | `/drive:plan` (next phase) |
+| Blocked | "Address blocker: [specific issue]" |
+
+**Do NOT offer multiple options.** Pick the ONE correct action.
+</step>
+
+<step name="report_and_route">
+Display to user with ONE next action:
+
+```
+════════════════════════════════════════
+Drive PROJECT RESUMED
+════════════════════════════════════════
+
+Project: [from PROJECT.md]
+Phase: [N] of [M] - [Phase Name]
+Plan: [NN-PP] - [plan description]
+
+Loop Position:
+┌─────────────────────────────────────┐
+│  PLAN ──▶ APPLY ──▶ UNIFY          │
+│   [✓/○]    [✓/○]    [✓/○]          │
+└─────────────────────────────────────┘
+
+Last Session: [timestamp]
+Stopped at: [what was happening]
+
+────────────────────────────────────────
+▶ NEXT: [single command with path]
+  [brief description of what it does]
+────────────────────────────────────────
+
+Type "yes" to proceed, or provide context for a different action.
+```
+
+**IMPORTANT:** Do NOT show numbered options (1, 2, 3, 4).
+Show exactly ONE suggested action with the standard Drive routing format.
+</step>
+
+</process>
+
+<step name="handoff_lifecycle">
+**After user proceeds with work:**
+
+When user confirms next action (e.g., "yes", "1", "approved"):
+
+1. **Archive handoff** (if one was consumed):
+   ```bash
+   mkdir -p .drive/handoffs/archive
+   mv .drive/HANDOFF-{context}.md .drive/handoffs/archive/
+   ```
+   - Preserves history while removing from active path
+   - Alternative: delete if archive not needed
+
+2. **Clean orphaned handoffs:**
+   ```bash
+   # Find handoffs older than current phase
+   find .drive -maxdepth 1 -name "HANDOFF*.md" -mtime +7 -type f
+   ```
+   - Move to archive or delete
+   - Prevents accumulation of stale handoffs
+
+3. **Update STATE.md:**
+   - Clear "Resume file" if it pointed to handoff
+   - Handoff context now integrated into session
+</step>
+
+</process>
+
+<output>
+- Context restored from STATE.md and/or handoff
+- Handoff content presented if detected
+- User informed of current position
+- Exactly ONE next action suggested
+- User can proceed or redirect
+- Handoff archived after work proceeds
+</output>
+
+<error_handling>
+**STATE.md corrupted or incomplete:**
+- Report what's missing
+- Suggest: `/drive:init` to reinitialize (destructive) or manual repair
+
+**Conflicting information:**
+- STATE.md says X, but files suggest Y
+- Report discrepancy
+- Ask user to clarify actual state
+
+**No resume context:**
+- If SESSION CONTINUITY section empty:
+- Fall back to loop position
+- Suggest based on what files exist
+
+**Stale handoff:**
+- If handoff older than STATE.md modifications
+- Trust STATE.md, note handoff may be outdated
+</error_handling>

package/modules/drive/src/workflows/roadmap-management.md

@@ -0,0 +1,334 @@
+<purpose>
+Handle dynamic roadmap modifications: adding phases to the current milestone and removing future phases. These are the "escape hatches" when scope changes mid-milestone.
+
+**Operations:**
+- **add-phase:** Append a new phase to the current milestone
+- **remove-phase:** Remove a future (not-started) phase
+</purpose>
+
+<when_to_use>
+- User realizes more phases are needed mid-milestone
+- Scope changed and a planned phase is no longer needed
+- Emergency phase insertion (use decimal phases for interruptions)
+- Roadmap cleanup after requirements change
+</when_to_use>
+
+<loop_context>
+N/A - This is a roadmap modification workflow, not a loop phase.
+Can be invoked at any time during a milestone.
+</loop_context>
+
+<required_reading>
+@.drive/ROADMAP.md
+@.drive/STATE.md
+</required_reading>
+
+<references>
+@src/templates/ROADMAP.md (phase section format)
+</references>
+
+---
+
+## Operation: add-phase
+
+<process>
+
+<step name="add_validate" priority="first">
+1. Read ROADMAP.md for current milestone
+2. Identify highest phase number in milestone
+3. Calculate next phase number = highest + 1
+
+**If no active milestone:**
+- Error: "No active milestone. Run /drive:milestone first."
+- Exit workflow
+</step>
+
+<step name="add_gather_info">
+Ask for phase details:
+
+```
+Adding phase {next_number} to {milestone_name}.
+
+Phase name?
+(Example: "Testing", "Documentation", "Performance")
+```
+
+Wait for response. Store as `phase_name`.
+
+Optional follow-up:
+```
+Brief description? (Press Enter to skip)
+```
+
+Store as `phase_description` or derive from name.
+</step>
+
+<step name="add_update_roadmap">
+Update ROADMAP.md:
+
+1. **Update milestone header:**
+   ```markdown
+   Phases: {X} of {new_total} complete
+   ```
+
+2. **Add to phases table:**
+   ```markdown
+   | {next_number} | {phase_name} | TBD | Not started | - |
+   ```
+
+3. **Add phase details section:**
+   ```markdown
+   ### Phase {next_number}: {phase_name}
+
+   Focus: {phase_description}
+   Plans: TBD (defined during /drive:plan)
+   Status: Not started
+   ```
+
+4. **Update footer timestamp**
+</step>
+
+<step name="add_create_directory">
+Create phase directory:
+
+```bash
+mkdir -p .drive/phases/{NN}-{phase-slug}
+```
+
+Where:
+- `NN` = zero-padded phase number
+- `phase-slug` = lowercase, hyphenated phase name
+</step>
+
+<step name="add_update_state">
+Update STATE.md:
+
+1. **Last activity:**
+   ```markdown
+   Last activity: {timestamp} — Added Phase {number}: {name}
+   ```
+
+2. **Decisions (add to table):**
+   ```markdown
+   | Added Phase {number}: {name} | Phase {current} | Extends milestone scope |
+   ```
+</step>
+
+<step name="add_confirm">
+Display confirmation:
+
+```
+════════════════════════════════════════
+PHASE ADDED
+════════════════════════════════════════
+
+Phase {number}: {name}
+Directory: .drive/phases/{slug}/
+
+{milestone_name} now has {total} phases.
+
+ROADMAP.md updated ✓
+STATE.md updated ✓
+
+Continue with current work or plan this phase later.
+════════════════════════════════════════
+```
+</step>
+
+</process>
+
+---
+
+## Operation: remove-phase
+
+<process>
+
+<step name="remove_validate" priority="first">
+1. Read ROADMAP.md for current milestone
+2. Find target phase by number or name
+3. Check phase status
+
+**Validation rules:**
+- Phase must be "Not started" — cannot remove in-progress or complete phases
+- Phase must be in current milestone
+- Cannot remove if it's the only remaining phase
+
+**If validation fails:**
+```
+Cannot remove Phase {number}: {name}
+Reason: {status is not "Not started" / only remaining phase / not in current milestone}
+
+Only future (not started) phases can be removed.
+```
+Exit workflow.
+</step>
+
+<step name="remove_confirm_intent">
+Ask for confirmation:
+
+```
+════════════════════════════════════════
+REMOVE PHASE?
+════════════════════════════════════════
+
+Phase {number}: {name}
+Status: Not started
+
+This will:
+- Remove from ROADMAP.md
+- Delete .drive/phases/{slug}/ (if empty)
+- Renumber subsequent phases
+
+[1] Yes, remove | [2] Cancel
+════════════════════════════════════════
+```
+
+Wait for confirmation. If "2" or "cancel" → exit.
+</step>
+
+<step name="remove_update_roadmap">
+Update ROADMAP.md:
+
+1. **Remove phase from table**
+
+2. **Remove phase details section**
+
+3. **Renumber subsequent phases:**
+   - Phase 7 removed → Phase 8 becomes 7, Phase 9 becomes 8, etc.
+   - Update both table and details sections
+
+4. **Update milestone header:**
+   ```markdown
+   Phases: {X} of {new_total} complete
+   ```
+
+5. **Update footer timestamp**
+</step>
+
+<step name="remove_cleanup_directory">
+Handle phase directory:
+
+```bash
+rmdir .drive/phases/{NN}-{slug} 2>/dev/null
+```
+
+**If directory not empty:**
+- Warn: "Directory not empty — preserved at .drive/phases/{slug}/"
+- User can manually delete if desired
+
+**If directory empty or doesn't exist:**
+- Silently removed or was never created
+</step>
+
+<step name="remove_renumber_directories">
+**If subsequent phases exist:**
+
+Renumber phase directories to match ROADMAP.md:
+
+```bash
+mv .drive/phases/08-name .drive/phases/07-name
+mv .drive/phases/09-name .drive/phases/08-name
+```
+
+**Note:** This is why we only allow removing "Not started" phases — they have no artifacts yet.
+</step>
+
+<step name="remove_update_state">
+Update STATE.md:
+
+1. **Last activity:**
+   ```markdown
+   Last activity: {timestamp} — Removed Phase {number}: {name}
+   ```
+
+2. **Decisions (add to table):**
+   ```markdown
+   | Removed Phase {original_number}: {name} | Phase {current} | Scope reduction |
+   ```
+
+3. **If removed phase was "next":**
+   - Update current position to reflect new next phase
+</step>
+
+<step name="remove_confirm">
+Display confirmation:
+
+```
+════════════════════════════════════════
+PHASE REMOVED
+════════════════════════════════════════
+
+Removed: Phase {original_number}: {name}
+{renumbered_phases count} phases renumbered.
+
+{milestone_name} now has {total} phases.
+
+ROADMAP.md updated ✓
+STATE.md updated ✓
+════════════════════════════════════════
+```
+</step>
+
+</process>
+
+---
+
+<output>
+**add-phase:**
+- ROADMAP.md updated with new phase
+- Phase directory created
+- STATE.md decision logged
+
+**remove-phase:**
+- ROADMAP.md updated (phase removed, subsequent renumbered)
+- Phase directory removed (if empty)
+- Subsequent directories renumbered
+- STATE.md decision logged
+</output>
+
+<success_criteria>
+**add-phase:**
+- [ ] Next phase number calculated correctly
+- [ ] Phase added to ROADMAP.md table and details
+- [ ] Directory created
+- [ ] STATE.md updated
+- [ ] Milestone total updated
+
+**remove-phase:**
+- [ ] Phase status validated (not started only)
+- [ ] User confirmed removal
+- [ ] Phase removed from ROADMAP.md
+- [ ] Directory cleaned up
+- [ ] Subsequent phases renumbered
+- [ ] STATE.md updated
+</success_criteria>
+
+<validation_rules>
+**add-phase:**
+- Active milestone must exist
+- Phase name required
+- Cannot add duplicate phase names (warning only)
+
+**remove-phase:**
+- Phase must exist
+- Phase must be "Not started"
+- Cannot remove last phase in milestone
+- Cannot remove phase with artifacts (PLAN.md, SUMMARY.md)
+</validation_rules>
+
+<error_handling>
+**No active milestone:**
+- Route to /drive:milestone or /drive:init
+
+**Phase directory not empty:**
+- Preserve directory, warn user
+- User can manually clean up
+
+**Renumbering conflicts:**
+- If directory already exists at target number, warn and skip
+- Report which directories couldn't be renamed
+
+**ROADMAP.md malformed:**
+- Report parsing error
+- Suggest manual fix
+</error_handling>