design-tracker

Name: design-tracker
Availability: InStock
Author: yoshihiko

Record design decisions into DESIGN.md with dated changelog entries.

Updated Feb 1, 2026

Search Tags:#documentation #traceability #architecture-decisions #project-docs #change-log #design-tracker #design-log

Ready to run

npx skills add https://github.com/yoshihiko555/ai-orchestra --skill design-tracker-yoshihiko555

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-tracker
Source: https://github.com/yoshihiko555/ai-orchestra/tree/main/skills/design-tracker
Command: npx skills add https://github.com/yoshihiko555/ai-orchestra --skill design-tracker-yoshihiko555

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams automatically capture and organize design decisions, ensuring architecture rationale is preserved without manual note-taking.

Core Features & Use Cases

Automatic decision capture: records architecture choices, implementation plans, and library selections as they occur.
Centralized design documentation: feeds Design docs (docs/DESIGN.md) with structured entries and a changelog entry.
Use Case: during architecture discussions, the Skill records decisions and updates the design log and changelog for future reference.

Quick Start

Use the design-tracker skill to add a new architecture decision to docs/DESIGN.md when discussions occur, and automatically append a dated entry to the changelog. For example, say: "Record this design decision: We adopt a microservices architecture with REST APIs and a shared design language."

Frequently Asked Questions about design-tracker

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

FAQPage Schema

How do I automatically record architecture decisions into project documentation?▼

To automatically record architecture decisions, you can use a tool to capture choices during discussions and append structured, dated entries directly into your project's DESIGN.md file and changelog.

What is design traceability and why do I need it in software engineering?▼

Design traceability is the practice of preserving architecture rationale. It is needed to ensure that library selections, implementation plans, and pattern choices are documented for future reference without manual note-taking.

How do I maintain a design log and changelog during architecture discussions?▼

You maintain a design log by recording decisions as they occur during architecture discussions. The tool automatically reads and updates DESIGN.md, appending a dated changelog entry for each captured decision.

Can I use this to document library and pattern selections in DESIGN.md?▼

Yes, you can document library and pattern selections in DESIGN.md. The tool automatically captures these selections as they happen and updates the design documentation with structured entries for future reference.

Does automatic decision capture work without manual note-taking?▼

Automatic decision capture works by proactively recording architecture choices, implementation plans, and library selections as they occur, ensuring rationale is preserved in DESIGN.md without requiring manual note-taking.

When should I not use automated design documentation?▼

You should avoid automated design documentation if your project lacks a docs/DESIGN.md file or if your workflow does not involve formal architecture discussions, library selections, or implementation planning that requires rationale tracking.