project-epic-plannerlisted

# Project Epic Planner Turn a project description into an epic/story breakdown that's ready to review: every ticket self-contained, every leaf story testable, every dependency real. The output is a plan file, not GitHub issues — turning an approved plan into issues is `github-project-bootstrap`'s job, and only when a human explicitly asks for it. This skill is model-invoked on purpose (no `disable-model-invocation`): planning is reversible. It writes a document someone reads and edits; nothing acts on it automatically. See `docs/adr/0002-invocation-control-on-github-actions.md`. ## Required reading Before generating **any** ticket, read [`references/ticket-quality-rules.md`](references/ticket-quality-rules.md) in full. Its five rules aren't style preferences — each is a mistake that was made and corrected on a real project, and a plan that breaks one isn't ready for review. ## Workflow ### 1. Pin down the project template Get the project into the shape defined in [`references/project-template.md`](references/project-template.md): `project_name`, `one_line_description`, `objective`, `in_scope`, `out_of_scope`, optional `known_pieces`, `repo.visibility`, `repo.license`, and `target_milestone_name`. If the user gave a filled-in template, use it. Otherwise draft one from what they've said, show it, and get it confirmed before planning — ask about anything you'd otherwise be guessing, especially scope boundaries. Apply the template's validation rules; send back a failing t