@accelerationguy/accel 1.0.0

package/modules/drive/src/templates/ISSUES.md

@@ -0,0 +1,93 @@
+# Project Issues Log
+
+Template for `.drive/ISSUES.md` — deferred enhancements discovered during execution.
+
+**Purpose:** Track nice-to-haves that aren't critical to current work. These follow deviation rule #5: log enhancements, continue with plan.
+
+**Location:** `.drive/ISSUES.md` (project-level, not phase-level)
+
+---
+
+## File Template
+
+```markdown
+# Project Issues Log
+
+Enhancements discovered during execution. Not critical - address in future phases.
+
+## Open Enhancements
+
+### ISS-001: [Brief description]
+
+- **Discovered:** Phase [X] Plan [Y] (YYYY-MM-DD)
+- **Type:** [Performance / Refactoring / UX / Testing / Documentation / Accessibility]
+- **Description:** [What could be improved and why it would help]
+- **Impact:** Low (works correctly, this would enhance)
+- **Effort:** [Quick / Medium / Substantial]
+- **Suggested phase:** [Phase number or "Future"]
+
+### ISS-002: [Brief description]
+
+...
+
+## Closed Enhancements
+
+[Moved here when addressed]
+
+### ISS-001: [Brief description]
+**Resolved:** [date] — Addressed in Phase [X] Plan [Y]
+**Commit:** [hash or "N/A"]
+
+---
+
+*Last updated: [date]*
+```
+
+---
+
+## Issue Types
+
+| Type | Description | Example |
+|------|-------------|---------|
+| Performance | Speed or efficiency improvements | "Cache API responses" |
+| Refactoring | Code quality improvements | "Extract shared utility" |
+| UX | User experience enhancements | "Add loading spinner" |
+| Testing | Test coverage additions | "Add edge case tests" |
+| Documentation | Doc improvements | "Add JSDoc comments" |
+| Accessibility | A11y improvements | "Add ARIA labels" |
+
+---
+
+## Effort Estimates
+
+| Effort | Definition |
+|--------|------------|
+| Quick | < 30 min, single task |
+| Medium | 1-2 hours, may need its own plan |
+| Substantial | Half day+, definitely needs dedicated plan |
+
+---
+
+## When to Create
+
+**Create an issue when:**
+- During APPLY, you notice something that could be better
+- It's not blocking current work
+- It's not a bug (bugs get fixed immediately)
+- It would be scope creep to address now
+
+**Don't create an issue when:**
+- It's a bug (fix it or document as blocker)
+- It's required for current AC (do it)
+- It's already in the roadmap
+
+---
+
+## Workflow
+
+1. During APPLY, notice enhancement opportunity
+2. Log to `.drive/ISSUES.md` with ISS-NNN format
+3. Note in SUMMARY.md: "Logged ISS-003 for future consideration"
+4. Continue with current plan
+5. Review ISSUES.md during phase planning
+6. Address issues in appropriate future phase

package/modules/drive/src/templates/MILESTONES.md

