spec-engineer

Name: spec-engineer
Availability: InStock
Author: EMSERO

Convert interactive requirements into a structured markdown specification document.

Updated Aug 27, 2026

Search Tags:#documentation #specification #requirements #agile #traceability #elicitation #stakeholders

Ready to run

npx skills add https://github.com/EMSERO/roger --skill spec-engineer

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive requirement gathering and specification generation that reduces ambiguity and accelerates planning by producing a structured, reviewable document for stakeholders.

Core Features & Use Cases

Clarifying questions to understand scope, stakeholders, and constraints
Iterative elicitation to define functional and non-functional requirements
Assigns requirement IDs (REQ-NNN) for traceability
Produces a markdown specification with sections: Overview, Goals/Non-Goals, Stakeholders, Requirements, Constraints, Open Questions
Use cases: when a feature needs a formal spec, this skill guides the user through requirement collection and finalizes the document

Quick Start

Ask the spec-engineer to generate a structured requirements specification by gathering scope, stakeholders, and constraints.

Frequently Asked Questions about spec-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write a specification document with traceable requirement IDs?▼

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.

What is the best way to gather project requirements from stakeholders?▼

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.

How do I define goals and non-goals for a feature request?▼

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.

Can I use this to create a Quick Start guide for system features?▼

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.

Does this approach work for agile requirement elicitation and traceability?▼

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.