Decompose GitHub issues into scoped Markdown implementation plans.
npx skills add https://github.com/drdanmaggs/rocket-fuel --skill issue-scope
Please help me install this Agent Skill. Skill: issue-scope Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/issue-scope Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill issue-scope
Brainstorm features into scoped implementation plans with test decomposition. This skill helps teams convert GitHub issues or user narratives into structured, edge-aware plan documents that align engineering work with test-driven development.
Provide a GitHub issue URL or user description to generate a scoped plan document at docs/plans/YYYY-MM-DD-<feature>.md for /tdd consumption.
High-intent search queries and answers about installing and using this skill.
To convert a GitHub issue into a testable implementation plan, provide the issue URL or content to trigger Socratic questioning and decomposition, generating a scoped Markdown plan file at docs/plans/YYYY-MM-DD-feature.md ready for TDD.
Issue decomposition for test-driven development breaks down feature narratives into scoped, edge-aware plan documents. It uses an Explore, Question, Approach, Decompose, and Plan workflow to align engineering work with test generation.
Yes, you can use a user description instead of a GitHub issue URL for feature planning. The workflow accepts issue URLs, issue content, or raw user narratives to brainstorm and produce the implementation plan.
Yes, issue scoping output integrates directly with TDD workflows. The generated Markdown plan file is structured specifically for /tdd consumption, enabling a rapid start to test-driven development.
The best way to brainstorm features into scoped plan documents is applying Socratic questioning to refine requirements, which explores approaches and decomposes them into edge-aware Markdown files for engineering teams.
You need a directory structure supporting docs/plans/ to store the generated Markdown plan files. The workflow outputs a date-stamped feature plan file directly into this path for subsequent test-driven development integration.
tillysosoResolve GitHub issues end-to-end through an eight-phase workflow to pull requests.
ninjasitmGenerate Markdown implementation plans from project specifications.
tonehqGenerate a formal feature PRD with requirements, edge cases, and API design into a Markdown file.
voidrotGenerate project breakdown plans with Epic, Feature, Story/Enabler, and Test hierarchies.