@@ -0,0 +1,167 @@
+# MILESTONES.md Template
+
+Template for `.drive/MILESTONES.md` — the project's milestone log.
+
+**Purpose:** Track completed milestones with key accomplishments, stats, and links to next work.
+
+---
+
+## File Template
+
+```markdown
+# Project Milestones: [Project Name]
+
+[Entries in reverse chronological order - newest first]
+
+## v[X.Y] [Name] (Shipped: YYYY-MM-DD)
+
+**Delivered:** [One sentence describing what shipped]
+
+**Phases completed:** [X-Y] ([Z] plans total)
+
+**Key accomplishments:**
+- [Major achievement 1]
+- [Major achievement 2]
+- [Major achievement 3]
+- [Major achievement 4]
+
+**Stats:**
+| Metric | Value |
+|--------|-------|
+| Files modified | [X] |
+| Lines of code | [Y] |
+| Phases | [N] |
+| Plans completed | [M] |
+| Duration | [D] days |
+
+**Git range:** `feat(XX-XX)` → `feat(YY-YY)`
+
+**What's next:** [Brief description of next milestone, or link to ROADMAP.md]
+
+---
+```
+
+---
+
+## Section Specifications
+
+### Header
+**Format:** `## v[X.Y] [Name] (Shipped: YYYY-MM-DD)`
+**Example:** `## v0.2 Session Continuity (Shipped: 2026-01-28)`
+
+### Delivered
+**Purpose:** One-sentence summary of what shipped.
+**Keep it:** User-focused, outcome-oriented.
+
+### Phases completed
+**Format:** `[Start]-[End] ([N] plans total)`
+**Example:** `5-7 (4 plans total)` or `8.5-8.7 (3 plans total)` for decimal phases
+
+### Key accomplishments
+**Count:** 3-5 major achievements.
+**Focus:** User-visible features, technical capabilities, quality improvements.
+**Avoid:** Implementation details, internal refactors (unless significant).
+
+### Stats
+**Purpose:** Quantify the work for historical reference.
+**Collect via:**
+- Files: `git diff --stat feat(XX-XX)..feat(YY-YY) | tail -1`
+- LOC: Count primary language (varies by project)
+- Phases/Plans: Count from ROADMAP.md
+- Duration: Days from first commit to ship
+
+### Git range
+**Purpose:** Reproducible reference to milestone commits.
+**Format:** First commit → last commit of milestone.
+
+### What's next
+**Purpose:** Link to future work.
+**Options:**
+- Next milestone goal: "v0.3 Roadmap & Milestone Management"
+- Reference: "See [ROADMAP.md](ROADMAP.md) for planned work"
+- End state: "Project complete" or "Maintenance mode"
+
+---
+
+## Guidelines
+
+### When to create milestones
+
+**DO create for:**
+- Initial MVP shipped (v1.0)
+- Major version releases (v2.0, v3.0)
+- Significant feature milestones (v1.1, v1.2)
+- Before archiving planning (capture what was shipped)
+
+**DON'T create for:**
+- Individual phase completions (normal workflow)
+- Work in progress (wait until shipped)
+- Minor bug fixes that don't constitute a release
+
+### Ordering
+
+Entries are **reverse chronological** — newest milestone at top.
+
+### Decimal phases
+
+Include decimal phases in the range when relevant:
+- "Phases completed: 8-8.7 (5 plans total)" — includes 8, 8.5, 8.6, 8.7
+
+---
+
+## Example
+
+```markdown
+# Project Milestones: Drive Framework
+
+## v0.2 Session Continuity (Shipped: 2026-01-28)
+
+**Delivered:** Pause/resume workflow with handoff files and enhanced STATE.md session tracking
+
+**Phases completed:** 7-8.7 (5 plans total)
+
+**Key accomplishments:**
+- Handoff file generation for session breaks
+- STATE.md Session Continuity section
+- SonarQube integration (optional)
+- Codebase CLAUDE.md improvements
+
+**Stats:**
+| Metric | Value |
+|--------|-------|
+| Files modified | 12 |
+| Lines of code | 850 |
+| Phases | 4 (7, 8.5, 8.6, 8.7) |
+| Plans completed | 5 |
+| Duration | 2 days |
+
+**Git range:** `feat(07-01)` → `feat(08.7-01)`
+
+**What's next:** v0.3 Roadmap & Milestone Management — milestone lifecycle commands
+
+---
+
+## v0.1 Core Loop (Shipped: 2026-01-27)
+
+**Delivered:** Drive framework foundation with Plan-Apply-Unify loop
+
+**Phases completed:** 1-6 (4 plans total)
+
+**Key accomplishments:**
+- PLAN.md, STATE.md, PROJECT.md, SUMMARY.md templates
+- ROADMAP.md with phase structure
+- Vector Drive domain with 11 rules
+
+**Stats:**
+| Metric | Value |
+|--------|-------|
+| Files modified | 18 |
+| Lines of code | 1,200 |
+| Phases | 6 |
+| Plans completed | 4 |
+| Duration | 1 day |
+
+**Git range:** `feat(01-01)` → `feat(06-01)`
+
+**What's next:** v0.2 Session Continuity — pause/resume workflow
+```

package/modules/drive/src/templates/PLAN.md

