project-planner

Sterne3

Forks0

Aktualisiert13. Juli 2026 um 17:13

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

Data-Wise

Data-Wise/craft

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

ProjektmanagementspezialistenWirtschafts- und Finanzberufe·SOC 13-1082

SKILL.md

readonly

name	project-planner
description	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.

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).

Mehr aus diesem Repository

gleiches Repository

preflight-check

Data-Wise/craft

This skill should be used when the user asks to "pre-flight check", "validate before commit", "validate before PR", "validate before deploy", "is this ready to ship", "check readiness", "run pre-flight", "validate project state", or wants context-aware validation across commit/PR/release/deploy boundaries. Orchestrates universal validators (lint, tests, types, version sync, stale refs, docs, hook conflicts) and supports generating new custom validators.

2026-07-273

prompt-refiner

Data-Wise/craft

This skill should be used when a command's --refine flag is set, or the user asks to "refine my prompt", "optimize this prompt", "make this request sharper" — rewrites a vague natural-language request into a specific, well-structured prompt using project context, shows before/after, and confirms before the caller proceeds. Replaces the deprecated /craft:refine command.

2026-07-263

release

Data-Wise/craft

This skill should be used when the user asks to "release", "create a release", "ship it", "publish a new version", "bump version and release", "cut a release", or mentions releasing to GitHub/npm/PyPI. Orchestrates the full release pipeline from pre-flight checks through GitHub release creation.

2026-07-253

adhd-workflow

Data-Wise/craft

ADHD-friendly session and task workflow for craft users — captures context at session end, restores it at session start, picks the next task, breaks through blockers, holds focus on one task, reviews a craft spec, or refines a vague craft prompt. Use when wrapping up or resuming a coding session, when deciding what to work on next (also "what's next", "pick a task for me", "give me something to do"), when stuck or in decision paralysis, when focusing on a single craft task, or when reviewing/refining a craft spec or prompt. The full intent-to-operation map is in the "When to Use" table below.

2026-07-253

git-workflow

Data-Wise/craft

This skill should be used when the user asks to "init a repo", "set up git", "manage branches", "switch branch", "create a worktree", "list worktrees", "clean merged branches", "sync with remote", "git activity", "git recap", "protect main", "apply branch protection", "bypass protection", "undo a commit", "fix a git mistake", or mentions git lifecycle, worktrees, branch protection, GitHub-side baseline protection, safety rails, or learning git workflows. Covers craft's full git lifecycle — repo init, branch and worktree management, remote sync, status/recap, local and GitHub-side branch protection, and the learning/safety reference docs.

2026-07-253

brainstorm-insights

Data-Wise/craft

This skill should be used when the user asks "what's my friction", "session insights", "friction report", "what patterns am I hitting", "analyze my sessions", "generate insights report", "aggregate facets", or "show CLAUDE.md suggestions". Aggregates session facet history into a friction/goals report. Formerly bundled with the brainstorm skill (ideation); split out because the two operations share no input or output. Directory name kept as brainstorm-insights for path stability — tests and references/insights.md reference it.

2026-07-183

name	project-planner
description	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.

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).