update-design

To update design documentation from issue content, this Skill applies a specification-driven workflow that maps issue details to relevant design sections while preserving the original section structure. It parses issue data and translates labels to target specific document sections.

Yes, markdown integrity is preserved during sync by validating formatting consistency, header levels, and code block structures. This ensures that automated updates from issue tracker data do not break the existing markdown validation rules of your design docs.

A specification-driven workflow for design docs uses project issues as structured specifications to drive documentation updates. It maps issue labels to specific design sections and applies changes interactively, ensuring documentation accurately reflects issue-driven requirements.

Yes, the update process explicitly excludes ADR (Architecture Decision Record) files from automated updates. This prevents specification-driven issue content from accidentally overwriting isolated architectural decisions stored within the documentation repository.

You can start interactively editing design files by running the update command, which prompts you through the update process. It guides you by suggesting next actions and mapping issue content directly to applicable design document sections.