update-design

To update a design document with new architecture decisions, the Skill reads the existing DESIGN.md, extracts decisions from the discussion, and maps them into appropriate sections like Overview, Architecture, or Implementation Plan to keep the living design document current.

Maintaining a changelog for design decisions involves appending a dated entry summarizing recorded choices and unresolved questions into the design document, ensuring architecture rationale stays auditable and synchronized with project development.

Mapping conversation topics to design document sections works by reading the discussion context, extracting settled decisions, and placing those entries into targeted sections such as Implementation Plan, TODO, or Open Questions for organized discoverability.

Yes, you can document design decisions without invoking external models. This Skill operates without external model invocation when disable-model-invocation is required, directly reading and merging content into the local .claude/docs/DESIGN.md file.

You need to record unresolved questions in a project design document during design conversations or orchestrator workflows when architecture choices or open questions arise, ensuring they are mapped to the Open Questions section for future resolution.

Yes, the tool supports English technical content within the design document structure while providing Korean descriptions for user-facing notes, allowing bilingual project teams to maintain architecture records effectively.