sprint-plan

To generate a sprint plan, you provide sprint context like length and theme. The skill reads your systems-index and session-state to decompose goals into an estimated, owner-assigned task list, saving the plan directly to a sprint plan markdown file.

Assigning tasks and estimating effort for a two-week sprint is done by reading current priorities and the systems-index. The skill automatically breaks down goals, flags dependencies, assigns specialists, and captures effort estimates for the backlog.

Yes, this sprint planning workflow is specifically designed for product teams managing two-week cycles. It derives sprint goals and task breakdowns from your backlog inputs to produce a ready-to-review, actionable task roadmap.

Documenting sprint goals and task ownership involves writing the generated plan to a dedicated markdown file. The skill outputs the estimated, owner-assigned task list to a sprint plan document for easy publishing and team review.

You need a markdown systems-index file and current session-state data to start the sprint planning process. The workflow reads these specific inputs to derive sprint goals, decompose tasks, and assign ownership.