// Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.
| name | sprint-planner |
| description | Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals. |
| version | 0.1.0 |
| status | experimental |
| risk | low |
| tags | ["product","writes-files"] |
roadmap-synthesizer)| Name | Type | Required | Notes |
|---|---|---|---|
tickets | list / path | yes | candidate work items with priority + estimates |
capacity | object | yes | per-engineer days available |
previous_carry | list | no | items rolling over from last sprint |
commitments | list | no | OKR / stakeholder commitments that must land |
sprint-plan.md with: Sprint goal, Committed, Stretch, Non-goals, Risks.
Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered, and the chosen path.
Use when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors, pagination, auth, and naming.
Use when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas) before any analysis.
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
Use after a session to promote useful episodic notes from logs/episodic/ into distilled, dated entries in MEMORY.md and memory/semantic/.