@accelerationguy/accel 1.0.0

package/modules/drive/src/templates/SPECIAL-FLOWS.md

@@ -0,0 +1,70 @@
+# Specialized Flows
+
+**Project:** {{project_name}}
+**Created:** {{timestamp}}
+**Last Updated:** {{timestamp}}
+
+---
+
+## Project-Level Dependencies
+
+Skills and commands that apply to this project's work.
+
+| Work Type | Skill/Command | Priority | When Required | Notes |
+|-----------|---------------|----------|---------------|-------|
+| {{work_type}} | {{/skill-name}} | required | {{trigger_condition}} | {{optional_notes}} |
+| {{work_type}} | {{/skill-name}} | optional | {{trigger_condition}} | {{optional_notes}} |
+
+**Priority Legend:**
+- `required` - Gap documented if not invoked during UNIFY
+- `optional` - Informational only, no gap logged
+
+---
+
+## Phase Overrides
+
+Skills needed for specific phases beyond project-level defaults.
+
+| Phase | Additional Skills | Notes |
+|-------|-------------------|-------|
+| {{phase_number}} | {{/skill:subcommand}} | {{why_needed}} |
+
+---
+
+## Templates & Assets
+
+Reference templates, assets, or external resources for this project.
+
+| Asset Type | Location | When Used |
+|------------|----------|-----------|
+| {{asset_type}} | {{path_or_url}} | {{trigger_condition}} |
+
+---
+
+## Verification Checklist
+
+During UNIFY, confirm:
+- [ ] Required skills were invoked for matching work types
+- [ ] Gaps documented in STATE.md Deviations section
+- [ ] Patterns updated if intentional deviation is now standard
+
+### Skill Audit Template
+
+Use this during UNIFY to track invocations:
+
+| Expected Skill | Invoked? | Gap? | Notes |
+|----------------|----------|------|-------|
+| {{/skill}} | ✓/○ | Yes/- | {{context}} |
+
+---
+
+## Amendment History
+
+| Date | Change | Reason |
+|------|--------|--------|
+| {{timestamp}} | Initial creation | Project setup |
+
+---
+
+*Generated by `/drive:flows` or `/drive:init`*
+*Reference: @references/specialized-workflow-integration.md*

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

