What problem does it solve?
It turns scattered stakeholder notes, specs, and API definitions into a single, continuously updated Elicitation Document that preserves traceability and supports human review at every step.
Core Features & Use Cases
- Input synthesis from whole project context: Reads all files under inputs/ (including OpenAPI YAML under inputs/APIs/) and extracts stakeholders, problem statement, scope, requirements, constraints, assumptions, risks, and open questions.
- Incremental, ID-preserving updates: Loads the existing artifacts/01-elicitation/elicitation-document.md if present and refines Pending items without changing their IDs; for Accepted/Rejected items, it protects their content and appends a review note when new info may affect them.
- Architecture diagram generation from APIs: Produces/updates component and sequence diagrams from OpenAPI operationId and service relationships, and flags missing API definitions with open questions.
- Quality gates for downstream approval: Enforces RFC 2119 normative language for FRs/NFRs, checks orphaned requirements, ensures owners exist, demands measurable targets for NFRs, and generates acceptance criteria when missing.
- Review-gated output artifacts: Writes artifacts/01-elicitation/elicitation-document.md and updates inputs/manifest.md to log what was incorporated.
Quick Start
Place your requirements inputs into the inputs/ directory (including any OpenAPI YAML under inputs/APIs/), then run the elicit skill to generate or update the Elicitation Document.