@@ -0,0 +1,328 @@
+# PLAN.md Template
+
+Template for `.drive/phases/{phase-number}-{name}/{phase}-{plan}-PLAN.md` - executable phase plans.
+
+**Naming:** `{phase}-{plan}-PLAN.md` (e.g., `01-02-PLAN.md` for Phase 1, Plan 2)
+
+---
+
+## File Template
+
+```markdown
+---
+phase: XX-name
+plan: NN
+type: execute                    # execute | tdd | research
+wave: N                          # Execution wave (1, 2, 3...). Pre-computed at plan time.
+depends_on: []                   # Plan IDs this plan requires (e.g., ["01-01"]).
+files_modified: []               # Files this plan modifies.
+autonomous: true                 # false if plan has checkpoints requiring user interaction
+---
+
+<objective>
+## Goal
+[What this plan accomplishes - specific, measurable]
+
+## Purpose
+[Why this matters for the project - connects to PROJECT.md value]
+
+## Output
+[What artifacts will be created/modified]
+</objective>
+
+<context>
+## Project Context
+@.drive/PROJECT.md
+@.drive/ROADMAP.md
+@.drive/STATE.md
+
+## Prior Work (only if genuinely needed)
+# Only reference prior SUMMARYs if:
+# - This plan imports types/exports from prior plan
+# - Prior plan made decision affecting this plan
+# - Prior plan's output is direct input to this plan
+#
+# Do NOT reflexively chain: Plan 02 refs 01, Plan 03 refs 02...
+
+## Source Files
+@path/to/relevant/source.ts
+</context>
+
+<skills>
+## Required Skills (from SPECIAL-FLOWS.md)
+
+<!-- If .drive/SPECIAL-FLOWS.md exists, this section is auto-populated by /drive:plan -->
+<!-- If no SPECIAL-FLOWS.md, omit this section or show "No specialized flows configured" -->
+
+| Skill | Priority | When to Invoke | Loaded? |
+|-------|----------|----------------|---------|
+| /skill-name | required | Before [work type] | ○ |
+| /skill-name | optional | For [specific need] | ○ |
+
+**BLOCKING:** Required skills MUST be loaded before APPLY proceeds.
+Run each skill command or confirm already loaded.
+
+## Skill Invocation Checklist
+- [ ] /skill-1 loaded (run command or confirm)
+- [ ] /skill-2 loaded (run command or confirm)
+
+</skills>
+
+<acceptance_criteria>
+
+## AC-1: [Criterion Name]
+```gherkin
+Given [precondition / system state]
+When [user action / trigger]
+Then [expected outcome / observable result]
+```
+
+## AC-2: [Criterion Name]
+```gherkin
+Given [precondition]
+When [action]
+Then [outcome]
+```
+
+## AC-3: [Criterion Name]
+```gherkin
+Given [precondition]
+When [action]
+Then [outcome]
+```
+
+</acceptance_criteria>
+
+<tasks>
+
+<task type="auto">
+  <name>Task 1: [Action-oriented name]</name>
+  <files>path/to/file.ext, another/file.ext</files>
+  <action>
+    [Specific implementation instructions]
+    - What to do
+    - How to do it
+    - What to avoid and WHY
+  </action>
+  <verify>[Command or check to prove it worked]</verify>
+  <done>[Measurable acceptance criteria - links to AC-N]</done>
+</task>
+
+<task type="auto">
+  <name>Task 2: [Action-oriented name]</name>
+  <files>path/to/file.ext</files>
+  <action>[Specific implementation]</action>
+  <verify>[Command or check]</verify>
+  <done>[Acceptance criteria]</done>
+</task>
+
+<task type="checkpoint:decision" gate="blocking">
+  <decision>[What needs deciding]</decision>
+  <context>[Why this decision matters now]</context>
+  <options>
+    <option id="option-a">
+      <name>[Option name]</name>
+      <pros>[Benefits and advantages]</pros>
+      <cons>[Tradeoffs and limitations]</cons>
+    </option>
+    <option id="option-b">
+      <name>[Option name]</name>
+      <pros>[Benefits and advantages]</pros>
+      <cons>[Tradeoffs and limitations]</cons>
+    </option>
+  </options>
+  <resume-signal>Select: option-a or option-b</resume-signal>
+</task>
+
+<task type="checkpoint:human-verify" gate="blocking">
+  <what-built>[What was built that needs verification]</what-built>
+  <how-to-verify>
+    1. Run: [command to start]
+    2. Visit: [URL or location]
+    3. Test: [Specific interactions]
+    4. Confirm: [Expected behaviors]
+  </how-to-verify>
+  <resume-signal>Type "approved" to continue, or describe issues to fix</resume-signal>
+</task>
+
+</tasks>
+
+<boundaries>
+
+## DO NOT CHANGE
+- [Protected file or pattern]
+- [Another protected element]
+
+## SCOPE LIMITS
+- [What's explicitly out of scope for this plan]
+- [Another exclusion]
+
+</boundaries>
+
+<verification>
+Before declaring plan complete:
+- [ ] [Specific test command]
+- [ ] [Build/type check passes]
+- [ ] [Behavior verification]
+- [ ] All acceptance criteria met
+</verification>
+
+<success_criteria>
+- All tasks completed
+- All verification checks pass
+- No errors or warnings introduced
+- [Plan-specific criteria]
+</success_criteria>
+
+<output>
+After completion, create `.drive/phases/XX-name/{phase}-{plan}-SUMMARY.md`
+</output>
+```
+
+---
+
+## Frontmatter Fields
+
+| Field | Required | Purpose |
+|-------|----------|---------|
+| `phase` | Yes | Phase identifier (e.g., `01-foundation`) |
+| `plan` | Yes | Plan number within phase (e.g., `01`, `02`) |
+| `type` | Yes | `execute` for standard, `tdd` for test-driven, `research` for exploration |
+| `wave` | Yes | Execution wave number (1, 2, 3...). Pre-computed at plan time. |
+| `depends_on` | Yes | Array of plan IDs this plan requires. Empty = parallel candidate. |
+| `files_modified` | Yes | Files this plan touches. For conflict detection. |
+| `autonomous` | Yes | `true` if no checkpoints, `false` if has checkpoints |
+
+---
+
+## Task Types
+
+| Type | Use For | Behavior |
+|------|---------|----------|
+| `auto` | Everything AI can do independently | Fully autonomous execution |
+| `checkpoint:decision` | Implementation choices requiring human input | Pauses, presents options, waits for selection |
+| `checkpoint:human-verify` | Visual/functional verification | Pauses, presents verification steps, waits for approval |
+| `checkpoint:human-action` | Truly unavoidable manual steps (rare) | Pauses, describes action, waits for confirmation |
+
+---
+
+## Task Structure Requirements
+
+Every `auto` task MUST have:
+- `<name>` - Action-oriented, describes outcome
+- `<files>` - Which files created/modified
+- `<action>` - Specific implementation (what to do, what to avoid)
+- `<verify>` - How to prove it worked (command, check)
+- `<done>` - Acceptance criteria (links to AC-N)
+
+**If you can't specify Files + Action + Verify + Done, the task is too vague.**
+
+---
+
+## Acceptance Criteria Format
+
+Use Given/When/Then (BDD) format:
+
+```gherkin
+Given [precondition / initial state]
+When [action / trigger]
+Then [expected outcome]
+```
+
+**Guidelines:**
+- Each criterion should be independently testable
+- Include error states and edge cases
+- Avoid implementation details (describe behavior, not code)
+- Link tasks to criteria via `<done>AC-N satisfied</done>`
+
+---
+
+## Scope Guidance
+
+**Plan sizing:**
+- 2-3 tasks per plan maximum
+- ~50% context usage target
+- Single concern per plan
+
+**When to split into multiple plans:**
+- Different subsystems (auth vs API vs UI)
+- More than 3 tasks
+- Risk of context overflow
+- TDD candidates (separate plans)
+
+**Prefer vertical slices:**
+```
+PREFER: Plan 01 = User (model + API + UI)
+        Plan 02 = Product (model + API + UI)
+
+AVOID:  Plan 01 = All models
+        Plan 02 = All APIs
+        Plan 03 = All UIs
+```
+
+---
+
+## Parallel Execution
+
+**Wave 1 candidates (parallel):**
+- `depends_on: []` - No dependencies
+- No file conflicts with other Wave 1 plans
+- `autonomous: true` - No checkpoints blocking
+
+**Sequential (genuine dependency):**
+- `depends_on: ["01-01"]` - Requires prior plan output
+- Uses types/exports created by prior plan
+- Prior plan makes decision affecting this plan
+
+**Do NOT reflexively chain:** Plan 02 depending on 01 "just because" creates false sequential execution.
+
+---
+
+## Anti-Patterns
+
+**Vague tasks:**
+```xml
+<!-- BAD -->
+<task type="auto">
+  <name>Set up authentication</name>
+  <action>Add auth to the app</action>
+</task>
+
+<!-- GOOD -->
+<task type="auto">
+  <name>Create login endpoint with JWT</name>
+  <files>src/api/auth/login.ts, src/lib/jwt.ts</files>
+  <action>
+    Create POST /api/auth/login endpoint:
+    - Accept { email, password } body
+    - Validate against User model with bcrypt compare
+    - Return JWT token on success (15min expiry)
+    - Return 401 on invalid credentials
+    Avoid: Storing plaintext passwords, using weak JWT secrets
+  </action>
+  <verify>curl -X POST /api/auth/login returns JWT token</verify>
+  <done>AC-1 satisfied: User can authenticate with valid credentials</done>
+</task>
+```
+
+**Reflexive dependencies:**
+```yaml
+# BAD - chaining just because sequential
+depends_on: ["01-01"]  # Plan 02 doesn't actually need 01's output
+
+# GOOD - genuine dependency
+depends_on: ["01-01"]  # Plan 02 imports User type from 01-01
+```
+
+**Missing boundaries:**
+```markdown
+<!-- BAD - no protection -->
+<tasks>...</tasks>
+
+<!-- GOOD - explicit boundaries -->
+<boundaries>
+## DO NOT CHANGE
+- database/migrations/* (schema locked for this phase)
+- src/lib/auth.ts (auth system stable)
+</boundaries>
+```