mt-sdd-spec

To turn vague feature requests into structured specifications, you need to collect context and perform requirement discovery. This Skill guides requirement interviews to produce validated, implementation-ready specification documents with supporting records.

The best way to review a software design specification is through a multi-angle review workflow. This process runs completeness, feasibility, consistency, and risk checks with automated correction loops and audit gates to validate the document.

Yes, you need specification templates and review criteria to create software design documents. The workflow requires these inputs alongside session management processes to guide requirement analysis and produce validated implementation-ready specifications.

To prepare a spec.md file for implementation approval, you must analyze the feature request and generate a structured specification. The workflow applies multi-perspective reviews and approval gates to ensure the document is ready for development.

This workflow applies to software development scenarios requiring context collection, specification authoring, multi-perspective review, and approval gates. If your scenario only needs requirement analysis without specification authoring and review, this process may be too heavy.