update-design

Update DESIGN.md with decisions extracted from conversation content.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/ribon-org/ribon --skill update-design-ribon-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-design
Source: https://github.com/ribon-org/ribon/tree/main/.claude/skills/update-design
Command: npx skills add https://github.com/ribon-org/ribon --skill update-design-ribon-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of recording and updating design and implementation decisions within a project's DESIGN.md file, ensuring that crucial information is consistently captured and easily accessible.

Core Features & Use Cases

  • Centralized Decision Tracking: Consolidates design choices, rationale, and implementation details into a single, organized document.
  • Automated Updates: Streamlines the process of adding new decisions or updating existing ones based on conversation content.
  • Use Case: After a team meeting discussing the architecture of a new feature, use this Skill to automatically update the DESIGN.md with the agreed-upon structure, chosen libraries, and key decisions made.

Quick Start

Use the update-design skill to record the decision to use React for the frontend components.

Frequently Asked Questions about update-design

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

FAQPage Schema
How do I update a DESIGN.md file with new architecture decisions?

To update a DESIGN.md file, this Skill maps extracted conversation content to specific sections like Overview, Architecture, and Implementation Plan. It records key decisions with context, rationale, and date while maintaining a changelog of updates.

What is the best way to track design decisions in project documentation?

Tracking design decisions in project documentation involves consolidating choices, rationale, and implementation details into a centralized file. This Skill automates recording decisions extracted from conversations directly into your project's DESIGN.md file.

Can I use markdown for technical writing and decision tracking in software development?

Yes, markdown is used for technical writing and decision tracking in software development. This Skill processes markdown files to structure decisions into defined sections, maintaining a changelog for project documentation and knowledge management.

How does automated decision tracking work for implementation plans?

Automated decision tracking for implementation plans works by extracting decisions from conversation content and mapping them to specific sections. It captures the context, rationale, and date of each decision, appending it to the DESIGN.md changelog.

Do I need any dependencies to record design decisions from team meetings?

No dependencies are required to record design decisions from team meetings. This Skill operates independently to parse conversation content and update your project documentation with the agreed-upon structure, chosen libraries, and key decisions.

What sections are supported when updating design decisions in markdown?

Supported sections when updating design decisions include Overview, Architecture, and Implementation Plan. The Skill maps extracted topics to these specific markdown sections, ensuring crucial information is consistently captured and organized.