@@ -0,0 +1,210 @@
+# STATE.md Template
+
+Template for `.drive/STATE.md` — the project's living memory.
+
+**Purpose:** Single source of truth for current position, accumulated context, and session continuity.
+
+---
+
+## File Template
+
+```markdown
+# Project State
+
+## Project Reference
+
+See: .drive/PROJECT.md (updated [YYYY-MM-DD])
+
+**Core value:** [One-liner from PROJECT.md - the ONE thing that matters]
+**Current focus:** [Current milestone and phase name]
+
+## Current Position
+
+Milestone: [Name] ([version])
+Phase: [X] of [Y] ([Phase Name])
+Plan: [A] of [B] in current phase
+Status: [Ready to plan | Planning | Approved | Applying | Unifying | Complete | Blocked]
+Last activity: [YYYY-MM-DD HH:MM] — [What happened]
+
+Progress:
+- Milestone: [░░░░░░░░░░] 0%
+- Phase: [░░░░░░░░░░] 0%
+
+## Loop Position
+
+Current loop state:
+```
+PLAN ──▶ APPLY ──▶ UNIFY
+  ◉        ○        ○     [Planning]
+  ✓        ◉        ○     [Applying]
+  ✓        ✓        ◉     [Unifying]
+  ✓        ✓        ✓     [Complete - ready for next PLAN]
+```
+
+## Performance Metrics
+
+**Velocity:**
+- Total plans completed: [N]
+- Average duration: [X] min
+- Total execution time: [X.X] hours
+
+**By Phase:**
+
+| Phase | Plans | Total Time | Avg/Plan |
+|-------|-------|------------|----------|
+| 01-[name] | 0/0 | - | - |
+
+**Recent Trend:**
+- Last 5 plans: [durations]
+- Trend: [Improving | Stable | Degrading]
+
+*Updated after each plan completion*
+
+## Accumulated Context
+
+### Decisions
+
+Decisions logged via decision-logger. Recent decisions affecting current work:
+
+| Decision | Phase | Impact |
+|----------|-------|--------|
+| [Decision summary] | [Phase X] | [Ongoing effect] |
+
+### Deferred Issues
+
+Issues logged but not yet addressed:
+
+| Issue | Origin | Effort | Revisit |
+|-------|--------|--------|---------|
+| [Brief description] | [Phase X] | [S/M/L] | [When to reconsider] |
+
+### Blockers/Concerns
+
+Active blockers affecting progress:
+
+| Blocker | Impact | Resolution Path |
+|---------|--------|-----------------|
+| [Description] | [What's blocked] | [How to resolve] |
+
+## Boundaries (Active)
+
+Protected elements for current phase:
+
+- [Protected file/pattern from current PLAN.md]
+- [Another protected element]
+
+## Session Continuity
+
+Last session: [YYYY-MM-DD HH:MM]
+Stopped at: [Description of last completed action]
+Next action: [What to do when resuming]
+Resume context: [Key information needed to continue]
+
+---
+*STATE.md — Updated after every significant action*
+*Size target: <100 lines (digest, not archive)*
+```
+
+---
+
+## Section Specifications
+
+### Project Reference
+**Purpose:** Pointer to PROJECT.md for full context.
+**Contains:**
+- Core value (one-liner from PROJECT.md)
+- Current focus (milestone + phase)
+- Last update date (triggers re-read if stale)
+
+**Update:** When PROJECT.md changes or milestone shifts.
+
+### Current Position
+**Purpose:** Where we are right now.
+**Contains:**
+- Milestone name and version
+- Phase X of Y with name
+- Plan A of B within phase
+- Status (planning/applying/unifying/complete/blocked)
+- Last activity timestamp and description
+- Visual progress bars
+
+**Update:** After every phase/plan state change.
+
+### Loop Position
+**Purpose:** Visual indicator of Drive loop state.
+**States:**
+- Planning: PLAN active, APPLY/UNIFY pending
+- Applying: PLAN complete, APPLY active, UNIFY pending
+- Unifying: PLAN/APPLY complete, UNIFY active
+- Complete: Full loop done, ready for next PLAN
+
+**Update:** At each loop phase transition.
+
+### Performance Metrics
+**Purpose:** Track velocity for patterns and estimation.
+**Contains:**
+- Aggregate stats (total plans, average duration)
+- Per-phase breakdown
+- Recent trend analysis
+
+**Update:** After each plan completion.
+
+### Accumulated Context
+**Purpose:** Digest of decisions, issues, blockers.
+
+**Decisions:** Recent decisions affecting current work. Full log in decision-logger or PROJECT.md.
+
+**Deferred Issues:** Items logged but not addressed. Include effort estimate and revisit trigger.
+
+**Blockers:** Active obstacles requiring resolution.
+
+**Update:** After UNIFY phase reconciliation.
+
+### Boundaries (Active)
+**Purpose:** Quick reference to current phase protections.
+**Contains:** Protected files/patterns from active PLAN.md.
+
+**Update:** When entering new PLAN phase.
+
+### Session Continuity
+**Purpose:** Enable instant session resumption.
+**Contains:**
+- Last session timestamp
+- What was completed
+- What to do next
+- Key context needed
+
+**Update:** At end of each session or significant pause.
+
+---
+
+## Size Constraint
+
+**Target:** Under 100 lines.
+
+STATE.md is a DIGEST, not an archive. If sections grow too large:
+- Keep only 3-5 recent decisions (full log elsewhere)
+- Reference issue tracker instead of listing all issues
+- Keep only active blockers, remove resolved
+- Summarize instead of detail
+
+**Goal:** "Read once, know where we are" — if too long, that fails.
+
+---
+
+## Lifecycle
+
+**Creation:** After ROADMAP.md created (during project init)
+- Reference PROJECT.md (extract core value)
+- Initialize empty sections
+- Set position to "Phase 1 ready to plan"
+
+**Reading:** First step of EVERY workflow
+- Load before planning, applying, or unifying
+- Provides instant context restoration
+
+**Writing:** After every significant action
+- After PLAN approval: Update status to "Approved"
+- After APPLY completion: Update position, log duration
+- After UNIFY: Update decisions, issues, blockers
+- After session end: Update continuity section

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

