spec-builder

Typed module spec files are generated by running a structured interview that elicits product requirements, fills gaps, and outputs markdown files with resolved YAML frontmatter and typed sections for inputs, outputs, and business rules.

Requirements elicitation is best handled through a seed, draft-with-gaps, and targeted interrogation workflow that tracks open questions and explicitly flags vague or unresolved areas before writing the final specification files.

Service specifications are structured using YAML frontmatter with fields like id, type, depends-on, and exposes, ensuring dependencies, inputs, outputs, and errors are explicit and parseable for downstream tooling.

Yes, spec shape files can be written directly into a user-specified output location such as a Carta workspace directory by instructing the tool to save the generated markdown files there during the interview process.

Yes, spec generation prevents invented business rules by only writing resolved fields based on user input, using TBD placeholders only when necessary, and explicitly tracking open questions during the elicitation process.

You should avoid LLM interviewing for documentation workflows when your project requires zero TBD placeholders, when you lack a defined module or service boundary, or when business rules cannot be explicitly stated.