kickoff_sprint_discussion

Sprint planning preparation aggregates backlog items from docs/BACKLOG.md, MEMORY.md, and recent git commits to categorize themes and propose a prioritized sprint brief. This approach builds a structured plan with rationale-backed top items before the planning meeting begins.

Backlog categorization groups items into themes like Infrastructure, Agent behavior, Orchestrator features, Extensibility, and Documentation gaps. This thematic grouping shapes a prioritized plan by applying dependency and risk considerations to propose a top 3-5 sprint items.

Recent git commits provide context to shape a prioritized sprint plan by aggregating recent changes alongside backlog items. The 10-recent-commits git log and MEMORY.md inform dependency and risk assessment for proposing top sprint priorities.

Sprint planning from a backlog requires specific documentation inputs, primarily docs/BACKLOG.md and MEMORY.md. These files provide the backlog context and recent change history needed to generate categorized themes and a ready-to-share sprint brief.

Generating a sprint brief with clarifying questions involves aggregating backlog items and recent commits into thematic categories. The output is a ready-to-share document proposing top sprint items with rationale and planning prompts for the team meeting.

Automated backlog categorization should not be used when an active sprint already exists, as this skill specifically applies when no active sprint is present. It relies on static backlog context rather than real-time sprint progress tracking.