GitHub project planning and breakdown into epics, features, stories, enablers and tests with dependencies and priorities

1. Prepare the feature documents in the expected paths: /docs/ways-of-work/plan/{epic-name}/{feature-name}.md, along with technical-breakdown.md and implementation-plan.md inside the feature folder. 2. Ask the agent to activate the breakdown-plan skill and specify the epic name and the feature name. Example user request: "Use breakdown-plan for the user-onboarding epic and the email-verification feature, and create the project plan and the issue creation checklist based on the existing documents." 3. Review the generated project-plan.md file. It includes a project overview, a hierarchy diagram, issue templates, a priority matrix (P0 to P3), Fibonacci estimates and T-shirt sizes. 4. Review the issues-checklist.md file, then use it to manually create the epic, feature, story and enabler issues in GitHub, linking dependencies and applying the suggested labels. 5. You can adapt the suggested GitHub Actions workflow examples to automate issue creation or status updates on the project board. Review and test them before adopting them, as they are partial and incomplete examples.

The skill requires an agent capable of reading repository files and writing new Markdown files. The feature documents must already exist in the /docs/ways-of-work/plan/ path, and the skill refers to related skills for preparing them, such as plan-feature-prd, plan-epic-arch and plan-test. The skill does not create issues on GitHub directly and does not call any API; its output is text only. Actually applying the plan requires a GitHub account, permissions on the repository and the project board, and GitHub Actions enabled if you want to use the automation examples. These examples are incomplete, as the status update steps contain comments instead of code, so they need to be completed and reviewed. The estimates and performance indicators provided are guidance and not guaranteed. The skill is licensed under the MIT License.