spec-author

To turn a vague ticket into a structured specification, use an automated spec drafting tool that clarifies user intent, allocates IDs, and outputs a single markdown file with ordered body sections and YAML frontmatter.

A delta spec captures review-driven follow-up changes to an existing specification without rewriting the original document. Use it during issue triage when updating a previously approved spec with new modifications or scope adjustments.

Yes, you can draft a specification using a zero-question or minimal-question interview mode. The workflow adjusts its questioning level based on your mode preference, though open-question gating ensures unresolved items are explicitly tracked in the output file.

Creating a markdown spec file with YAML frontmatter involves drafting a structured document that includes requirements, scenarios, out-of-scope items, and open questions. The file must pass best-effort format validation to ensure it is review-ready.

Yes, spec drafting is designed specifically for non-trivial tickets to qualify requirements before architecture, development, or testing begins. It ensures teams align on scope, constraints, and success criteria prior to downstream implementation.

Automated spec qualification workflows rely on best-effort format validation and may not capture every nuanced architectural constraint. They function best as a drafting assistant to produce review-ready specifications rather than replacing human architectural review.