update-design

Update DESIGN.md with conversation decisions and changelog entries.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/arugo11/sit-copilot --skill update-design-arugo11
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: update-design
Source: https://github.com/arugo11/sit-copilot/tree/main/.claude/skills/update-design
Command: npx skills add https://github.com/arugo11/sit-copilot --skill update-design-arugo11

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that project design decisions made during conversations are systematically recorded and updated in the DESIGN.md document, maintaining a clear and current record of the project's architecture and choices.

Core Features & Use Cases

  • Decision Recording: Captures key design decisions, rationale, and context from conversations.
  • Document Maintenance: Updates the central DESIGN.md file and adds entries to the Changelog.
  • Use Case: After a lengthy discussion about choosing a new database technology, use this Skill to formally record the decision, the reasons behind it, and any alternatives considered, ensuring this information is accessible to the entire team.

Quick Start

Use the update-design skill to record the decision to use FastAPI for the backend API.

Frequently Asked Questions about update-design

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

FAQPage Schema
How do I update DESIGN.md with decisions from a conversation?β–Ό

To update DESIGN.md with decisions, this skill extracts design choices from your current conversation and maps them into specific sections like Overview, Architecture, Implementation Plan, TODOs, and Open Questions.

What is the best way to track project design decisions in markdown?β–Ό

Tracking project design decisions in markdown is achieved by recording your conversation's rationale and context directly into a central DESIGN.md file, maintaining a clear and current record of your architecture choices.

How does decision tracking work for architecture changes?β–Ό

Decision tracking for architecture changes works by capturing key design choices and alternatives from your discussion, then appending a dated changelog entry to your design document to maintain a historical record.

Can I use this to record a database technology choice and its rationale?β–Ό

Yes, you can record a database technology choice by extracting the decision, the reasons behind it, and any alternatives considered from your conversation to ensure the information is accessible to the entire team.

What sections of a design document does this skill update?β–Ό

This skill updates the Overview, Architecture, Implementation Plan, TODOs, and Open Questions sections of your design document, mapping relevant conversation topics to the appropriate markdown sections.

Do I need any dependencies to maintain a changelog of design decisions?β–Ό

No dependencies are required to maintain a changelog of design decisions. The skill operates independently to extract decisions from the conversation and append dated entries to your markdown file.