OpenParable
Skip to content
← Back to skills

Design Tracker

Productivity
design-tracker

Design Tracker is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

PROACTIVELY track and document project design decisions without being asked. Activate automatically when detecting architecture discussions, implementation decisions, pattern choices, library selections, or any technical decisions. Also use when user explicitly says "記録して", "設計どうなってる", "record this". Do NOT wait for user to ask - record important decisions immediately.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/design-tracker/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/design-tracker, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Design Tracker Skill

Purpose

This skill manages the project's design documentation (.claude/docs/DESIGN.md). It automatically tracks:

  • Architecture decisions
  • Implementation plans
  • Library choices and their rationale
  • TODO items and open questions

When to Activate

  • User discusses architecture or design patterns
  • User makes implementation decisions (e.g., "let's use ReAct pattern")
  • User says "record this", "add to design", "document this"
  • User asks "what's our current design?" or "what have we decided?"
  • Important technical decisions are made during conversation

Workflow

Recording Decisions

  1. Read existing .claude/docs/DESIGN.md
  2. Extract the decision/information from conversation
  3. Update the appropriate section
  4. Add entry to Changelog with today's date

Sections to Update

Conversation TopicTarget Section
Overall goals, purposeOverview
System structure, componentsArchitecture
Patterns (ReAct, etc.)Implementation Plan > Patterns
Library choicesImplementation Plan > Libraries
Why we chose X over YImplementation Plan > Key Decisions
Things to implement laterTODO
Unresolved questionsOpen Questions

Output Format

When recording, confirm in Korean:

  • What was recorded
  • Which section was updated
  • Brief summary of the change

Language Rules

  • Thinking/Reasoning: English
  • Code examples: English
  • Document content: English (technical terms) + Korean (descriptions OK)
  • User communication: Korean