Conduct stakeholder interviews to generate scope journals and .feature descriptions.
npx skills add https://github.com/nullhack/temple8 --skill define-scope
Please help me install this Agent Skill. Skill: define-scope Source: https://github.com/nullhack/temple8/tree/main/.opencode/skills/define-scope Command: npx skills add https://github.com/nullhack/temple8 --skill define-scope
Product teams often struggle to crystallize and agree on feature scope early. This skill guides the product owner through structured stakeholder interviews and synthesis to produce clear scope definitions, leaving behind ambiguous requirements and misaligned expectations.
Start a discovery session with a stakeholder using predefined groups and capture outputs to the scope journal and discovery docs for immediate iteration.
High-intent search queries and answers about installing and using this skill.
Feature scope is defined by running guided stakeholder interviews using predefined question groups, capturing outputs in a scope journal, and synthesizing the results to produce clear scope definitions and initial .feature descriptions.
Stakeholder alignment is achieved by enforcing a structured discovery process with session gates and baselining criteria, ensuring all parties agree on validated requirements before moving to the next development stage.
Stakeholder interviews are conducted using predefined question groups and active listening protocols to surface requirements, which are then captured in a scope journal for immediate iteration and synthesis.
Early lifecycle scope discovery produces scope journals, discovery syntheses, and initial .feature template descriptions, providing structured documentation to transition validated requirements into Stage 2 development.
Yes, structured discovery sessions capture stakeholder inputs and synthesize them into initial .feature descriptions, providing a foundation for Gherkin-based feature documentation in Stage 2.
Ambiguous requirements occur when product teams lack structured stakeholder validation; a guided discovery process prevents this by baselining decisions and enforcing session gates to align expectations early.
LucasMalessaAssess project health across schedule, cost, scope, quality, risk, and stakeholder dimensions.
nullhackDocument stakeholder requirements and convert them into Gherkin specifications.
qa-amanFacilitate structured stakeholder requirement elicitation across interviews, workshops, observation, and document analysis.
nimrodfisherIdentify and structure stakeholder requirements into actionable documents with acceptance criteria.
