Planning
Universal planning methodology for technical implementation and general project planning.
Mode Selection
| Project Type |
Mode |
Key Focus |
| Software/Technical |
Implementation |
Codebase analysis, architecture, code changes |
| Business/Personal/Creative |
Project |
Goals, milestones, resources, timeline |
Technical Implementation Planning
Use when: Planning software features, system architecture, technical solutions
Core Principles
Always honor YAGNI, KISS, and DRY principles.
Be honest, be brutal, straight to the point, and be concise.
Workflow
Research & Analysis → references/research-phase.md
- Skip if: Provided with researcher reports
Codebase Understanding → references/codebase-understanding.md
- Skip if: Provided with scout reports
Solution Design → references/solution-design.md
Plan Organization → references/plan-organization.md
Task Breakdown → references/output-standards.md
Output Structure
plans/
└── YYYYMMDD-HHmm-plan-name/
├── research/
├── reports/
├── scout/
├── plan.md
└── phase-XX-*.md
Requirements
- DO NOT implement code - only create plans
- Self-contained with necessary context
- Include code snippets/pseudocode when clarifying
- Provide options with trade-offs
- Detailed enough for junior developers
Project Planning (Non-Technical)
Use when: Business, personal, creative, academic, event planning
Domains
- Business: Product launches, marketing, process improvements
- Personal: Career development, learning, lifestyle changes
- Creative: Writing, art, content creation
- Academic: Research, thesis, study programs
- Events: Conferences, weddings, community events
Plan Format
Location: docs/plans/PLAN-YYYYMMDD-HHMM-{slug}.md
Frontmatter:
---
plan_id: PLAN-YYYYMMDD-HHMM-{slug}
title: [Project Name]
created: YYYY-MM-DD HH:MM
status: draft | active | completed | on_hold
category: business | personal | creative | academic | event
phase: planning | execution | monitoring | complete
priority: critical | high | medium | low
---
Required Sections
- Vision & Objectives - SMART goals, alignment
- Scope & Deliverables - In/out of scope, acceptance criteria
- Action Steps - Phased tasks with owners, durations
- Resources Required - People, budget, materials, tools
- Timeline & Milestones - Dates, checkpoints, Gantt
- Risks & Contingencies - Mitigation, early warnings
- Success Metrics - Measurable outcomes, completion criteria
Quick Templates
references/business-plan-template.mdreferences/personal-goal-template.mdreferences/generic-plan-template.md
Pre-Planning Protocol
ALWAYS execute before creating new plan:
- Check for active plan:
test -f docs/plan.md && cat docs/plan.md
- If exists: Ask user to continue or create new
- If none: Proceed with new plan creation
Quality Standards
Technical Plans
- Consider long-term maintainability
- Address security and performance
- Validate against codebase patterns
- Research thoroughly when uncertain
Project Plans
- All 7 sections present
- Each step has owner and deadline
- Resources are realistic
- Risks have contingencies
- Metrics are SMART
Both Types
- Be thorough and specific
- Simple, understandable structure
- Action-oriented
- Clear next steps
References
Technical Implementation
references/research-phase.md - Research methodologyreferences/codebase-understanding.md - Codebase analysisreferences/solution-design.md - Architecture patternsreferences/plan-organization.md - Plan structurereferences/output-standards.md - Task breakdown standards
Project Templates
references/business-plan-template.mdreferences/personal-goal-template.mdreferences/generic-plan-template.md
Plan quality determines implementation success. Be comprehensive.
1---2name: planning-23description: Universal planning for technical and non-technical projects. Domains: software implementation, business, personal, creative, academic, events. Capabilities: feature planning, system architecture, goal setting, milestone planning, requirement breakdown, trade-off analysis, resource allocation, risk assessment. Actions: plan, architect, design, evaluate, breakdown, structure projects. Keywords: implementation plan, technical design, architecture, roadmap, project plan, strategy, goal setting, milestones, timeline, action plan, SMART goals, sprint planning, task breakdown, OKRs. Use when: planning features, designing architecture, creating roadmaps, setting goals, organizing projects, breaking down requirements.4---5
6# Planning
7
8Universal planning methodology for technical implementation and general project planning.
9
10## Mode Selection
11
12| Project Type | Mode | Key Focus |
13|--------------|------|-----------|
14| **Software/Technical** | Implementation | Codebase analysis, architecture, code changes |
15| **Business/Personal/Creative** | Project | Goals, milestones, resources, timeline |
16
17---
18
19## Technical Implementation Planning
20
21**Use when:** Planning software features, system architecture, technical solutions
22
23### Core Principles
24
25Always honor **YAGNI**, **KISS**, and **DRY** principles.
26**Be honest, be brutal, straight to the point, and be concise.**
27
28### Workflow
29
301. **Research & Analysis** → `references/research-phase.md`
31 - Skip if: Provided with researcher reports
32
332. **Codebase Understanding** → `references/codebase-understanding.md`
34 - Skip if: Provided with scout reports
35
363. **Solution Design** → `references/solution-design.md`
37
384. **Plan Organization** → `references/plan-organization.md`
39
405. **Task Breakdown** → `references/output-standards.md`
41
42### Output Structure
43
44```
45plans/
46└── YYYYMMDD-HHmm-plan-name/
47 ├── research/
48 ├── reports/
49 ├── scout/
50 ├── plan.md
51 └── phase-XX-*.md
52```
53
54### Requirements
55
56- DO NOT implement code - only create plans
57- Self-contained with necessary context
58- Include code snippets/pseudocode when clarifying
59- Provide options with trade-offs
60- Detailed enough for junior developers
61
62---
63
64## Project Planning (Non-Technical)
65
66**Use when:** Business, personal, creative, academic, event planning
67
68### Domains
69
70- **Business**: Product launches, marketing, process improvements
71- **Personal**: Career development, learning, lifestyle changes
72- **Creative**: Writing, art, content creation
73- **Academic**: Research, thesis, study programs
74- **Events**: Conferences, weddings, community events
75
76### Plan Format
77
78**Location:** `docs/plans/PLAN-YYYYMMDD-HHMM-{slug}.md`
79
80**Frontmatter:**
81```yaml
82---
83plan_id: PLAN-YYYYMMDD-HHMM-{slug}
84title: [Project Name]
85created: YYYY-MM-DD HH:MM
86status: draft | active | completed | on_hold
87category: business | personal | creative | academic | event
88phase: planning | execution | monitoring | complete
89priority: critical | high | medium | low
90---
91```
92
93### Required Sections
94
951. **Vision & Objectives** - SMART goals, alignment
962. **Scope & Deliverables** - In/out of scope, acceptance criteria
973. **Action Steps** - Phased tasks with owners, durations
984. **Resources Required** - People, budget, materials, tools
995. **Timeline & Milestones** - Dates, checkpoints, Gantt
1006. **Risks & Contingencies** - Mitigation, early warnings
1017. **Success Metrics** - Measurable outcomes, completion criteria
102
103### Quick Templates
104
105- `references/business-plan-template.md`
106- `references/personal-goal-template.md`
107- `references/generic-plan-template.md`
108
109---
110
111## Pre-Planning Protocol
112
113**ALWAYS execute before creating new plan:**
114
1151. Check for active plan: `test -f docs/plan.md && cat docs/plan.md`
1162. If exists: Ask user to continue or create new
1173. If none: Proceed with new plan creation
118
119---
120
121## Quality Standards
122
123### Technical Plans
124- Consider long-term maintainability
125- Address security and performance
126- Validate against codebase patterns
127- Research thoroughly when uncertain
128
129### Project Plans
130- All 7 sections present
131- Each step has owner and deadline
132- Resources are realistic
133- Risks have contingencies
134- Metrics are SMART
135
136### Both Types
137- Be thorough and specific
138- Simple, understandable structure
139- Action-oriented
140- Clear next steps
141
142---
143
144## References
145
146### Technical Implementation
147- `references/research-phase.md` - Research methodology
148- `references/codebase-understanding.md` - Codebase analysis
149- `references/solution-design.md` - Architecture patterns
150- `references/plan-organization.md` - Plan structure
151- `references/output-standards.md` - Task breakdown standards
152
153### Project Templates
154- `references/business-plan-template.md`
155- `references/personal-goal-template.md`
156- `references/generic-plan-template.md`
157
158---
159
160**Plan quality determines implementation success. Be comprehensive.**
diegosouzapw