Breaks down large tickets into dated .md files with WHAT and WHY sections.
npx skills add https://github.com/ryanmoran/workspace --skill ticket-breakdown
Please help me install this Agent Skill. Skill: ticket-breakdown Source: https://github.com/ryanmoran/workspace/tree/main/skills/ticket-breakdown Command: npx skills add https://github.com/ryanmoran/workspace --skill ticket-breakdown
This skill helps product teams and engineers convert vague feature requests into a structured, independent set of implementation issues that can be tackled in parallel, reducing delays and coordination overhead.
To begin, run brainstorming to outline major components, then generate the issues/ folder, write README.md with phases and dependencies, and create ISSUE-*.md files following the WHAT/WHY pattern. Then run rumdl to lint the markdown files.
High-intent search queries and answers about installing and using this skill.
To break down a large feature ticket, you convert the feature spec into a structured set of independent issues. This creates an issues directory with phased organization and a dependency DAG to enable parallel execution.
Structuring ticket dependencies for parallel execution requires building a directed acyclic graph (DAG). This organizes issues into sequential phases while allowing independent tasks within each phase to be executed simultaneously.
Writing acceptance criteria for backlog issues involves generating individual markdown files for each task. These files outline the specific WHAT and WHY of the implementation, ensuring clear scope and expectations for parallel work.
Yes, phase-based organization is ideal for managing complex feature documentation. It breaks the work into a directed acyclic graph of dependencies, grouping issues by implementation order to clarify parallelizable work.
Creating an issues directory from a feature request involves outlining major components and generating markdown files. A README file maps the phases and dependencies, while individual issue files document the WHAT and WHY for each task.
Andrej1601Convert vague concepts into structured, testable feature specifications.
OreStudioGenerate Markdown sprint release notes from the latest ORE Sprint Backlog file.
danielbushManage work items, tickets, and session histories in a work/ directory.
wtthorntonCreates user stories, epics, and tasks with Fibonacci point estimates.
