Break down complex plans into independently actionable issues for project trackers.
npx skills add https://github.com/dallenpyrah/pi --skill to-issues-dallenpyrah
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/dallenpyrah/pi/tree/main/skills/to-issues Command: npx skills add https://github.com/dallenpyrah/pi --skill to-issues-dallenpyrah
The to-issues Skill addresses the challenge of breaking down complex plans, specifications, or PRDs into individual, independently actionable issues for project issue tracking.
Run /to-issues <plan-url> to analyze a plan and generate issues based on tracer-bullet vertical slices.
High-intent search queries and answers about installing and using this skill.
Breaking down a project plan into actionable issues involves splitting complex specifications into traceable vertical slices. This ensures each issue is independently grabbable, manageable, and linked to project requirements for effective tracking.
Tracer-bullet vertical slices in issue tracking are independently grabbable units of work identified by analyzing a plan. They simplify issue creation by ensuring each slice is manageable and traceable back to the original project specifications.
Converting a PRD into issues with dependency linking requires breaking down the specification into traceable vertical slices. This process generates independently grabbable issues intended for use within project issue trackers that support detailed structuring.
Yes, you can automatically generate issues from a plan URL by analyzing the provided link. The process automates issue creation within your project's issue tracker using predefined templates and labels based on the extracted vertical slices.
Issue breakdown from specifications works with existing project requirements by splitting plans into traceable vertical slices. Each generated issue is explicitly linked back to the project requirements to maintain context and tracking accuracy.
You should avoid automated issue breakdown when your project issue tracker lacks support for detailed issue structuring and dependency linking. The generated vertical slices require these features to maintain traceable and effective project tracking.
tanshunyuanBreak down plans, specifications, or PRDs into issues on GitHub and GitLab.
anonymousminatiBreak plans into dependency-ordered tracer-bullet issues with acceptance criteria.
lasswelltAnalyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.
adriannoesDecompose project plans into hierarchical, independent issues for tracking tools.
