Skip to content
Skills Library
Management & product · Planning

plan

/plan

Strategic planning and task decomposition. Use for "plan this", "break down", and "roadmap".

Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Strategic planning and task decomposition. Use for "plan this", "break down", and "roadmap".

Triggers from the description

plan thisbreak downroadmap
Original author description

Strategic planning and task decomposition. Use for "plan this", "break down", and "roadmap".

How it works

  1. Skill: plan
  2. When to Use
  3. Planning Process
  4. Output Format
  5. Planning Modes
  6. Constraints
Original SKILL.md headings · 118 lines, 348 words
SKILL.md preview
---
name: plan
description: Strategic planning and task decomposition. Use for "plan this", "break down", and "roadmap".
trigger: /oma:plan
---

## Skill: plan

Create structured plans for complex tasks and projects.

## When to Use

- New projects or features
- Complex refactoring
- Multi-file changes
- When unsure of approach
- Before writing significant code

## Planning Process

### 1. Understand the Goal
- What is the desired end state?
- What problem does this solve?
- What are the constraints?

### 2. Analyze Current State
- What exists today?
- What needs to change?
- What are the dependencies?

### 3. Identify Paths Forward
- Option A: {description}
- Option B: {description}
- Option C: {description}

### 4. Evaluate Options
- Pros and cons of each
- Risk assessment
- Effort vs. value

### 5. Choose Direction
- Select best path
- Document rationale
- Define success criteria

### 6. Decompose into Steps
- Atomic, verifiable tasks
- Dependencies identified
- Estimated effort

## Output Format

```
## Plan: {task/goal}

### Understanding
**Problem:** {what problem this solves}
**Success criteria:** {how we know we're done}
**Constraints:** {limitations}

### Current State
{summary of existing code/state}

### Options Considered

#### Option A: {name}
- **Approach:** {description}
- **Pros:** {list}
- **Cons:** {list}
- **Risk:** {assessment}
- **Effort:** {t-shirt sizing}

#### Option B: {name}
...

### Decision
**Selected:** Option {letter}
**Rationale:** {why this option}

### Implementation Plan

| Step | Task | Dependencies | Effort |
|------|------|--------------|--------|
| 1 | {task} | none | {time} |
| 2 | {task} | step 1 | {time} |
| 3 | {task} | steps 1, 2 | {time} |

### Verification
- [ ] {criterion 1}
- [ ] {criterion 2}
- [ ] {criterion 3}

### Timeline
**Estimated total:** {time}
**Checkpoints:** {milestones}
```

## Planning Modes

### Quick Plan
- 5-10 minutes
- High-level only
- Good for small tasks

### Full Plan
- 20-30 minutes
- Detailed steps
- Risk analysis
- Good for complex work

### RALPLAN
- Consensus-based
- Pre-execution gate
- See `ralplan` skill

## Constraints

- Verify before planning
- Consider multiple approaches
- Keep plans realistic
- Include verification steps
- Update when reality changes

Versions

RepositoryScoreLicence
This page · r3dlex/oh-my-auggie100Apache-2.0
mlophez/polix-ai100Apache-2.0
jeremylongshore/tons-of-skills-marketplace100MIT
duronext/jig100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
xoai/sage100MIT
JoDi-27/JoDi-SDD100MIT

Database snapshot: 13.11.2026 · package version 52d1aaa0b077 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100create-plan
    Create a repository-aware implementation plan, PRD, technical spec, or roadmap item. Use when the user asks to plan a feature, write a PRD or spec, draft a roadmap plan, or produce an implementation-ready feature plan. Discovers local plan conventions; supports quick, standard,…
  • 90teamwork-plan
    Use when the user asks for an implementation plan, task breakdown, checklist, roadmap, or handoff and the outcome and direction are already selected; do not use to choose the direction or execute changes.
  • 100business-strategy
    Business strategy expertise for strategic planning, competitive analysis, market entry, M&A strategy, portfolio management, and strategic decision-making. Use when analyzing competitive positioning, planning growth strategies, or making strategic decisions.
  • 90foreman
    The one entrance to Foreman, which keeps a project's plan and task history. Say what you want in plain language and this routes it to one of the six things Foreman does to a project: add work, show status, correct work, check the roadmap, pick work, or reconcile and pick. It…
  • 100github-project-management
    GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
  • 82donny-plan-phase
    Creates executable PLAN.md files for a roadmap phase, integrating research, planning, and a verification loop. Use to turn a phase, with or without prior discuss-phase context, into verified wave-grouped plans ready to execute. Flags narrow the flow: --skip-research, --gaps…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.