skills.rest
antstanley
antstanleyCOMMUNITY
Explore all skills by this author โ†’
GitHub

spec-planner

Decompose a specification into a dependency-ordered graph of reviewable task packages with definitions of done.

Updated May 4, 2026
Search Tags:#implementation planning#task decomposition#definition of done#spec-driven development#kanban#dependency graph#technical specifications
One-click install
npx skills add https://github.com/antstanley/skills --skill spec-planner-antstanley
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: spec-planner
Source: https://github.com/antstanley/skills/tree/main/plugins/spec-planner/skills/spec-planner
Command: npx skills add https://github.com/antstanley/skills --skill spec-planner-antstanley

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve? Turning a specification into an executable build sequence is error-prone: teams either restate the spec, plan work that already exists, or order tasks so nothing is reviewable until the end. This Skill converts a canonical spec set, change spec, or external spec (PRD, RFC, OpenAPI) into a structured implementation plan where every task is independently reviewable and carries a definition of done. ## Core Features & Use Cases - Task decomposition: Slices a spec into coherent, vertically-cut task packages, each mapped back to the spec sections it implements, with build/data/contract/review dependency edges forming a DAG. - Reviewability-first ordering: Topologically sorts the graph, then biases the order toward enablers (auth, app shell, schema, CI) that later work is reviewed through, grouped into milestones ending at demonstrable states. - Kanban plan folder output: Writes .specs/plans/YYYY-MM-DD-title/ with a plan.md (Mermaid graph plus a source-of-truth dependency table) and task files authored into backlog/, each with steps, a definition of done ending in a Reviewable: line, and an optional co-located done certificate. - Use Case: Given a change spec adding tagging to an editor app, the Skill expands its implementation notes into numbered task files (tag type, store migration, picker UI, filtering), orders the store before the UI, and indexes the plan in .specs/README.md. ## Quick Start Ask the agent to plan the implementation of the spec at .specs/ and break it into a dependency-ordered graph of reviewable task packages written to .specs/plans/.

Frequently Asked Questions about spec-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a specification into an implementation plan?โ–ผ

Provide a canonical spec set, change spec, or external spec and ask to plan the implementation. The Skill reads the spec and codebase, decomposes the work into reviewable task packages, orders them by dependency and reviewability, and writes a plan folder under .specs/plans/.

What is a task package in a spec-driven implementation plan?โ–ผ

A task package is one coherent, vertically sliced unit of work that a reviewer can evaluate on its own once merged. Each package is a numbered markdown file with Implements, Depends on, Produces, a step checklist, and a definition of done ending in a Reviewable line.

Can I plan from a PRD or RFC instead of a canonical spec?โ–ผ

Yes. The Skill accepts external formats such as PRDs, RFCs, Gherkin, or OpenAPI documents. It maps each feature or requirement to a task package and notes in Open questions that the source has no canonical schema to check against.

How does the plan decide which tasks to build first?โ–ผ

It topologically sorts the dependency DAG, then biases the order toward enablers that unlock the most downstream review, such as auth, the app shell, persistence schema, and CI. Milestones are grouped so each ends at a demonstrable, reviewable state.

When should I not use spec-planner for a change?โ–ผ

Skip it when the change is small and self-contained, such as a change spec whose three-line Implementation notes already serve as the plan. It is also not for writing specs, reviewing spec-versus-code drift, or producing date-based project schedules.

What are done certificates and are they required?โ–ผ

A done certificate is a per-task verification protocol authored by the companion done-certificates skill, with obligations matching the task's definition of done. Authoring is on by default but can be declined; a separate validating agent later discharges each certificate during the build.

Related Skills

Explore More Software Engineering Skillsโ†’
urban233urban233

feature-spec-creator

Creates self-contained implementation specifications for GitHub issues and feature requests.

Community
Advanced
tazagametazagame

task-cleaner

Archive completed task files into done/ folders by branch or feature name.

Official
Intermediate
OvidOvid

experimental-dedup

Identify semantic duplication across a codebase by analyzing behavior.

Community
Advanced
Priivacy-aiPriivacy-ai
1.6k

spk-team-connectors

Route Spec Kitty connector work across tracker, sync, SaaS, and external services.

Official
Basic