@@ -0,0 +1,221 @@
+# SUMMARY.md Template
+
+Template for `.drive/phases/{phase-number}-{name}/{phase}-{plan}-SUMMARY.md` — plan completion documentation.
+
+**Purpose:** Document what was built, decisions made, deviations from plan, and readiness for next phase.
+
+---
+
+## File Template
+
+```markdown
+---
+phase: XX-name
+plan: NN
+subsystem: [primary category: auth, payments, ui, api, database, infra, testing]
+tags: [searchable tech: jwt, stripe, react, postgres, prisma]
+
+# Dependency graph
+requires:
+  - phase: [prior phase this depends on]
+    provides: [what that phase built that this uses]
+provides:
+  - [what this plan built/delivered]
+  - [another deliverable]
+affects: [phase names or keywords that will need this context]
+
+# Tech tracking
+tech-stack:
+  added: [libraries/tools added]
+  patterns: [architectural patterns established]
+
+key-files:
+  created: [important files created]
+  modified: [important files modified]
+
+key-decisions:
+  - "Decision 1: [brief]"
+  - "Decision 2: [brief]"
+
+patterns-established:
+  - "Pattern 1: [description]"
+  - "Pattern 2: [description]"
+
+# Metrics
+duration: Xmin
+started: YYYY-MM-DDTHH:MM:SSZ
+completed: YYYY-MM-DDTHH:MM:SSZ
+---
+
+# Phase [X] Plan [Y]: [Name] Summary
+
+**[Substantive one-liner describing outcome - what actually shipped]**
+
+## Performance
+
+| Metric | Value |
+|--------|-------|
+| Duration | [time] |
+| Started | [ISO timestamp] |
+| Completed | [ISO timestamp] |
+| Tasks | [N] completed |
+| Files modified | [N] |
+
+## Acceptance Criteria Results
+
+| Criterion | Status | Notes |
+|-----------|--------|-------|
+| AC-1: [Name] | Pass / Fail | [Details if needed] |
+| AC-2: [Name] | Pass / Fail | [Details] |
+| AC-3: [Name] | Pass / Fail | [Details] |
+
+## Accomplishments
+
+- [Most important outcome - specific, substantive]
+- [Second key accomplishment]
+- [Third if applicable]
+
+## Task Commits
+
+Each task committed atomically:
+
+| Task | Commit | Type | Description |
+|------|--------|------|-------------|
+| Task 1: [name] | `abc123f` | feat | [What was done] |
+| Task 2: [name] | `def456g` | feat | [What was done] |
+| Task 3: [name] | `hij789k` | test | [What was done] |
+
+Plan metadata: `lmn012o` (docs: complete plan)
+
+## Files Created/Modified
+
+| File | Change | Purpose |
+|------|--------|---------|
+| `path/to/file.ts` | Created | [What it does] |
+| `path/to/another.ts` | Modified | [What changed] |
+
+## Decisions Made
+
+[Key decisions with brief rationale]
+
+| Decision | Rationale | Impact |
+|----------|-----------|--------|
+| [What was decided] | [Why] | [Effect on future work] |
+
+Or: "None - followed plan as specified"
+
+## Deviations from Plan
+
+### Summary
+
+| Type | Count | Impact |
+|------|-------|--------|
+| Auto-fixed | [N] | [Brief assessment] |
+| Scope additions | [N] | [Brief assessment] |
+| Deferred | [N] | Logged to issues |
+
+**Total impact:** [Brief assessment - e.g., "Essential fixes, no scope creep"]
+
+### Auto-fixed Issues
+
+**1. [Category] [Brief description]**
+- **Found during:** Task [N] ([task name])
+- **Issue:** [What was wrong]
+- **Fix:** [What was done]
+- **Files:** [Affected files]
+- **Verification:** [How verified]
+- **Commit:** [hash] (part of task commit)
+
+[Repeat for each auto-fix]
+
+### Deferred Items
+
+Logged to issue tracker for future consideration:
+- [Issue ID]: [Brief description] (discovered in Task [N])
+
+Or: "None - plan executed exactly as written"
+
+## Issues Encountered
+
+[Problems during execution and how resolved]
+
+| Issue | Resolution |
+|-------|------------|
+| [Problem] | [How solved] |
+
+Or: "None"
+
+## Next Phase Readiness
+
+**Ready:**
+- [What's ready for next phase]
+- [Foundation established]
+
+**Concerns:**
+- [Potential issues for future phases]
+- [Technical debt introduced]
+
+**Blockers:**
+- [Anything blocking next phase] or "None"
+
+---
+*Phase: XX-name, Plan: NN*
+*Completed: [YYYY-MM-DD]*
+```
+
+---
+
+## Section Specifications
+
+### Frontmatter
+**Purpose:** Machine-readable metadata for automatic context assembly.
+
+| Field | Purpose |
+|-------|---------|
+| `phase`, `plan` | Identification |
+| `subsystem` | Primary categorization (auth, api, ui, etc.) |
+| `tags` | Searchable tech keywords |
+| `requires` | What prior phases this depended on |
+| `provides` | What this plan delivers |
+| `affects` | Future phases that need this context |
+| `tech-stack` | Libraries added, patterns established |
+| `key-files` | Important files for @context references |
+| `key-decisions` | Quick-reference decisions (detail in body) |
+| `patterns-established` | Conventions future phases should follow |
+| `duration`, `started`, `completed` | Performance metrics |
+
+### One-liner Requirements
+
+**Must be substantive:**
+
+| Good | Bad |
+|------|-----|
+| "JWT auth with refresh rotation using jose library" | "Phase complete" |
+| "Prisma schema with User, Session, Product models" | "Authentication implemented" |
+| "Dashboard with real-time metrics via SSE" | "All tasks done" |
+
+The one-liner should tell someone what actually shipped.
+
+### Acceptance Criteria Results
+**Purpose:** Verify all AC from PLAN.md were met.
+**Contains:** Each AC with pass/fail status and notes.
+**Requirement:** All must pass for plan to be complete.
+
+### Deviations Section
+**Purpose:** Document unplanned work and its handling.
+
+**Auto-fixed:** Issues discovered and resolved during execution.
+- Include: category, what was wrong, fix, verification
+- Must be essential fixes, not scope creep
+
+**Deferred:** Items logged for future consideration.
+- Include: issue ID, brief description, origin task
+
+**Note:** Separate from "Issues Encountered" which documents problems with planned work.
+
+### Next Phase Readiness
+**Purpose:** Prepare context for next PLAN phase.
+
+**Ready:** What's available for next phase to build on.
+**Concerns:** Potential issues to watch for.
+**Blockers:** Anything preventing next phase (usually "None").

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

