@accelerationguy/accel 1.0.0

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

@@ -0,0 +1,219 @@
+# PROJECT.md Template
+
+Template for `.drive/PROJECT.md` — the project's business context and requirements.
+
+**Purpose:** Define what we're building, why it matters, and constraints. This is the "brief" that informs all planning. Init populates this from a type-adapted requirements walkthrough — instead of leaving placeholders, because plans built against real requirements produce better output.
+
+---
+
+## File Template
+
+```markdown
+# [Project Name]
+
+## What This Is
+
+[One paragraph describing what we're building. Be specific about the product/feature, not the technology.]
+
+## Core Value
+
+[Single sentence: What problem does this solve for whom? This is THE thing that matters.]
+
+## Current State
+
+| Attribute | Value |
+|-----------|-------|
+| Type | [Application / Campaign / Workflow / Other] |
+| Version | [current version] |
+| Status | [Prototype / MVP / Beta / Production] |
+| Last Updated | [YYYY-MM-DD] |
+
+**Production URLs:** (if applicable)
+- [URL 1]: [Description]
+- [URL 2]: [Description]
+
+## Requirements
+
+### Core [Features / Deliverables / Automation Scope]
+
+<!-- Label adapts by project type:
+     Application: "Core Features" — the 3-5 things users do in this app
+     Campaign: "Core Deliverables" — landing pages, emails, ad copy, etc.
+     Workflow: "Automation Scope" — what this automates and what triggers it
+     Other: "Core Deliverables" — primary outputs of this project -->
+
+- [item 1]
+- [item 2]
+- [item 3]
+
+### Validated (Shipped)
+
+[Requirements that have been implemented and proven]
+
+- [x] [Requirement 1] — [version shipped]
+
+### Active (In Progress)
+
+[Requirements currently being worked on]
+
+- [ ] [Requirement 1] — [status/notes]
+
+### Planned (Next)
+
+[Requirements queued for upcoming work]
+
+- [ ] [Requirement 1]
+
+### Out of Scope
+
+[Explicitly excluded requirements — important for preventing scope creep]
+
+- [Excluded feature 1] — [reason]
+
+## Target Users
+
+**Primary:** [Who is the main user]
+- [Key characteristic 1]
+- [Key characteristic 2]
+- [Their main goal/need]
+
+**Secondary:** [Other users, if applicable]
+- [Characteristics]
+
+## Context
+
+**Business Context:**
+[Relevant business information — market, partners, strategy]
+
+**Technical Context:**
+[Relevant technical information — existing systems, integrations, constraints]
+
+## Constraints
+
+### Technical Constraints
+
+<!-- Type-adapted examples:
+     Application: deployment platform limits, framework constraints, auth requirements, external API dependencies
+     Campaign: platform limitations, character limits, image specs, automation constraints
+     Workflow: rate limits, API auth requirements, platform-specific restrictions, error handling needs -->
+
+- [Constraint 1]
+- [Constraint 2]
+
+### Business Constraints
+
+<!-- Type-adapted examples:
+     Application: budget, timeline, team skills, compliance requirements
+     Campaign: budget, timeline, brand guidelines, approval chains, legal review
+     Workflow: SLAs, uptime requirements, data handling policies, vendor contracts -->
+
+- [Constraint 1]
+- [Constraint 2]
+
+### Compliance Constraints
+- [Constraint 1: e.g., "GDPR data handling required"]
+
+## Key Decisions
+
+| Decision | Rationale | Date | Status |
+|----------|-----------|------|--------|
+| [What was decided] | [Why] | [YYYY-MM-DD] | Active / Superseded |
+
+## Success Metrics
+
+<!-- Type-adapted examples:
+     Application: test coverage, uptime, response time, user adoption, error rate
+     Campaign: conversion rate, open rate, click-through rate, ROAS, lead volume, cost per lead
+     Workflow: execution success rate, processing time, error rate, throughput, data accuracy -->
+
+| Metric | Target | Current | Status |
+|--------|--------|---------|--------|
+| [Metric 1] | [Target value] | [Current value] | [On track / At risk / Achieved] |
+
+## Tech Stack / Tools
+
+<!-- Adapts by project type:
+     Application: framework, frontend, database, hosting, auth, payments
+     Campaign: platform (GHL, ClickFunnels), ad platforms (Meta, Google), email tool, analytics
+     Workflow: integration platform (Zapier, Make, custom), APIs, scheduler, monitoring
+     Other: whatever tools/platforms are involved -->
+
+| Layer | Technology | Notes |
+|-------|------------|-------|
+| [Layer/Category] | [Tool/Technology] | [Why this choice] |
+
+## Links
+
+| Resource | URL |
+|----------|-----|
+| Repository | [URL] |
+| Production | [URL] |
+| Documentation | [URL] |
+
+---
+*PROJECT.md — Updated when requirements or context change*
+*Last updated: [YYYY-MM-DD]*
+```
+
+---
+
+## Section Specifications
+
+### What This Is
+**Purpose:** Concrete description of the product/feature.
+**Length:** One paragraph.
+**Focus:** What it is, not how it's built.
+
+### Core Value
+**Purpose:** The ONE thing that matters. Used to guide all decisions.
+**Format:** Single sentence answering "What problem for whom?"
+**Example:** "Attorneys can make informed accept/reject decisions on cases in under 2 minutes without reading raw documents."
+
+### Core Features / Deliverables / Automation Scope
+**Purpose:** The 3-5 primary capabilities or outputs this project delivers. Populated during init walkthrough.
+**Type-adaptive label:**
+- Application → "Core Features"
+- Campaign → "Core Deliverables"
+- Workflow → "Automation Scope"
+- Other → "Core Deliverables"
+**Why:** Plans that reference specific features produce better acceptance criteria than plans referencing "[To be defined]" placeholders.
+
+### Requirements
+**Purpose:** Track feature state across development.
+**Categories:**
+- **Core [Features/Deliverables]:** Top-level project capabilities (populated during init)
+- **Validated:** Shipped and proven
+- **Active:** Currently being implemented
+- **Planned:** Queued for future
+- **Out of Scope:** Explicitly excluded (prevents scope creep)
+
+### Target Users
+**Purpose:** Who we're building for.
+**Include:** Characteristics, goals, needs.
+**Why:** Prevents building for imaginary users.
+**Note:** For campaigns, this is the target audience. For workflows, this may be internal team or system consumers.
+
+### Constraints
+**Purpose:** Hard limits on solutions.
+**Categories:**
+- Technical (platform, technology requirements)
+- Business (partnerships, integrations, budget)
+- Compliance (legal, regulatory, security)
+**Type-adaptive:** Comments in template show relevant examples per project type.
+
+### Key Decisions
+**Purpose:** Record of significant decisions.
+**Include:** What, why, when, status (Active/Superseded).
+**Integration:** Can sync with decision-logger MCP.
+**Note:** Init walkthrough may capture early decisions (tech stack, platform choice, approach). These are pre-populated if gathered.
+
+### Success Metrics
+**Purpose:** Measurable outcomes.
+**Include:** Target values and current state.
+**Type-adaptive:** Application metrics differ from campaign metrics differ from workflow metrics. Comments show relevant examples per type.
+**Why:** Objective success criteria prevent endless scope expansion.
+
+### Tech Stack / Tools
+**Purpose:** What technologies and platforms are involved.
+**Type-adaptive:** "Tech Stack" for applications, "Platforms & Tools" for campaigns, "Integration Stack" for workflows. The table format accommodates all types.
+**Note:** Populated during init walkthrough when user discusses their stack/tools/platforms.

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

