design-tracker
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", "what's our design status", or equivalent. Do NOT wait for user to ask - record important decisions immediately.
Best use case
design-tracker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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", "what's our design status", or equivalent. Do NOT wait for user to ask - record important decisions immediately.
Teams using design-tracker should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design-tracker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design-tracker Compares
| Feature / Agent | design-tracker | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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", "what's our design status", or equivalent. Do NOT wait for user to ask - record important decisions immediately.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 Topic | Target Section | |-------------------|----------------| | Overall goals, purpose | Overview | | System structure, components | Architecture | | Patterns (ReAct, etc.) | Implementation Plan > Patterns | | Library choices | Implementation Plan > Libraries | | Why we chose X over Y | Implementation Plan > Key Decisions | | Things to implement later | TODO | | Unresolved questions | Open Questions | ## Output Format When recording, confirm in Japanese: - 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) + Japanese (descriptions OK) - **User communication**: Japanese
Related Skills
update-design
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
context-loader
ALWAYS activate this skill at the start of every task. Load project context from .claude/ directory including coding rules, design decisions, and documentation before executing any task.
update-lib-docs
Update library documentation in .claude/docs/libraries/ with latest information from web search.
troubleshoot
Diagnose and plan fixes for errors/bugs with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for deep code reasoning, hypothesis evaluation, and fix validation. Phase 1: Error reproduction & context gathering (Opus subagent 1M context + Codex initial analysis + Claude user interaction). Phase 2: Parallel diagnosis (Agent Teams: Root Cause Analyst [Codex-driven] + Impact Investigator [Opus + Codex risk analysis]). Phase 3: Fix plan synthesis, Codex validation & user approval. Fix implementation is handled separately by /team-implement.
team-review
Parallel code review using Agent Teams. Spawns specialized reviewers (security, quality, test coverage) to review implementation from different perspectives simultaneously. Run after implementation.
team-implement
Parallel implementation using Agent Teams. Spawns teammates per module/layer, each owning separate files to avoid conflicts. Uses shared task list with dependencies for autonomous coordination. Run after /start-feature plan approval.
tdd
Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.
start-feature
Start a new feature with multi-agent collaboration (Opus 4.6 + Agent Teams). Phase 1: Codebase understanding (Opus subagent 1M context + Claude user interaction). Phase 2: Parallel research & design (Agent Teams: Researcher + Architect). Phase 3: Plan synthesis & user approval. Implementation is handled separately by /team-implement.
spike
Time-boxed technical investigation/feasibility study with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for question framing, feasibility analysis, and final evaluation. Phase 1: Frame the investigation question & constraints (Claude user interaction + Codex question decomposition). Phase 2: Parallel investigation (Agent Teams: Researcher [Opus external research] + Feasibility Analyst [Codex deep analysis] + optional prototype). Phase 3: Codex synthesis into go/no-go recommendation & research report. Produces a DECISION DOCUMENT, NOT an implementation plan. Use /add-feature or /start-feature after a GO decision.
simplify
Simplify and refactor code while preserving functionality and library constraints.
research-lib
Research a library and create comprehensive documentation in .claude/docs/libraries/.
plan
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.