skills.rest
arugo11
arugo11COMMUNITY
Explore all skills by this author →
GitHub

design-tracker

Records design decisions and updates DESIGN.md automatically.

1|Updated Feb 22, 2026
Search Tags:#design#project management#architecture#documentation#decision logging#technical decisions
One-click install
npx skills add https://github.com/arugo11/sit-copilot --skill design-tracker-arugo11
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-tracker
Source: https://github.com/arugo11/sit-copilot/tree/main/.claude/skills/design-tracker
Command: npx skills add https://github.com/arugo11/sit-copilot --skill design-tracker-arugo11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill proactively captures and documents crucial project design decisions, ensuring that architectural choices, implementation plans, and technical rationales are systematically recorded and easily accessible.

Core Features & Use Cases

  • Automatic Decision Logging: Captures discussions on architecture, patterns, and library choices without explicit user commands.
  • Centralized Documentation: Updates a central DESIGN.md file with new decisions.
  • Use Case: During a team meeting, when a developer states, "We've decided to use the CQRS pattern for the data layer," this skill automatically logs this decision under the 'Patterns' section of the design document.

Quick Start

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

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 project design decisions during development?▼

To document project design decisions automatically, you need a tool that detects technical discussions and logs them. This skill captures architectural choices and implementation plans by proactively updating a central DESIGN.md file without requiring explicit commands.

What is the best way to track architectural decisions and library selections?▼

Tracking architectural decisions and library selections is best handled by centralizing the records in a DESIGN.md file. This skill logs technical rationales and patterns into a changelog, ensuring choices are systematically recorded and accessible.

How does automatic decision logging work for technical architecture discussions?▼

Automatic decision logging works by detecting when users discuss technical decisions, such as selecting a pattern like CQRS. The skill then proactively records the architectural choice and its rationale directly into the project's design documentation.

Do I need to manually update DESIGN.md when logging implementation plans?▼

You do not need to manually update DESIGN.md when logging implementation plans. The skill automatically detects technical decisions and appends the new architectural choices or library selections to the design document and changelog.

Can I use this design tracker for project management documentation in any software engineering context?▼

You can use this design tracker for project management documentation in software engineering contexts where tracking architecture and library selections is needed. It systematically captures technical decisions and logs changes within a central DESIGN.md file.

Related Skills

Explore More Software Engineering Skills→
cdrgurucdrguru
1

gemini-cli-init

Initialize Gemini CLI configuration and auditor persona for the PACK workflow.

Community
Intermediate
rotnovrotnov

create-architectural-decision-record

Create Architectural Decision Records using a repository-specific ADR template.

Community
Basic
nextcnextc
2

update-docs

Synchronize project documentation with codebase changes across CLAUDE.md, tasks.md, specs, design.md, changelog, and glossary.

Official
Advanced
lyndonkllyndonkl
142

adr-architecture

Document architectural decisions using the Architecture Decision Record format.

Community
Advanced