Document product requirements and define feature scope from discovery interviews.
npx skills add https://github.com/martinffx/atelier --skill spec-product
Please help me install this Agent Skill. Skill: spec:product Source: https://github.com/martinffx/atelier/tree/main/skills/spec%3Aproduct Command: npx skills add https://github.com/martinffx/atelier --skill spec-product
Product teams often struggle to convert vague ideas into concrete requirements and clear scope. This Skill provides a structured approach to discovery interviews, scope definition, and backlog-ready outputs.
Start a discovery session with stakeholders to capture requirements and define the initial feature scope.
High-intent search queries and answers about installing and using this skill.
To define clear scope and user stories from vague ideas, conduct structured discovery interviews with stakeholders to extract concrete user needs, constraints, and success criteria. This process establishes explicit in-scope versus out-of-scope boundaries and MVP criteria for backlog formation.
The best way to run product discovery interviews is using a structured approach to capture business rules, constraints, and non-functional considerations. This ensures you document specific user needs and integration points required for a successful handoff to architects.
Defining MVP criteria and scope boundaries requires documenting product requirements through discovery sessions. You establish explicit in-scope versus out-of-scope parameters, capture data requirements, and record non-functional considerations to guide downstream development.
Yes, this approach captures non-functional requirements and integration points specifically for architect handoff. The structured discovery process satisfies business rules, constraints, and integration points, ensuring deliverables contain the technical depth architects need.
Yes, you can use this for backlog formation and prioritization inputs across diverse domains. The discovery outputs deliver backlog-ready user stories and prioritization inputs suitable for product managers working in varied product contexts.
Deliverables from a product scope definition session include clear in-scope versus out-of-scope boundaries, MVP criteria, data requirements, and user stories. These outputs provide prioritization inputs for product managers and integration details for architects.
EnigmaWUTranslate raw product requirements into architectural drivers for system design.
deepeshBodhConvert feature descriptions into prioritized user stories with Given/When/Then acceptance scenarios.
ai-enhanced-engineerDefine MVP scope and phased delivery with MoSCoW prioritization.
spideynoloveFetches web page HTML via a lightweight headless browser CLI.
