planning

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.

16 stars

Best use case

planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using planning should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/planning/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/product/planning/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/planning/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How planning Compares

Feature / AgentplanningStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

1. **Research & Analysis** → `references/research-phase.md`
   - Skip if: Provided with researcher reports

2. **Codebase Understanding** → `references/codebase-understanding.md`
   - Skip if: Provided with scout reports

3. **Solution Design** → `references/solution-design.md`

4. **Plan Organization** → `references/plan-organization.md`

5. **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:**
```yaml
---
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

1. **Vision & Objectives** - SMART goals, alignment
2. **Scope & Deliverables** - In/out of scope, acceptance criteria
3. **Action Steps** - Phased tasks with owners, durations
4. **Resources Required** - People, budget, materials, tools
5. **Timeline & Milestones** - Dates, checkpoints, Gantt
6. **Risks & Contingencies** - Mitigation, early warnings
7. **Success Metrics** - Measurable outcomes, completion criteria

### Quick Templates

- `references/business-plan-template.md`
- `references/personal-goal-template.md`
- `references/generic-plan-template.md`

---

## Pre-Planning Protocol

**ALWAYS execute before creating new plan:**

1. Check for active plan: `test -f docs/plan.md && cat docs/plan.md`
2. If exists: Ask user to continue or create new
3. 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 methodology
- `references/codebase-understanding.md` - Codebase analysis
- `references/solution-design.md` - Architecture patterns
- `references/plan-organization.md` - Plan structure
- `references/output-standards.md` - Task breakdown standards

### Project Templates
- `references/business-plan-template.md`
- `references/personal-goal-template.md`
- `references/generic-plan-template.md`

---

**Plan quality determines implementation success. Be comprehensive.**

Related Skills

agile-planning

16
from diegosouzapw/awesome-omni-skill

Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.

implementation-planning

16
from diegosouzapw/awesome-omni-skill

Use when you have specifications or requirements for multi-step implementation tasks requiring comprehensive documentation for handoff

Capacity Planning

16
from diegosouzapw/awesome-omni-skill

Forecast resource needs and design scaling strategies based on growth projections

planning-with-files

16
from diegosouzapw/awesome-omni-skill

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

dev-workflow-planning

16
from diegosouzapw/awesome-omni-skill

Structured development workflows using /brainstorm, /write-plan, and /execute-plan patterns. Transform ad-hoc conversations into systematic project execution with hypothesis-driven planning, incremental implementation, and progress tracking.

concise-planning

16
from diegosouzapw/awesome-omni-skill

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

architecture-planning

16
from diegosouzapw/awesome-omni-skill

Create detailed architecture plans with decision records and risk assessments. Use when planning significant features or system changes.

architectural-planning

16
from diegosouzapw/awesome-omni-skill

Create detailed technical plans and implementation roadmaps by analyzing project architecture and designing solutions that integrate seamlessly with existing patterns. Use when designing features, planning integrations, making architectural decisions. Triggers: 'plan', 'design', 'architecture', 'approach', 'how should I', 'best way', 'integrate', '계획', '설계', '아키텍처', '접근법', '어떻게 해야', '가장 좋은 방법', '통합', '마이그레이션', working with multi-module features, system boundaries, complex migrations.

u04425-experiment-design-for-nutrition-and-meal-planning

16
from diegosouzapw/awesome-omni-skill

Operate the "Experiment design for nutrition and meal planning" capability in production for nutrition and meal planning workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.

accessibility-planning

16
from diegosouzapw/awesome-omni-skill

Plan accessibility compliance - WCAG 2.2, Section 508, EN 301 549, inclusive design principles, audit planning, and remediation strategies.

planning-phase

16
from diegosouzapw/awesome-omni-skill

Generates implementation plans with code reuse analysis, architecture design, and complexity estimation during the /plan phase. Use when planning feature implementation, analyzing code reuse opportunities, or designing system architecture after specification phase completes. Integrates with 8 project documentation files for constraint extraction. (project)

todo-task-planning

16
from diegosouzapw/awesome-omni-skill

Execute task planning based on the specified file and manage questions[/todo-task-planning file_path --pr --branch branch_name]