@@ -0,0 +1,130 @@
+# RESEARCH.md Template
+
+Template for `.drive/research/{topic-slug}.md` - research findings from subagent discovery.
+
+**Purpose:** Captures research findings for main session review. Created by `/drive:research` or `/drive:research-phase`.
+
+---
+
+## File Template
+
+```markdown
+# Research: {Topic}
+
+**Generated:** {date}
+**Status:** Draft | Reviewed | Integrated
+**Agent Type:** Explore | general-purpose
+**Spawn Time:** {timestamp}
+
+## Topic
+
+{Original research question or topic}
+
+## Sources
+
+{List of sources consulted}
+- [Source 1](url) - {brief description}
+- [Source 2](url) - {brief description}
+- Codebase: {file paths examined}
+
+## Findings
+
+### Key Points
+
+{Main findings as bullets}
+- Finding 1
+- Finding 2
+- Finding 3
+
+### Details
+
+{Detailed findings, organized by subtopic}
+
+#### {Subtopic 1}
+
+{Details, code examples, patterns found}
+
+#### {Subtopic 2}
+
+{Details, code examples, patterns found}
+
+## Recommendations
+
+{Actionable recommendations based on findings}
+- Recommendation 1: {what to do and why}
+- Recommendation 2: {what to do and why}
+
+## Open Questions
+
+{Items that need further investigation}
+- Question 1
+- Question 2
+
+## Subagent Metadata
+
+| Field | Value |
+|-------|-------|
+| Agent Type | {Explore \| general-purpose} |
+| Spawned | {timestamp} |
+| Duration | {approximate} |
+| Token Estimate | {rough estimate if available} |
+
+---
+
+*Created by /drive:research. Review before integrating.*
+*Status should be updated when findings are reviewed or integrated.*
+```
+
+---
+
+## Field Descriptions
+
+| Field | Purpose |
+|-------|---------|
+| `Topic` | Original research question |
+| `Status` | Draft (new), Reviewed (vetted), Integrated (used) |
+| `Agent Type` | Which subagent performed research |
+| `Sources` | Documentation, URLs, or files consulted |
+| `Findings` | Key points and detailed findings |
+| `Recommendations` | Actionable next steps |
+| `Open Questions` | Items needing more research |
+| `Subagent Metadata` | Tracking info for research task |
+
+---
+
+## Status Lifecycle
+
+```
+Draft ──▶ Reviewed ──▶ Integrated
+  │          │            │
+  │          │            └── Findings used in plan/code
+  │          └── Main session vetted findings
+  └── Fresh from subagent
+```
+
+**Draft:** Subagent just completed research
+**Reviewed:** Main session has vetted and confirmed findings
+**Integrated:** Findings have been incorporated into plans or code
+
+---
+
+## Usage Pattern
+
+1. User runs `/drive:research <topic>`
+2. Workflow spawns appropriate subagent
+3. Subagent researches and returns findings
+4. RESEARCH.md created with status: Draft
+5. Main session reviews findings
+6. Status updated to Reviewed when vetted
+7. Status updated to Integrated when used
+
+---
+
+## Relationship to Other Files
+
+| File | Relationship |
+|------|--------------|
+| CONTEXT.md | May inform discussion or result from questions |
+| PLAN.md | May reference research findings |
+| RESEARCH.md | This file (research output) |
+| subagent-criteria.md | Validates when to spawn research |

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

