quick-design

To document small project changes without a full design spec, use a lightweight quick-design workflow that generates a concise design spec file, skipping comprehensive documentation when only minor tweaks or additions are needed.

You should generate a quick design spec instead of a full CDD when applying minor tweaks, tuning, or additions that do not warrant comprehensive authoring, especially when a system CDD already exists or the change is minor.

To create a design spec file for minor governance workflow tweaks, submit a brief change description into the quick-design workflow, which then automatically outputs a kebab-case spec file under the design/quick-specs directory.

Generating a quick design spec for small changes requires a brief description of the change as input, and it can reference existing project artifacts if needed to produce the design spec file.

Yes, the quick design spec workflow supports rapid development handoffs by generating compact design specifications for minor changes, enabling quick reviews and approvals in fast-paced development cycles.

You should not use quick-design for major system changes, as it is specifically built to skip full CDD authoring for minor tweaks and additions, meaning it lacks the depth required for comprehensive system modifications.