Sprint
Create a new sprint or advance to the next one.
Usage
sprint [description] - Create new sprint from feature description
sprint next - Advance to next sprint from roadmap
Creating from Description
- Parse $ARGUMENTS as feature description
- Generate epic prefix from description
- Create/update prd.json with new sprint
- Generate 10-20 stories via TaskCreate with full metadata (see core skill for schema):
TaskCreate({
subject: "[verb] [specific deliverable]",
description: "## What\n[Exactly what to build]\n\n## Acceptance Criteria\n- [ ] [Testable outcome]\n- [ ] Build passes\n- [ ] No type errors\n\n## Files\n- `src/path/file.ts` - [what to change]",
activeForm: "[Building|Adding] [short desc]",
metadata: {
sid: "[PREFIX]-[NNN]",
sprint: currentSprint,
epic: "[epic name]",
priority: [1-3],
category: "[auth|ui|perf|security|qa|infra]",
type: "feature",
passes: null,
verified: null
}
})
- Include file paths, patterns to follow
- Set dependencies between stories
- Report sprint summary
Advancing (sprint next)
- Read prd.json
- Mark current sprint as "done"
- Find next unscheduled roadmap epic(s)
- Create new sprint with stories from those epics
- Update prd.json
Auto-Archive Check
Before creating a new sprint, check if prd.json needs archiving:
# Count completed sprints. Object.values() handles stories as the id-keyed OBJECT
# core documents as well as an array — .every on an object threw, the catch ate it,
# and this printed nothing at all.
# "complete" = no agent-actionable story left (prd-states.js isActionable): needs-setup is blocked on a HUMAN, not on this sprint's engineering, and archive-prd's keep-list retains those stories — so one credential-blocked leftover must not stop the archive suggestion from ever firing.
node -e "try{const p=require('./prd.json');const sprints=p.sprints||[];const done=sprints.filter(s=>{const st=Object.values(s.stories||{});return s.passes===true||(st.length>0&&st.every(x=>x.passes===true||x.passes==='deferred'||x.passes==='needs-setup'))});console.log('completed:',done.length,'total:',sprints.length,'lines:',JSON.stringify(p).split(',').length)}catch(e){console.log(e.code==='MODULE_NOT_FOUND'?'no prd.json yet - nothing to archive':'archive check failed: '+e.message)}"
| Condition |
Action |
| 3+ completed sprints in prd.json |
Suggest archive before creating new sprint |
| prd.json > 500 lines |
Warn: "prd.json is large, consider archive first" |
Large prd.json wastes tokens on every request. Run the check.
Rules
- HARD CAP: 20 stories per sprint
- Stories must be detailed enough to implement without guessing
- Every story must be testable
- If user asks to "expand", explain roadmap and offer
sprint next
1---2name: sprint3description: Creates or advances sprints in prd.json. Use when starting new work cycles or closing completed sprints.4---56# Sprint78Create a new sprint or advance to the next one.910## Usage1112- `sprint [description]` - Create new sprint from feature description13- `sprint next` - Advance to next sprint from roadmap1415## Creating from Description16171. Parse $ARGUMENTS as feature description182. Generate epic prefix from description193. Create/update prd.json with new sprint204. Generate 10-20 stories via TaskCreate with full metadata (see core skill for schema):21 ```22 TaskCreate({23 subject: "[verb] [specific deliverable]",24 description: "## What\n[Exactly what to build]\n\n## Acceptance Criteria\n- [ ] [Testable outcome]\n- [ ] Build passes\n- [ ] No type errors\n\n## Files\n- `src/path/file.ts` - [what to change]",25 activeForm: "[Building|Adding] [short desc]",26 metadata: {27 sid: "[PREFIX]-[NNN]",28 sprint: currentSprint,29 epic: "[epic name]",30 priority: [1-3],31 category: "[auth|ui|perf|security|qa|infra]",32 type: "feature",33 passes: null,34 verified: null35 }36 })37 ```38 - Include file paths, patterns to follow39 - Set dependencies between stories405. Report sprint summary4142## Advancing (sprint next)43441. Read prd.json452. Mark current sprint as "done"463. Find next unscheduled roadmap epic(s)474. Create new sprint with stories from those epics485. Update prd.json4950## Auto-Archive Check5152Before creating a new sprint, check if prd.json needs archiving:5354```bash55# Count completed sprints. Object.values() handles stories as the id-keyed OBJECT56# core documents as well as an array — .every on an object threw, the catch ate it,57# and this printed nothing at all.58# "complete" = no agent-actionable story left (prd-states.js isActionable): needs-setup is blocked on a HUMAN, not on this sprint's engineering, and archive-prd's keep-list retains those stories — so one credential-blocked leftover must not stop the archive suggestion from ever firing.59node -e "try{const p=require('./prd.json');const sprints=p.sprints||[];const done=sprints.filter(s=>{const st=Object.values(s.stories||{});return s.passes===true||(st.length>0&&st.every(x=>x.passes===true||x.passes==='deferred'||x.passes==='needs-setup'))});console.log('completed:',done.length,'total:',sprints.length,'lines:',JSON.stringify(p).split(',').length)}catch(e){console.log(e.code==='MODULE_NOT_FOUND'?'no prd.json yet - nothing to archive':'archive check failed: '+e.message)}"60```6162| Condition | Action |63|-----------|--------|64| 3+ completed sprints in prd.json | Suggest `archive` before creating new sprint |65| prd.json > 500 lines | Warn: "prd.json is large, consider `archive` first" |6667Large prd.json wastes tokens on every request. Run the check.6869## Rules70- HARD CAP: 20 stories per sprint71- Stories must be detailed enough to implement without guessing72- Every story must be testable73- If user asks to "expand", explain roadmap and offer `sprint next`