spec-solicitation

Automated requirements solicitation generates a complete SPEC.md by guiding you through structured questions that capture context, functional needs, user stories, and edge cases. All Q&A history is preserved for traceability and saved directly to your configured workspace.

Structured requirement discovery is a repeatable elicitation process ensuring alignment across product, design, and engineering. It captures non-functional requirements, acceptance criteria, and dependencies, replacing inconsistent ad-hoc gathering with full traceability.

Yes, external-spec workflows are supported alongside interactive sessions. The skill handles zero-session context and preserves full Q&A history, allowing you to document and refine requirements from existing materials directly into SPEC.md.

You can resume requirements gathering by recovering your progress from the solicitation-workflow.yaml file. This non-blocking conversation mechanism restores your context and saves the completed output to SPEC.md.

The best way to ensure traceability is using a guided solicitation process that preserves all Q&A interactions. This captures dependencies and edge cases systematically, documenting the full reasoning history within the final SPEC.md output.

Yes, the skill explicitly handles zero-session context to initiate requirements discovery for new projects. It uses context-aware solicitation to prompt for necessary details, ensuring a complete specification document is generated from a blank state.