Sprint Planning Skill

Transform raw backlog items into a structured, achievable sprint with clear goals, velocity-calibrated scope, and team-ready output.

Reads from / Writes to the Brain

If a professional-brain (brain/) exists, ground in it instead of re-asking for what you already know:

• Read first: priority decisions/ (what the team agreed matters), feature entities/, and open hypotheses/ the sprint might test. Run python3 ../professional-brain/scripts/brain_query.py ./brain "<sprint goal>" and carry each fact's provenance tag through.
• 📥 Propose to the Brain: after producing, propose logging the sprint commitment (goal + committed scope) as a decisions/ record, provenance-tagged. Show it, get a yes, then write with ../professional-brain/scripts/brain_write.py … --commit (append-only, dry-run by default).

Proposes Actions

Once the sprint is agreed, hand it to action-runner: it previews (dry-run, risk-rated), runs only what you approve via the connected action MCP, and records what was done back to the brain. Typical: create a ticket per committed backlog item and set the sprint milestone (🟡). This skill proposes; action-runner gates and runs — never silently.

What This Skill Produces