update-design

Extract conversation decisions and update DESIGN.md Markdown sections with a dated changelog entry.

190|33|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/DeL-TaiseiOzaki/claude-code-orchestra --skill update-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-design
Source: https://github.com/DeL-TaiseiOzaki/claude-code-orchestra/tree/main/.claude/skills/update-design
Command: npx skills add https://github.com/DeL-TaiseiOzaki/claude-code-orchestra --skill update-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures DESIGN.md stays in sync with decisions from ongoing conversations, reducing drift and manual tracking.

Core Features & Use Cases

  • Extract decisions from chat and apply them to the DESIGN.md file sections (Overview, Architecture, Implementation Plan, and Changelog).
  • Force updates to reflect new goals, structure, patterns, or library choices as decisions are made.
  • Maintain an up-to-date changelog entry with the update date.

Quick Start

Example: Update DESIGN.md with the latest decisions from the current discussion and append a dated changelog entry

Frequently Asked Questions about update-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep my DESIGN.md file in sync with decisions made during a chat?

You can update DESIGN.md directly from your conversation by extracting architectural decisions and applying them to the file's Overview, Architecture, and Implementation Plan sections, ensuring your design documentation stays synchronized with ongoing discussions.

What is the best way to track design decisions and automatically log them in documentation?

Tracking design decisions automatically involves extracting choices made in conversation and appending them as a dated entry to the Changelog section of your DESIGN.md file, reducing manual tracking effort and preventing documentation drift.

Can I force a design document update to reflect new patterns or library choices?

Yes, you can force a design revision to immediately reflect new goals, structural patterns, or library choices by invoking an update that overwrites the relevant sections of your DESIGN.md file with the latest decisions.

How do I maintain an architecture changelog without manually copying conversation outcomes?

Maintaining an architecture changelog without manual copying is possible by automatically extracting decisions from your current discussion and appending a dated update entry directly to the DESIGN.md Changelog section.

Does this approach work for updating existing Markdown documentation or only creating new files?

This approach works for updating existing Markdown documentation by reading your current DESIGN.md file, modifying specific sections like goals and architecture, and writing the updated content back without creating new files.