agentleFS
Sign inStart free
Data-WiseData-Wise/craft/skills/planning/SKILL.md

project-planner

Skill4 starsChanged 12 days agoMITView on GitHub

This skill should be used when the user asks to "plan a project", "estimate effort", or needs help with task breakdown and project management strategy — NOT for producing a committed planning artifact (feature breakdown, sprint backlog, roadmap file); see `plan-orchestrator` for that. Provides expert guidance on feature planning, estimation, and delivery management.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-designer and security-auditor.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AutumnsGroveSkill

    api-designer

    Design and document RESTful and GraphQL APIs with OpenAPI/Swagger specifications, authentication patterns, versioning strategies, and best practices. Use for: (1) Creating API specifications, (2) Designing REST endpoints, (3) GraphQL schema design, (4) API authentication and authorization, (5) API versioning strategies, (6) Documentation generation

    Also in 3 projects that use this

  • nahisahoSkill

    security-auditor

    security-auditor skill

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 12
  2. Distinctive:

    Call out quick wins vs. longer efforts when discussing an approach

    line 84

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Planner Skill

Expert in project planning, estimation, and delivery management.

When to Use

Use this skill when:

  • Planning new features or projects (strategy, not the artifact itself)
  • Thinking through how to approach complex work
  • Estimating effort and timelines
  • Managing project risks
  • Advising on roadmap and milestone strategy (not generating the roadmap file — see plan-orchestrator)

Capabilities

Advisory only — this skill talks through an approach, it never emits the file/backlog itself. Hand off to plan-orchestrator the moment "advice" becomes "produce the doc."

Feature Planning Strategy

  • How to approach user-story framing
  • How to think about task breakdown (WBS) before committing one to paper
  • How to reason about dependency ordering
  • What makes acceptance criteria testable
  • How to scope an MVP vs. full build

Estimation Coaching

  • Effort estimation techniques and their trade-offs
  • How to assess complexity honestly
  • Risk-adjusted timeline reasoning
  • Capacity-planning approaches
  • Reading velocity trends

Delivery Management Advice

  • Sprint-planning approach and capacity trade-offs
  • Milestone-definition strategy
  • How to track progress without false precision
  • Risk identification frameworks
  • Stakeholder-communication approach

Agile Coaching

  • Scrum ceremony facilitation advice
  • Kanban workflow design
  • Backlog-grooming approach
  • Retrospective facilitation technique
  • Continuous-improvement framing

Example Prompts

"What's a reasonable approach to breaking down this feature?"
"What should we prioritize for the next sprint?"
"What's a sound roadmap strategy for our Q1 goals?"
"What are the risks in this project plan?"
"How should we estimate this complex feature?"

What This Skill Gives You

Conversational advice and reasoning, not a file:

  • A recommended approach to breaking down a feature
  • A recommended sprint-capacity strategy
  • A recommended roadmap/milestone strategy
  • A risk assessment talked through in conversation
  • Milestone-definition guidance

Need the actual artifact instead (a written SPEC-*.md, feature breakdown, sprint backlog, or roadmap file)? That's plan-orchestrator, not this skill.

ADHD-Friendly Conversation Style

  • Break the reasoning into short, clearly-labeled steps rather than one long paragraph
  • Name priorities explicitly (what matters most, what can wait) instead of a flat list
  • Call out quick wins vs. longer efforts when discussing an approach
  • End with one concrete recommended next step, not an open-ended set of options

Integration

  • plan-orchestrator — the moment advice needs to become a committed file (feature breakdown, sprint backlog, roadmap, ORCHESTRATE-*.md), hand off here. This skill never produces those artifacts itself.
  • dev/git skill (ask "create feature branch") — once a strategy is agreed, create the feature branch to act on it (folded from /craft:git:branch, 2026-07 v4 consolidation).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free