Decompose project specifications into vertical slices with dependency mapping.
npx skills add https://github.com/wachawo/claude-skills --skill to-issues-wachawo
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/wachawo/claude-skills/tree/main/skills/to-issues Command: npx skills add https://github.com/wachawo/claude-skills --skill to-issues-wachawo
This Skill solves the friction of translating high-level project plans or PRDs into granular, manageable tasks, ensuring that work is broken down into logical, verifiable units.
Ask the to-issues skill to break the current project plan into a series of vertical slices and publish them to the issue tracker.
High-intent search queries and answers about installing and using this skill.
To break down a project plan into actionable issue tickets, you decompose high-level project specifications into granular, independently implementable vertical slices. This automatically structures tasks with dependency mapping, acceptance criteria, and triage labels for your issue tracker.
Vertical slicing in agile software development is breaking complex requirements into tracer-bullet tasks that span all integration layers. This ensures work is decomposed into logical, verifiable units that can be implemented and tracked independently.
Managing task dependencies when creating issues from a PRD requires identifying and structuring tasks based on blockers. This ensures a logical implementation sequence, mapping dependencies so development can proceed without encountering unresolved blockers.
Yes, you can automatically generate standardized issue tickets from a feature specification. The process creates consistent, high-quality tickets complete with acceptance criteria and triage labels, ready to be published directly to your issue tracker.
The best way to structure tracker tickets for independent implementation is decomposing specifications into vertical slices that span integration layers. This approach guarantees each ticket represents a logical, verifiable unit of work.
Yes, you need issue tracker integration to map project dependencies effectively. Access to project context and the issue tracker is required to generate structured, actionable tickets and publish the decomposed vertical slices directly.
bossjonesConvert plans, specifications, or PRDs into actionable project issues.
babuallyBreak plans, specs, and PRDs into actionable issue tracker tickets.
willdadyDecomposes specs and plans into structured vertical-slice tickets with dependency mapping for GitHub or Linear.
jfrometaDecompose complex software work into small, verifiable tasks with dependencies.