@@ -0,0 +1,139 @@
+# UAT Issues Template
+
+Template for `.drive/phases/XX-name/{phase}-{plan}-UAT.md` — issues discovered during user acceptance testing.
+
+**Purpose:** Capture problems found during verify-work workflow. Unlike global ISSUES.md (for deferred enhancements), this file tracks bugs and problems in specific delivered work.
+
+**Location:** Same directory as the SUMMARY.md being tested.
+
+---
+
+## File Template
+
+```markdown
+# UAT Issues: Phase [X] Plan [Y]
+
+**Tested:** [date]
+**Source:** [path to SUMMARY.md that was tested]
+**Tester:** User via verify-work workflow
+
+## Open Issues
+
+### UAT-001: [Brief description]
+
+**Discovered:** [date]
+**Phase/Plan:** [XX]-[YY]
+**Severity:** [Blocker/Major/Minor/Cosmetic]
+**Feature:** [Which feature from the test checklist]
+**Description:** [User's description of the problem]
+**Expected:** [What should have happened]
+**Actual:** [What actually happened]
+**Repro:** [Steps to reproduce, if captured]
+
+### UAT-002: [Brief description]
+
+...
+
+## Resolved Issues
+
+[Moved here after fix plan executes and fixes are verified]
+
+### UAT-001: [Brief description]
+**Resolved:** [date] — Fixed in {phase}-{plan}-FIX.md
+**Commit:** [hash]
+
+---
+
+*Phase: XX-name*
+*Plan: YY*
+*Tested: [date]*
+```
+
+---
+
+## Severity Guide
+
+| Severity | Definition | Example | Action |
+|----------|------------|---------|--------|
+| **Blocker** | Feature completely unusable | App crashes on button click | Stop, fix immediately |
+| **Major** | Feature works but significant problem | Form submits but data not saved | Fix before shipping |
+| **Minor** | Feature usable but has issues | Button text slightly cut off | Fix if time permits |
+| **Cosmetic** | Visual only, no functional impact | Wrong shade of color | Log, fix later |
+
+---
+
+## UAT Numbering
+
+- **Prefix:** `UAT-` (distinguishes from ISS- enhancement issues)
+- **Scope:** Per-file numbering (UAT-001, UAT-002, etc. within each file)
+- **No global numbering:** Each {phase}-{plan}-UAT.md has its own sequence
+
+---
+
+## Good Example
+
+```markdown
+# UAT Issues: Phase 5 Plan 2
+
+**Tested:** 2026-01-15
+**Source:** .drive/phases/05-auth/05-02-SUMMARY.md
+**Tester:** User via verify-work workflow
+
+## Open Issues
+
+### UAT-001: Login form doesn't show validation errors
+
+**Discovered:** 2026-01-15
+**Phase/Plan:** 05-02
+**Severity:** Major
+**Feature:** User login form
+**Description:** When I enter an invalid email, nothing happens. No error message appears.
+**Expected:** Red error message below email field saying "Invalid email format"
+**Actual:** Field border turns red but no text explanation
+**Repro:**
+1. Go to /login
+2. Enter "notanemail" in email field
+3. Click Login button
+
+### UAT-002: Password field allows paste
+
+**Discovered:** 2026-01-15
+**Phase/Plan:** 05-02
+**Severity:** Cosmetic
+**Feature:** User login form
+**Description:** Can paste into password field. Minor UX inconsistency.
+**Expected:** Paste disabled (matches signup form)
+**Actual:** Paste works in login but not signup
+**Repro:** Ctrl+V in password field
+
+## Resolved Issues
+
+[None yet]
+
+---
+
+*Phase: 05-auth*
+*Plan: 02*
+*Tested: 2026-01-15*
+```
+
+---
+
+## Workflow
+
+1. **verify-work workflow** runs against a SUMMARY.md
+2. User tests each feature from the plan's AC
+3. Issues found → create/update {phase}-{plan}-UAT.md
+4. If blockers exist → create FIX plan immediately
+5. If majors exist → create FIX plan before shipping
+6. After FIX plan executes → move issues to "Resolved" section
+7. File becomes historical record of what was found and fixed
+
+---
+
+## Difference from ISSUES.md
+
+| File | Purpose | Content | Timing |
+|------|---------|---------|--------|
+| **ISSUES.md** | Deferred enhancements | Nice-to-haves discovered during APPLY | During development |
+| **UAT-ISSUES.md** | Testing problems | Bugs found during verification | During UAT |