@@ -0,0 +1,328 @@
+# ROADMAP.md Template
+
+Template for `.drive/ROADMAP.md` — the project's phase structure.
+
+**Purpose:** Define milestones and phases. Provides structure, not detailed tasks.
+
+---
+
+## Milestone Status Legend
+
+| Emoji | Status | Meaning |
+|-------|--------|---------|
+| ✅ | Shipped | Milestone complete and archived |
+| 🚧 | In Progress | Active development |
+| 📋 | Planned | Defined but not started |
+
+---
+
+## File Template (Initial v1.0)
+
+```markdown
+# Roadmap: [Project Name]
+
+## Overview
+
+[One paragraph describing the journey from start to finish]
+
+## Current Milestone
+
+**[Milestone Name]** ([version])
+Status: [Not started | In progress | Complete]
+Phases: [X] of [Y] complete
+
+## Phases
+
+**Phase Numbering:**
+- Integer phases (1, 2, 3): Planned milestone work
+- Decimal phases (2.1, 2.2): Urgent insertions (marked with [INSERTED])
+
+Phases execute in numeric order: 1 → 2 → 2.1 → 2.2 → 3 → 3.1 → 4
+
+| Phase | Name | Plans | Status | Completed |
+|-------|------|-------|--------|-----------|
+| 1 | [Name] | [N] | Not started | - |
+| 2 | [Name] | [N] | Not started | - |
+| 3 | [Name] | [N] | Not started | - |
+| 4 | [Name] | [N] | Not started | - |
+
+## Phase Details
+
+### Phase 1: [Name]
+
+**Goal:** [What this phase delivers - specific outcome]
+**Depends on:** Nothing (first phase)
+**Research:** [Unlikely | Likely] ([reason])
+
+**Scope:**
+- [Deliverable 1]
+- [Deliverable 2]
+- [Deliverable 3]
+
+**Plans:**
+- [ ] 01-01: [Brief description]
+- [ ] 01-02: [Brief description]
+- [ ] 01-03: [Brief description]
+
+### Phase 2: [Name]
+
+**Goal:** [What this phase delivers]
+**Depends on:** Phase 1 ([specific dependency])
+**Research:** [Unlikely | Likely] ([reason])
+**Research topics:** [If Likely - what needs investigating]
+
+**Scope:**
+- [Deliverable 1]
+- [Deliverable 2]
+
+**Plans:**
+- [ ] 02-01: [Brief description]
+- [ ] 02-02: [Brief description]
+
+### Phase 2.1: [Name] [INSERTED]
+
+**Goal:** [Urgent work inserted between phases]
+**Depends on:** Phase 2
+**Reason:** [Why this was inserted]
+
+**Plans:**
+- [ ] 02.1-01: [Description]
+
+### Phase 3: [Name]
+
+**Goal:** [What this phase delivers]
+**Depends on:** Phase 2 ([specific dependency])
+**Research:** [Unlikely | Likely]
+
+**Scope:**
+- [Deliverable 1]
+- [Deliverable 2]
+
+**Plans:**
+- [ ] 03-01: [Brief description]
+- [ ] 03-02: [Brief description]
+
+### Phase 4: [Name]
+
+**Goal:** [What this phase delivers]
+**Depends on:** Phase 3
+**Research:** Unlikely (internal patterns)
+
+**Scope:**
+- [Deliverable 1]
+
+**Plans:**
+- [ ] 04-01: [Brief description]
+
+---
+*Roadmap created: [YYYY-MM-DD]*
+*Last updated: [YYYY-MM-DD]*
+```
+
+---
+
+## File Template (After v1.0 Ships)
+
+After completing first milestone, reorganize with milestone groupings:
+
+```markdown
+# Roadmap: [Project Name]
+
+## Milestones
+
+| Version | Name | Phases | Status | Completed |
+|---------|------|--------|--------|-----------|
+| v1.0 | MVP | 1-4 | ✅ Shipped | YYYY-MM-DD |
+| v1.1 | [Name] | 5-6 | 🚧 In Progress | - |
+| v2.0 | [Name] | 7-10 | 📋 Planned | - |
+
+## 🚧 Active Milestone: v1.1 [Name]
+
+**Goal:** [What v1.1 delivers]
+**Status:** Phase [X] of [Y]
+**Progress:** [██████░░░░] 60%
+
+### Phase 5: [Name]
+
+**Goal:** [What this phase delivers]
+**Depends on:** Phase 4
+
+**Plans:**
+- [x] 05-01: [Completed plan]
+- [ ] 05-02: [In progress or pending]
+
+### Phase 6: [Name]
+
+**Goal:** [What this phase delivers]
+**Depends on:** Phase 5
+
+**Plans:**
+- [ ] 06-01: [Brief description]
+
+## 📋 Planned Milestone: v2.0 [Name]
+
+**Goal:** [What v2.0 delivers]
+**Prerequisite:** v1.1 complete
+**Estimated phases:** [N]
+
+[Phase outlines without detailed plans — detail added when milestone begins]
+
+| Phase | Focus | Research |
+|-------|-------|----------|
+| 7 | [Focus] | Unlikely |
+| 8 | [Focus] | Likely |
+| 9 | [Focus] | Unlikely |
+| 10 | [Focus] | Unlikely |
+
+## ✅ Completed Milestones
+
+<details>
+<summary>v1.0 MVP (Phases 1-4) — Shipped YYYY-MM-DD</summary>
+
+### Phase 1: [Name]
+**Goal:** [What was delivered]
+**Plans:** 3 complete
+
+- [x] 01-01: [Description]
+- [x] 01-02: [Description]
+- [x] 01-03: [Description]
+
+### Phase 2: [Name]
+**Goal:** [What was delivered]
+**Plans:** 2 complete
+
+- [x] 02-01: [Description]
+- [x] 02-02: [Description]
+
+### Phase 3: [Name]
+**Goal:** [What was delivered]
+**Plans:** 1 complete
+
+- [x] 03-01: [Description]
+
+### Phase 4: [Name]
+**Goal:** [What was delivered]
+**Plans:** 1 complete
+
+- [x] 04-01: [Description]
+
+**Milestone archive:** See [milestones/v1.0-mvp.md](milestones/v1.0-mvp.md)
+
+</details>
+
+---
+*Last updated: [YYYY-MM-DD]*
+```
+
+---
+
+## Section Specifications
+
+### Overview
+**Purpose:** High-level journey description.
+**Length:** One paragraph.
+**Update:** When project direction changes significantly.
+
+### Current Milestone
+**Purpose:** Quick reference to active milestone.
+**Contains:** Name, version, status, phase progress.
+**Update:** After each phase completion.
+
+### Phases Table
+**Purpose:** At-a-glance view of all phases.
+**Contains:** Phase number, name, plan count, status, completion date.
+**Update:** After each plan/phase completion.
+
+### Phase Details
+**Purpose:** Detailed breakdown of each phase.
+**Contains:**
+- **Goal:** Specific deliverable outcome
+- **Depends on:** Phase dependencies with reason
+- **Research:** Likely/Unlikely with justification
+- **Scope:** Bullet list of deliverables
+- **Plans:** Checklist with brief descriptions
+
+**Update:** During planning; status after completion.
+
+---
+
+## Phase Numbering
+
+**Integer phases (1, 2, 3):** Planned work from roadmap creation.
+
+**Decimal phases (2.1, 2.2):** Urgent insertions.
+- Insert between consecutive integers
+- Mark with [INSERTED] tag
+- Include reason for insertion
+- Filesystem sorts correctly: 2 < 2.1 < 2.2 < 3
+
+**Validation for decimal insertion:**
+- Integer X must exist and be complete
+- Integer X+1 must exist in roadmap
+- Decimal X.Y must not already exist
+- Y >= 1
+
+---
+
+## Depth Configuration
+
+Phase count depends on project depth:
+
+| Depth | Typical Phases | Plans/Phase |
+|-------|----------------|-------------|
+| Quick | 3-5 | 1-3 |
+| Standard | 5-8 | 3-5 |
+| Comprehensive | 8-12 | 5-10 |
+
+**Key principle:** Derive phases from actual work. Depth determines compression tolerance, not a target to hit.
+
+---
+
+## Research Flags
+
+- **Unlikely:** Internal patterns, CRUD operations, established conventions
+- **Likely:** External APIs, new libraries, architectural decisions
+
+When `Research: Likely`:
+- Include `Research topics:` field
+- Consider research phase before implementation
+- Discovery may be required during planning
+
+---
+
+## Status Values
+
+| Status | Meaning |
+|--------|---------|
+| Not started | Phase hasn't begun |
+| In progress | Actively working |
+| Complete | All plans done (add date) |
+| Deferred | Pushed to later (add reason) |
+
+---
+
+## Milestone Sections
+
+### Active Milestone
+**Purpose:** Currently executing milestone with full phase details.
+**Contains:**
+- Goal and status summary
+- Progress bar visualization
+- All phases with plan checklists
+- Research flags where applicable
+
+### Planned Milestone
+**Purpose:** Defined but not started milestone.
+**Contains:**
+- Goal and prerequisites
+- Phase table (focus areas, research likelihood)
+- NOT detailed plans (added when milestone begins)
+
+### Completed Milestones
+**Purpose:** Historical record in collapsible sections.
+**Contains:**
+- Summary header with ship date
+- Phase details (collapsed by default)
+- Link to full milestone archive
+
+**Key principle:** Completed work should not consume visual space — collapse it.