design-tracker

Track project design decisions and update centralized design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill proactively captures and organizes critical project design decisions, ensuring that architectural choices, implementation plans, and technical rationale are consistently documented without manual prompting.

Core Features & Use Cases

  • Automatic Decision Logging: Records architecture, implementation, and library choices as they occur in conversations.
  • Centralized Design Document: Maintains a single source of truth in .claude/docs/DESIGN.md.
  • Use Case: During a development meeting, when the team decides to use the "ReAct pattern" for a new feature, this skill automatically adds this decision to the "Implementation Plan > Patterns" section of the design document.

Quick Start

Use the design-tracker skill to record the decision to use the ReAct pattern.

Frequently Asked Questions about design-tracker

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

FAQPage Schema
How do I automatically document architecture decisions made during project discussions?

To automatically document architecture decisions, this Skill parses conversational context for technical decision points and updates a centralized design document. It records implementation plans and library selections proactively without requiring manual prompting.

What is the best way to maintain a centralized technical design document for project management?

Maintaining a centralized technical design document is achieved by automatically capturing architectural choices and implementation rationale into a single source of truth. The Skill continuously updates specific sections like Overview, Architecture, and Open Questions as decisions occur.

How do I track technical decisions and library selections without manual logging?

Tracking technical decisions without manual logging is handled by proactively scanning discussions for decision points. When library selections or patterns are mentioned, the Skill automatically appends them to the designated sections of the design document.

Can I capture implementation plans and open questions from development meetings automatically?

Capturing implementation plans and open questions from development meetings is fully supported. The Skill processes the conversational context in real-time, identifying technical decisions and organizing them into structured sections like Implementation Plan and TODO.

Does this design documentation tool require any specific dependencies or environment setup?

No specific dependencies or environment setup are required to use this design documentation tool. It operates independently to parse conversational context and maintain the centralized design document within the project structure.

What sections are automatically updated when logging technical documentation for a software project?

When logging technical documentation, the Skill automatically updates specific sections including Overview, Architecture, Implementation Plan, TODO, and Open Questions. This ensures all project design rationale is consistently organized in one file.