technical-design-writer

To generate module-level technical design documents, you consume a completed technical design plan and map all decisions and frontend interaction requirements into formal api-design.md and page-design.md files.

Documenting frontend interaction requirements involves explicitly mapping them from the technical design plan and preserving fidelity-critical layout information from source documents into the final page-design.md output.

Ensuring traceability requires prioritizing plan consumption over freeform interpretation, mapping requirements directly from planning documents to final design specifications, and performing coverage and gap reviews before output.

Yes, you need a completed technical design plan before generating module-level documentation, because the Skill consumes existing planning artifacts rather than re-deriving the software engineering design from scratch.

Automated technical design generation handles incomplete plans by performing coverage and gap reviews before final output, explicitly identifying missing decisions or unmapped interaction requirements from the source document.

You should use an automated design writer instead of manually writing module-level technical design docs when you have finalized design plans and need to ensure consistency, completeness, and strict traceability of frontend interactions.