@accelerationguy/accel 1.0.0

package/modules/ignition/templates/planning-application.md

@@ -0,0 +1,193 @@
+# {Project Name}
+
+> {One-line description of what this application does}
+
+**Created:** {date}
+**Type:** Application
+**Stack:** {framework + language + db + cache + deployment}
+**Skill Loadout:** ui-ux-pro-max, /drive:audit, sonarqube scan
+**Quality Gates:** test coverage, security scan, accessibility, performance
+
+---
+
+## Problem Statement
+
+{What does this solve? Who's it for (solo, team, public)? Why build vs buy?}
+
+---
+
+## Tech Stack
+
+{Framework, language, database, caching, deployment platform. Include "Why this stack?" rationale.}
+
+| Layer | Choice | Rationale |
+|-------|--------|-----------|
+| Frontend | {e.g., Next.js, React, Vue} | {why} |
+| Backend | {e.g., Laravel, Node, Python} | {why} |
+| Database | {e.g., SQLite, Postgres, MySQL} | {why} |
+| Cache | {e.g., Redis, none} | {why} |
+| Deployment | {e.g., Docker, Vercel, VPS} | {why} |
+
+### Research Needed
+{If exploring unfamiliar tech: what's known, what needs research, what reference architectures exist.}
+
+---
+
+## Data Model
+
+{Core entities and relationships. Can be rough at ideation stage — refine during Drive planning.}
+
+### Entities
+
+| Entity | Key Fields | Relationships |
+|--------|-----------|---------------|
+| {e.g., User} | {id, email, role} | {has many Projects} |
+
+### Notes
+- {JSON column candidates, polymorphic relationships, soft deletes, etc.}
+
+---
+
+## API Surface
+
+{Key route groups, auth strategy, versioning approach.}
+
+### Auth Strategy
+{Sanctum, JWT, session, API key — and why}
+
+### Route Groups
+
+| Group | Methods | Auth | Purpose |
+|-------|---------|------|---------|
+| {e.g., /api/users} | {GET, POST} | {required} | {description} |
+
+### Internal vs External
+- **Public endpoints:** {list}
+- **Internal/admin endpoints:** {list}
+- **MCP integration points:** {if applicable}
+
+---
+
+## Deployment Strategy
+
+### Local Development
+{Docker Compose services, dev server setup, ignition data}
+
+| Service | Image/Runtime | Port | Purpose |
+|---------|--------------|------|---------|
+| {e.g., app} | {node:20} | {3000} | {main application} |
+
+### Staging / Production
+{CI/CD approach, environment management, hosting}
+
+---
+
+## Security Considerations
+
+{Per-app security concerns — not a generic checklist. What's specific to THIS application?}
+
+- **Auth/Authz model:** {description}
+- **Input validation:** {key areas}
+- **OWASP concerns:** {relevant items for this app}
+- **Secrets management:** {approach}
+- **Rate limiting:** {if applicable}
+
+---
+
+## UI/UX Needs
+
+{Frontend requirements, design approach, key views.}
+
+### Design System
+{Tailwind, shadcn, custom components — and why}
+
+### Key Views / Pages
+
+| View | Purpose | Complexity |
+|------|---------|------------|
+| {e.g., Dashboard} | {primary workspace} | {high — real-time data} |
+
+### Real-Time Requirements
+{WebSockets, SSE, polling — if applicable}
+
+### Responsive Needs
+{Desktop-first, mobile-first, both, or desktop-only}
+
+---
+
+## Integration Points
+
+{External APIs, MCP servers, webhooks, third-party services.}
+
+| Integration | Type | Purpose | Auth |
+|------------|------|---------|------|
+| {e.g., Stripe} | {API} | {payments} | {API key} |
+
+---
+
+## Phase Breakdown
+
+{Independently shippable milestones. Each phase: what's built, what's testable, what's the user-facing outcome. Maps directly to Drive milestones.}
+
+### Phase 1: {Name}
+- **Build:** {what gets built}
+- **Testable:** {what can be verified}
+- **Outcome:** {user-facing result}
+
+### Phase 2: {Name}
+- **Build:** {what gets built}
+- **Testable:** {what can be verified}
+- **Outcome:** {user-facing result}
+
+---
+
+## Skill Loadout & Quality Gates
+
+### Skills Used During Build
+
+| Skill | When It Fires | Purpose |
+|-------|--------------|---------|
+| ui-ux-pro-max | Frontend phases | Design system, component quality |
+| /drive:audit | End of each milestone | Architecture review |
+| sonarqube scan | End of each phase | Code quality, vulnerabilities |
+
+### Quality Gates
+
+| Gate | Threshold | When |
+|------|-----------|------|
+| Test coverage | {e.g., 80%} | {each phase} |
+| Security scan | {pass} | {each phase} |
+| Accessibility | {WCAG AA} | {frontend phases} |
+| Performance | {e.g., LCP < 2s} | {final milestone} |
+
+---
+
+## Design Decisions
+
+{Numbered list of resolved decisions. Each entry: what was decided and why.}
+
+1. **{Decision}**: {choice} — {rationale}
+
+---
+
+## Open Questions
+
+{Unresolved items that need answers before or during build.}
+
+1. {Question}
+
+---
+
+## Next Actions
+
+- [ ] {First concrete step}
+
+---
+
+## References
+
+- {Links, related files, prior art}
+
+---
+
+*Last updated: {date}*

package/modules/ignition/templates/planning-campaign.md

@@ -0,0 +1,138 @@
+# {Campaign Name}
+
+> {One-line description of the campaign objective}
+
+**Created:** {date}
+**Type:** Content/Campaign
+**Goal:** {specific measurable objective}
+**Skill Loadout:** content-manager, revops-expert, content-flywheel-strategist
+**Quality Gates:** deliverables checklist complete, metrics baseline captured
+
+---
+
+## Strategy & Goal
+
+{What's the business objective? Be specific — "grow the channel" is not a goal.}
+
+- **Primary objective:** {measurable target}
+- **Revenue target:** {if applicable}
+- **Lead gen target:** {if applicable}
+- **Brand awareness metric:** {if applicable}
+
+---
+
+## Audience
+
+- **Existing audience:** {Skool members, YouTube subs, email list — sizes}
+- **New acquisition:** {target demographics, where they hang out}
+- **Pain points:** {what keeps them up at night}
+- **Language they use:** {actual phrases, not marketing speak}
+
+---
+
+## Deliverables List
+
+{Enumerate EVERY output. Nothing ambiguous.}
+
+| # | Deliverable | Format | Length | Platform | Due |
+|---|------------|--------|--------|----------|-----|
+| 1 | {e.g., Main video} | {YouTube long-form} | {15-20 min} | {YouTube} | {date} |
+| 2 | {e.g., Teaser clip} | {Instagram Reel} | {60s} | {Instagram} | {date} |
+
+---
+
+## Channels & Platforms
+
+| Platform | Content Type | Format Reqs | Posting Schedule |
+|----------|-------------|-------------|-----------------|
+| YouTube | {long-form} | {16:9, chapters, cards} | {date} |
+| Instagram | {reels, stories} | {9:16, captions} | {date} |
+| LinkedIn | {text posts} | {3000 char max} | {date} |
+| Skool | {community posts} | {markdown} | {date} |
+
+---
+
+## Timeline
+
+| Date | Milestone | Depends On | Owner |
+|------|-----------|------------|-------|
+| {date} | {e.g., Script draft complete} | {—} | {Chris} |
+| {date} | {e.g., Recording done} | {script} | {Chris} |
+| {date} | {e.g., Edit complete} | {recording} | {editor/Chris} |
+| {date} | {e.g., Publish} | {edit} | {Chris} |
+
+### Promotion Windows
+{When to push, when to let organic run, when to follow up}
+
+---
+
+## Success Metrics
+
+{Define BEFORE execution.}
+
+| Metric | Baseline | Target | Measurement Tool |
+|--------|----------|--------|-----------------|
+| {e.g., Video views (7d)} | {current avg} | {target} | {YouTube Analytics} |
+| {e.g., New subscribers} | {current count} | {target} | {YouTube Analytics} |
+| {e.g., Skool signups} | {current} | {target} | {Skool admin} |
+
+### Post-Campaign Review Date
+{When to assess results: ____}
+
+---
+
+## Skill Loadout & Quality Gates
+
+### Skills Used
+
+| Skill | When It Fires | Purpose |
+|-------|--------------|---------|
+| content-manager | Throughout | Pipeline tracking, status updates |
+| revops-expert | Strategy phase | Framework application (Brunson, Hormozi) |
+| content-flywheel-strategist | Post-creation | Repurposing into derivative content |
+
+### Quality Gates
+
+| Gate | When | Pass Criteria |
+|------|------|---------------|
+| Deliverables checklist | Pre-launch | All items produced |
+| Metrics baseline | Pre-launch | Baseline numbers captured |
+
+---
+
+## Design Decisions
+
+1. **{Decision}**: {choice} — {rationale}
+
+---
+
+## Open Questions
+
+1. {Question}
+
+---
+
+## Next Actions
+
+- [ ] {First concrete step}
+
+---
+
+## References
+
+- {Links, related files, prior art}
+
+---
+
+### Drive Decision
+
+{Does this campaign need Drive?}
+- Single deliverable (one video, one post) → No Drive, just do it
+- Multi-deliverable, single week → ACTIVE.md tracking, no Drive
+- Multi-week campaign with dependencies → Drive with timeline-based phases
+
+**Decision:** {Drive / ACTIVE.md tracking / Just do it}
+
+---
+
+*Last updated: {date}*

package/modules/ignition/templates/planning-client.md

@@ -0,0 +1,149 @@
+# {Client Name} — {Project Name}
+
+> {One-line description of what we're building for this client}
+
+**Created:** {date}
+**Type:** Client Website
+**Client:** {name}
+**Skill Loadout:** business-context-extractor, revops-expert, ui-ux-pro-max
+**Quality Gates:** conversion psychology checklist, mobile optimization, client approval
+
+---
+
+## Business Context
+
+{Who's the client? What do they do? Target audience, current online presence.}
+
+- **Client:** {name, industry}
+- **What they do:** {core offering}
+- **Target audience:** {who buys from them}
+- **Current presence:** {existing website, social, reviews}
+- **Brand voice:** {formal, casual, authoritative, friendly}
+- **Brand colors:** {if known}
+- **Existing assets:** {logos, photos, testimonials, case studies}
+
+---
+
+## Competitor Analysis
+
+{3-5 competitors. What they do well, what they miss. Positioning opportunity.}
+
+| Competitor | URL | Strengths | Weaknesses | Positioning Opportunity |
+|-----------|-----|-----------|------------|------------------------|
+| {name} | {url} | {what they do well} | {gaps} | {how client can differentiate} |
+
+---
+
+## Conversion Strategy
+
+{What action should visitors take?}
+
+- **Primary CTA:** {e.g., book a call, buy now, sign up}
+- **Secondary CTAs:** {e.g., download guide, join newsletter}
+
+### Funnel
+```
+{e.g., Landing page → Form → Thank you page → Email follow-up}
+```
+
+### Objection Handling
+{Top 3-5 objections and how the site addresses them}
+
+| Objection | How We Address It |
+|-----------|------------------|
+| {e.g., "Too expensive"} | {e.g., ROI calculator, payment plans, guarantee} |
+
+---
+
+## Content Needs
+
+### Existing Content
+- [ ] Testimonials: {available / need to gather}
+- [ ] Case studies: {available / need to create}
+- [ ] Product/service descriptions: {available / need to write}
+- [ ] Media assets (photos, video): {available / need}
+
+### Content to Create
+
+| Section | Status | Notes |
+|---------|--------|-------|
+| Hero / headline | {exists / needs writing} | {notes} |
+| About | {exists / needs writing} | {notes} |
+| Services | {exists / needs writing} | {notes} |
+| Testimonials | {exists / needs gathering} | {notes} |
+| FAQ | {exists / needs writing} | {notes} |
+
+### Tone & Style Guide
+{Content tone, reading level, industry jargon level}
+
+---
+
+## Tech Approach
+
+- **Method:** {site-launcher-wp standard flow / custom build / other}
+- **Framework:** {Next.js template / WordPress conversion / static HTML}
+- **Hosting:** {Vercel, client's existing hosting, other}
+- **Domain/DNS:** {client provides / we manage / TBD}
+- **CMS needs:** {client self-edits / we maintain / headless CMS}
+
+---
+
+## Timeline & Deliverables
+
+| Date | Milestone | Deliverable | Client Action |
+|------|-----------|-------------|---------------|
+| {date} | {Kickoff} | {—} | {Provide assets, access} |
+| {date} | {First draft} | {staging URL} | {Review, feedback} |
+| {date} | {Revisions} | {updated staging} | {Final approval} |
+| {date} | {Launch} | {live site} | {DNS update if needed} |
+
+### Client Review Checkpoints
+{When does the client see work? How do they provide feedback? What's the approval process?}
+
+---
+
+## Skill Loadout & Quality Gates
+
+### Skills Used During Build
+
+| Skill | When It Fires | Purpose |
+|-------|--------------|---------|
+| business-context-extractor | Discovery | Crawl existing site for business details |
+| revops-expert | Strategy | Conversion frameworks, offer positioning |
+| ui-ux-pro-max | Build | Design system, responsive layout |
+
+### Quality Gates
+
+| Gate | When | Pass Criteria |
+|------|------|---------------|
+| Conversion psychology checklist | Pre-launch | All items addressed |
+| Mobile optimization | Pre-launch | Fast, responsive, no layout breaks |
+| Client approval | Each milestone | Written sign-off |
+
+---
+
+## Design Decisions
+
+1. **{Decision}**: {choice} — {rationale}
+
+---
+
+## Open Questions
+
+1. {Question}
+
+---
+
+## Next Actions
+
+- [ ] {First concrete step}
+
+---
+
+## References
+
+- {Links, related files, prior art}
+
+---
+
+*Last updated: {date}*

package/modules/ignition/templates/planning-utility.md

@@ -0,0 +1,112 @@
+# {Tool Name}
+
+> {One sentence. If you need two, this might not be a utility.}
+
+**Created:** {date}
+**Type:** Utility Tool
+**Location:** tools/{personal|shareable|mcp-servers}/
+**Skill Loadout:** {usually minimal}
+**Quality Gates:** {done criteria pass}
+
+---
+
+## Problem Statement
+
+{What specific problem does this solve? One sentence. If you can't say it in one sentence, it might not be a utility tool.}
+
+---
+
+## Scope Guard
+
+{Actively resist expansion.}
+
+- **Can this be one file?** {yes/no — if no, why not?}
+- **Can this be one function?** {yes/no — if no, why not?}
+- **Single script or project structure?** {script / project — justify if project}
+
+### What This Does
+- {capability 1}
+- {capability 2}
+
+### What This Does NOT Do
+- {explicitly excluded — resist feature creep}
+
+---
+
+## User & Distribution
+
+- **Audience:** {just me / Skool community / Claude Code users / MCP consumers}
+- **Location:** {tools/personal/ | tools/shareable/ | tools/mcp-servers/production/}
+- **Packaging:** {standalone script / npm package / MCP server / slash command}
+
+---
+
+## Dependencies
+
+{Minimize ruthlessly. If dependencies are heavy, this might be an Application, not a Utility.}
+
+| Dependency | Why | Can We Avoid It? |
+|-----------|-----|-----------------|
+| {e.g., node-fetch} | {HTTP requests} | {no — core need} |
+
+---
+
+## Interface
+
+- **Invocation:** {CLI args / MCP tool call / slash command / import}
+- **Input:** {format, required args, optional args}
+- **Output:** {format, stdout, file, return value}
+
+### Examples
+```
+{example invocation and expected output}
+```
+
+---
+
+## Done Criteria
+
+{3-5 concrete test cases. If you can't define done criteria easily, scope is too big.}
+
+- [ ] {Test case 1: input → expected output}
+- [ ] {Test case 2: input → expected output}
+- [ ] {Test case 3: edge case → expected behavior}
+
+---
+
+## Design Decisions
+
+1. **{Decision}**: {choice} — {rationale}
+
+---
+
+## Open Questions
+
+1. {Question}
+
+---
+
+## Next Actions
+
+- [ ] {First concrete step — probably "just build it"}
+
+---
+
+## References
+
+- {Links, related files, prior art}
+
+---
+
+### Drive Decision
+
+{Does this need Drive?}
+- < 200 lines, single file → **Just build it, no Drive**
+- Multiple files, tests needed → Light Drive (1 milestone, 1-2 phases)
+- Complex with integrations → Probably an Application, not a Utility
+
+**Decision:** {Just build it / Light Drive / Reclassify as Application}
+
+---
+
+*Last updated: {date}*

package/modules/ignition/templates/planning-workflow.md

@@ -0,0 +1,125 @@
+# {Project Name}
+
+> {One-line description of what this workflow does}
+
+**Created:** {date}
+**Type:** Claude Code Workflow
+**Skill Loadout:** {skills relevant to building this — e.g., /drive:audit}
+**Quality Gates:** {quality checks — e.g., governance review, integration testing}
+
+---
+
+## Problem Statement
+
+{What workflow pain or gap does this solve? Be specific about what's broken, slow, or missing.}
+
+---
+
+## Scope Definition
+
+{What components make up this workflow? Check all that apply and describe each.}
+
+### Components
+- [ ] Slash command(s): {list}
+- [ ] Skill(s): {list}
+- [ ] Vector domain(s): {new or modified}
+- [ ] Hook(s): {list}
+- [ ] MCP server tool(s): {list}
+- [ ] Templates / file generators: {list}
+- [ ] Modifications to existing commands: {list}
+
+### Out of Scope
+- {Explicitly excluded items}
+
+---
+
+## Integration Map
+
+### Systems Touched
+
+| System | How It's Touched | Changes Needed |
+|--------|-----------------|----------------|
+| {e.g., Vector} | {e.g., new domain, rule updates} | {specific changes} |
+| {e.g., Drive} | {e.g., new input format} | {specific changes} |
+| {e.g., Existing commands} | {e.g., /graduate modification} | {specific changes} |
+
+### Systems NOT Touched
+- {List systems explicitly unaffected to prevent scope creep}
+
+---
+
+## Interaction Design
+
+{Map the user experience as conversation flows.}
+
+### Entry Point
+```
+User: /{command}
+Claude: {what happens}
+```
+
+### Conversation Flow
+{Step-by-step: what Claude asks, what user provides, what Claude does with it. Include branching logic if applicable.}
+
+### Session End
+{What artifacts are produced? What does Claude report? What's the next step prompt?}
+
+---
+
+## Output Artifacts
+
+| Artifact | Location | Purpose |
+|----------|----------|---------|
+| {file/command/domain} | {path} | {what it does} |
+
+---
+
+## Downstream Handoff
+
+{How does the output connect to the next stage? What metadata travels? What does the next tool expect?}
+
+---
+
+## Skill/Tool Discovery
+
+{Skills or tools that could enhance this workflow but don't exist yet.}
+
+| Skill | When It Would Fire | What It Would Do |
+|-------|-------------------|-----------------|
+| {name} | {trigger} | {description} |
+
+---
+
+## Edge Cases & Constraints
+
+{What shouldn't this workflow do? When does it NOT apply? What happens with unexpected input?}
+
+- {Edge case and how to handle it}
+
+---
+
+## Design Decisions
+
+1. **{Decision}**: {choice} — {rationale}
+
+---
+
+## Open Questions
+
+1. {Question}
+
+---
+
+## Next Actions
+
+- [ ] {First concrete step}
+
+---
+
+## References
+
+- {Links, related files, prior art}
+
+---
+
+*Last updated: {date}*