drobins25/craft / skills/plan-chunks
plan-chunks
VerifiedThis skill should be used when the user asks to "plan chunks", "break this down", "plan the implementation", or when a story has status planning and needs implementation details before building. Required before any story can be implemented. Turns a story into a chunk-by-chunk build plan with file lists, the contracts chunks share, named tests and risks. Supports parallel planning of multiple stories via batch mode.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.8 KB |
| references/batch-triage.md | markdown | 21.5 KB |
| references/chunk-format-guide.md | markdown | 7.5 KB |
| references/research-integration.md | markdown | 7.5 KB |
| references/spark-extraction.md | markdown | 1.1 KB |
| references/team-planning.md | markdown | 6.7 KB |
references/spark-extraction.md
View on GitHub# Spark Extraction Guide
How to extract concrete requirements from a story's Spark prose. These requirements become the constraints that chunks must fulfill.
---
## Method
The Spark is 2-3 sentences of freeform prose. Pull out the distinct outcomes or behaviors it describes — not every word, but every intent. Ask: "If this requirement isn't addressed, did we actually deliver the story?"
---
## Worked Examples
**Example 1:**
> Spark: "The discovery page filter labels are misleading — 'Transcripts/Videos' actually filters by in-bank status. Rename to 'Saved/Not Saved' on Discovery, and add a real content type filter on Knowledge Bank."
Requirements:
1. Discovery filter renamed from "Transcripts/Videos" to "Saved/Not Saved"
2. Knowledge Bank gets a content type filter for Videos vs Transcripts
**Example 2:**
> Spark: "The agent never offers implementation during story creation. Story-new mode is purely creative — no code suggestions, no implementation planning."
Requirements:
1. Agent does not offer implementation during story creation
2. Story-new mode is creative-only
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |