Guide feature requests through clarifying questions and structured PRD drafting.
npx skills add https://github.com/sebnow/configs --skill product-definition
Please help me install this Agent Skill. Skill: product-definition Source: https://github.com/sebnow/configs/tree/main/home-manager/agentic/skills/product-definition Command: npx skills add https://github.com/sebnow/configs --skill product-definition
Product teams often struggle to translate vague feature ideas into precise requirements. This Skill enforces a clarification-first workflow and a standard PRD structure to ensure the problem, scope, and success criteria are documented before any implementation.
Describe the feature request and I will guide you through 3–5 clarifying questions before drafting the PRD.
High-intent search queries and answers about installing and using this skill.
To write a PRD from a vague feature request, describe your idea to trigger a clarification-first workflow that asks 3-5 critical questions about problem definition, scope, and success metrics before drafting the document.
A Product Requirements Document should include Introduction, Objectives, User Stories, Functional Requirements, Out of Scope, Design Considerations, Success Criteria, and Open Questions sections to ensure comprehensive scope definition.
Defining clear user stories and functional requirements requires answering clarifying questions on core functionality and scope, which then structures these elements systematically within the drafted PRD.
You cannot start implementation before PRD approval because the workflow enforces a formal approval gate that requires your explicit sign-off on the documented requirements and success criteria.
The best way to align product teams on feature scope is enforcing a clarification-first workflow that defines out-of-scope boundaries and success metrics, ensuring all members agree before drafting the final PRD.
Product teams struggle to translate feature ideas into precise requirements due to missing clarification steps, which this workflow solves by asking targeted questions across problem definition and scope before drafting structured documentation.
chrono-metaClarify vague project requests through guided Socratic questioning into structured spec documents.
kazdencGenerate a Product Requirements Document with problem statements, goals, and success metrics.
alex-tgkGenerate INVEST-compliant user stories with acceptance criteria from epics.
imonmiConvert PRD, Architecture, and UX artifacts into epics and stories.
