design-tracker

Record project design decisions and update DESIGN.md documentation.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/nakaj1214/trader --skill design-tracker-nakaj1214
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-tracker
Source: https://github.com/nakaj1214/trader/tree/main/.claude/skills/design-tracker
Command: npx skills add https://github.com/nakaj1214/trader --skill design-tracker-nakaj1214

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill proactively captures and documents critical project design decisions, architectural choices, and implementation plans, ensuring that important technical details are not lost and are easily accessible.

Core Features & Use Cases

  • Automatic Decision Logging: Records architecture, implementation, and library choices as they are made during conversations.
  • Centralized Documentation: Maintains a single source of truth for design decisions in .claude/docs/DESIGN.md.
  • Proactive Tracking: Activates automatically upon detecting discussions related to technical decisions or when explicitly prompted to record information.
  • Use Case: When discussing the choice between two different database solutions, this skill will automatically record the chosen solution, the rationale, and any alternative considerations in the project's design document.

Quick Start

Use the design tracker skill to record the decision to use the ReAct pattern for agentic workflows.

Frequently Asked Questions about design-tracker

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

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

To document technical decisions automatically, this skill proactively tracks architecture choices and implementation plans as they occur in conversation, saving them directly into a centralized design document.

What is the best way to maintain a centralized log of architecture choices and library selections?

The best way to maintain a centralized log of architecture choices and library selections is using a proactive tracker that updates a single source of truth file, capturing the rationale and alternatives considered.

Can I automatically record the rationale for choosing a specific framework or pattern?

Yes, you can automatically record the rationale for choosing a framework or pattern; the skill activates upon detecting technical decision discussions to log the chosen solution and its alternatives.

How do I start logging design decisions into my project's documentation?

To start logging design decisions, simply discuss technical choices in conversation or issue an explicit recording command; the skill will capture the details and update the project's design document automatically.

Does this design tracker require manual activation to save implementation plans?

No, this design tracker does not require manual activation to save implementation plans; it supports automatic activation upon detecting decision-related discussions alongside explicit recording commands.