Document stakeholder requirements and convert them into Gherkin specifications.
npx skills add https://github.com/nullhack/pytest-beehave --skill scope-nullhack
Please help me install this Agent Skill. Skill: scope Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/scope Command: npx skills add https://github.com/nullhack/pytest-beehave --skill scope-nullhack
This skill guides the PO through Step 1 of the feature lifecycle: interviewing the stakeholder, discovering requirements, and writing Gherkin specifications precise enough for a developer to write tests without asking questions.
Run a discovery session with the stakeholder and generate the discovery journal and synthesis templates, then draft initial feature descriptions.
High-intent search queries and answers about installing and using this skill.
To convert stakeholder interview notes into Gherkin specifications, use a structured discovery workflow that synthesizes stakeholder requirements and transforms them into precise Rule and Example blocks with @id tags, producing ready-to-edit .feature files.
Documenting feature requirements during stakeholder discovery works best by maintaining a discovery journal and synthesis templates, capturing raw inputs and active listening results to produce a structured discovery.md file for stakeholder alignment.
Writing Gherkin feature files precise enough for developers requires applying gap-finding techniques during stakeholder interviews to surface hidden constraints, then mapping those exact criteria into structured Rule and Example blocks within the feature descriptions.
Yes, you can use structured interviewing techniques for refining existing feature scope, as the discovery and specification workflow supports both new features and refined features by iterating on governance templates and updating the discovery documentation.
Templates needed to guide stakeholder requirements discovery include a discovery journal for raw interview capture, a synthesis document for structured analysis, and governance templates to maintain and iterate feature scope with stakeholders throughout the lifecycle.
pisithrpsExtract quotes, behaviors, pain points, and workarounds from user interview transcripts.
cuongtl1992Convert Lean PRD or Confluence content into structured Gherkin feature files.
hmctsConverts acceptance criteria into Cucumber/Gherkin feature files with backgrounds and tags.
vadimcomanescuGenerate INVEST-compliant user stories and plan sprints with capacity.
