pantheon-ai/implementation-planner
Converts a PRD or requirements document into a structured, phased implementation plan with individual phase files and granular per-task files written to .context/plans/. Also restructures existing monolithic planning documents into digestible, hierarchical directory structures. Creates a root plan index summarising all phases, a numbered phase file per phase, and a numbered task file per task inside each phase directory.
92
93%
Does it follow best practices?
Impact
91%
3.25xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that excels across all dimensions. It provides highly specific actions with concrete outputs (directory structure, file types), includes comprehensive natural trigger terms in an explicit 'Use when...' clause, and carves out a distinct niche around PRD/requirements-to-plan conversion that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: converts PRD to structured plan, creates phase files, creates task files, writes to specific directory (.context/plans/), restructures monolithic documents, creates root plan index, numbered phase files, and numbered task files. | 3 / 3 |
Completeness | Clearly answers both what (converts PRD to structured phased implementation plan with specific file outputs) AND when (explicit 'Use when...' clause with comprehensive list of trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'implementation plan', 'break down a PRD', 'convert requirements to tasks', 'project phases', 'roadmap', 'sprints', 'task breakdown', 'monolithic planning doc', 'decompose a spec', 'phases and tasks'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on PRD-to-plan conversion with distinct output structure (.context/plans/, phase files, task files). The specific file hierarchy and planning document focus makes it unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with exceptional actionability and workflow clarity. The two-mode structure is well-documented with clear decision tables, concrete examples, and explicit validation requirements. The main weakness is some verbosity in the anti-patterns section where similar points are restated multiple times, though this redundancy may be intentional for emphasis on critical guardrails.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy, particularly in the anti-patterns section where the same points are made multiple times with slight variations. The guardrail explanation is repeated extensively across multiple sections. | 2 / 3 |
Actionability | Excellent actionability with concrete shell commands, specific file paths, executable verification examples, and copy-paste ready code blocks. The worked examples show exact command sequences to run. | 3 / 3 |
Workflow Clarity | Outstanding workflow clarity with explicit numbered steps, validation checkpoints (validate-plan.sh must exit 0 before reporting), clear decision tables for mode selection, and explicit feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Well-structured with clear navigation to reference files (mode2-advanced.md, example-transformation.md, templates, schemas). The main content provides actionable quick-start guidance while deferring deep dives to linked references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (722 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents