Plan
Convert a spec or design document into PM epics and tasks. Parses sections, extracts deliverables, maps to project hierarchy.From its SKILL.md
npx -y skills add sevenbelowllc/the-library --skill planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
library:plan — Spec to PM Tasks
Turn a design spec into a structured set of PM epics and tasks.
When to Use
- After a design spec is approved (brainstorming output)
- When a new initiative needs to be broken into trackable work
- When importing requirements from external documents
Process
Step 1: Read Spec
Take a spec file path as input. Read and parse:
- Sections and subsections
- Deliverables (features, components, modules)
- Dependencies between deliverables
- Build order (if specified)
Step 2: Map to PM Hierarchy
- Spec → Epic (one epic per major section)
- Section deliverables → Tasks under that epic
- Apply labels based on content:
core,ui,infra,security
Step 3: Present Plan
Show the proposed PM structure:
Epic: "Vault Module"
- Task: "Implement vault init" [core]
- Task: "Implement vault validate" [core]
- Task: "Implement vault parse" [core]
- Task: "Write vault tests" [core]
Step 4: Create (with approval)
Ask: "Create these N epics and M tasks?"
- Call
library_pm_create_epicfor each epic - Call
library_pm_create_taskfor each task, linked to its epic
Step 5: Link Back
Add a comment on each created epic linking to the source spec file.
Token Budget
Weight: Medium Estimated context cost: ~1500 tokens Subagent delegation: No
MCP Tools Used
library_pm_create_epic— create epicslibrary_pm_create_task— create taskslibrary_pm_update— add link-back commentslibrary_config_get— project keys