Structure GitHub issues into Epic, Story, and Task units with acceptance criteria.
npx skills add https://github.com/ebijun1007/vibe-coding --skill issue-design
Please help me install this Agent Skill. Skill: issue-design Source: https://github.com/ebijun1007/vibe-coding/tree/main/.codex/skills/issue-design Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill issue-design
This skill helps you design and structure GitHub issues with appropriate granularity (Epic / Story / Task) and clearly defined sections like Acceptance Criteria, Out of Scope, and Open Questions so that 1 issue maps to 1 PR.
Provide a project context and desired outcome, and the skill will outline Epic/Story/Task, acceptance criteria, out of scope, and open questions.
High-intent search queries and answers about installing and using this skill.
To enforce one issue equals one PR mapping, structure GitHub issues by defining Epic, Story, and Task boundaries alongside Acceptance Criteria, Out of Scope, and Open Questions sections to ensure clear, implementation-ready handoffs.
Breaking down an Epic requires defining granular Story and Task boundaries within your GitHub issues. By delineating these layers and explicitly listing Out of Scope items, you create implementation-ready units that maintain a strict one-to-one issue to pull request ratio.
Defining Out of Scope and Open Questions in GitHub issue design clarifies project boundaries and surfaces unknowns early. This practice reduces ambiguity by explicitly excluding unrelated work and highlighting decisions needed before implementation begins.
Yes, this issue design approach applies to planning and scoping product work of various sizes on GitHub. It determines the appropriate issue granularity, from large Epics to specific Tasks, ensuring consistent one-to-one mapping between issues and pull requests regardless of scale.
Enforcing the principle that one GitHub issue corresponds to one pull request streamlines code review and delivery. It ensures each issue remains a clear, actionable work unit with defined acceptance criteria, preventing oversized pull requests and simplifying project tracking.
flpbaladaStructure product work into Theme, Epic, and Story hierarchies.
SolaneHubManage GitHub issues, branches, and pull requests with automated workflows.
GDSDNClose product development stories by updating status, changelog, and epic indexes.
wtthorntonCreates user stories, epics, and tasks with Fibonacci point estimates.
