Convert interactive requirements into a structured markdown specification document.
npx skills add https://github.com/EMSERO/roger --skill spec-engineer
Please help me install this Agent Skill. Skill: spec-engineer Source: https://github.com/EMSERO/roger/tree/main/internal/skills/builtin/spec-engineer Command: npx skills add https://github.com/EMSERO/roger --skill spec-engineer
Interactive requirement gathering and specification generation that reduces ambiguity and accelerates planning by producing a structured, reviewable document for stakeholders.
Ask the spec-engineer to generate a structured requirements specification by gathering scope, stakeholders, and constraints.
High-intent search queries and answers about installing and using this skill.
To write a specification, this skill guides you through interactive requirement elicitation and assigns traceable IDs like REQ-001 to each item. It outputs a markdown document with sections for goals, stakeholders, constraints, and open questions to reduce ambiguity.
Gathering requirements is done through iterative, guided dialogue that clarifies scope and constraints across stakeholders. The process captures functional and non-functional needs, finalizing them into a structured specification document for stakeholder review.
To define goals and non-goals, the skill uses clarifying questions during requirement elicitation. This interactive process ensures project scope is explicitly bounded and documented within the final specification output.
Yes, you can create a Quick Start guide for system features. The generated specification document includes a dedicated Quick Start section alongside structured requirements, overview, stakeholders, constraints, and open questions.
Yes, this approach works for agile requirement elicitation by iteratively capturing stakeholder needs and constraints. It ensures traceability by assigning unique requirement IDs like REQ-001 to all functional and non-functional items.
Sheldon-92Automate structured requirement elicitation with 3-5 rounds of questioning and evidence recording.
MichelMokbelImplement a structured development lifecycle with Specification, Pseudocode, Architecture, Refinement, and Completion phases.
Zoomma1Switch to a Kanban work context by searching features, notes, or tickets.
stevolandGuide structured refinement dialogues to produce documented software specifications.
