What problem does it solve? Turning a rough project theme into a milestone of well-scoped, dependency-ordered issues is error-prone: criteria end up vague, dependencies point at wrong issue numbers, and items without an existing code precedent get forced into the plan. This Skill interviews the user about scope, classifies each backlog item by whether a precedent exists in the codebase, and only then creates labels, the milestone, and issues in the tracker. ## Core Features & Use Cases - Precedent-based backlog classification: Each backlog item is tested against the repository for an existing code pattern to extend; items without precedent stay in the backlog for a future wave instead of becoming vague issues. - Interactive scope interview and draft confirmation: The user confirms scope boundaries, the draft issue table, and any new labels before anything is written to the tracker. - Sequential tracker creation: Creates missing labels, the milestone (or a new wave in an existing one), then issues one by one so dependency references point at real issue numbers, via GitHub scripts or Gitea MCP tools. - Use Case: You want to build a UI kit and need it broken into tracker issues. The Skill interviews you on scope, checks which items have code precedents, drafts anchored issues with topological ordering, and creates the milestone after your approval. ## Quick Start Ask the assistant to plan a milestone for your topic, for example: plan a milestone for the UI kit and break it into issues.
