Scope GitHub feature issues from product ideas with discovery questions and mockups.
npx skills add https://github.com/mujtaba3B/gstack-extensions --skill feature-mujtaba3b
Please help me install this Agent Skill. Skill: feature Source: https://github.com/mujtaba3B/gstack-extensions/tree/main/pm/skills/feature Command: npx skills add https://github.com/mujtaba3B/gstack-extensions --skill feature-mujtaba3b
This Skill helps turn a product idea into a well-scoped GitHub feature issue, so teams can clarify value, scope, edge cases, and ownership before implementation begins.
Use the feature skill to scope this product idea, ask the discovery questions, review the full issue preview, and file the GitHub issue when I approve it.
High-intent search queries and answers about installing and using this skill.
Scoping product ideas into GitHub feature issues requires structured discovery questions to identify beneficiaries, first version size, affected surfaces, and success metrics before generating the final ticket. This process clarifies value, scope, edge cases, and ownership prior to implementation.
A well-scoped GitHub feature issue must include a summary, acceptance criteria, QA instructions, context, and notes. It also requires collaborator assignment, project-board routing, and visual mockups to ensure designers, engineers, and QA can align without guessing.
Yes, mockups are required for UI-backed product changes before filing a GitHub feature issue. Embedding reviewable Pencil visuals ensures designers, engineers, and QA align on the UI changes without guessing, making the issue documentation complete and issue-ready.
Yes, you can use a fast-mode filing path to quickly create GitHub feature issues for new functionality and enhancements. This operational routing handles assignee selection and project board placement for teams wanting a quicker, guided issue-creation flow.
The best way to add QA instructions is through discovery-led scoping that asks structured questions about the feature. This produces an issue-ready ticket where QA instructions, acceptance criteria, and context are formatted exactly as needed for filing.
Discovery questions are required to identify who benefits, how big the first version should be, what surfaces are affected, and how success is measured. This clarifies value, scope, edge cases, and ownership before implementation begins, ensuring reliable ticket creation.
eKoh951Draft and manage a reusable product marketing context document in .claude/product-marketing-context.md.
kayacConvert meeting notes into GitHub Project Epic/Feature/Story/Task hierarchies.
opsMachinePost a QA testing checklist to a GitHub issue with acceptance criteria.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
