Menu

Individual skill

project-planner

Converts an idea into a structured development plan with milestones, tasks, dependencies, and implementation phases. Use when an idea or feature needs to be broken into a plan before work starts.

skills/architecture/project-planner/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Turn an idea, feature request, or goal into a structured development plan — phases, milestones, concrete tasks, and their dependencies — so work can actually start in the right order instead of everyone improvising sequencing.

## When to Use

- An idea exists but hasn't been broken into actionable phases/tasks yet.
- Kicking off a nontrivial feature or project and want a shared plan before work starts.
- Coordinating work across multiple people/teams where task ordering and dependencies matter.

## What to Analyze / Do

1. **Clarify the goal and scope** — what does "done" look like; what's explicitly out of scope (pair with [Requirements Extractor](../../reasoning/requirements-extractor/) if the goal itself is still vague).
2. **Break into phases** — logical stages of work where each phase produces something usable or verifiable, not arbitrary time-boxed chunks.