Where are the design documents stored?

Documents are saved as Markdown files in a dedicated 'design-docs/' directory within your project, ensuring they are versioned alongside your source code.

What is the difference between a design doc and an implementation manual?

A design doc explores trade-offs and justifies the chosen path, whereas an implementation manual describes specific tasks without exploring alternatives.

When should I use the Design Documents skill?

Use it when you face architectural ambiguity, need to evaluate multiple valid solutions, or want to preserve the reasoning behind a major system change for future maintainers.

Can I update existing documents without losing history?

Yes, the skill follows a 'never silently edit' policy, adding dated update sections to show how the project's architecture has evolved over time.

Does this skill help with the actual code implementation?

It focuses on the 'what' and 'why' phase. Once a design is approved, it is designed to hand off to the technical-design skill to map the solution onto the codebase.

Technical Design Documents

Name: Technical Design Documents
Author: xobotyi

byxobotyi

•

学習とドキュメンテーション

Drafts and maintains structured technical design documents to analyze problems and evaluate architectural solutions before implementation.

This skill streamlines the architectural planning process by helping developers create comprehensive design documents that bridge the gap between human intent and code execution. It guides users through problem analysis, goal setting, and trade-off evaluation, ensuring that architectural decisions are well-reasoned and preserved as searchable records. By enforcing a standardized template and exploring multiple solution paths, it helps prevent 'single-option' bias and catches expensive architectural mistakes during the cheapest phase of the development lifecycle.

主な機能

01Standardized Markdown templates for architectural decision records (ADRs)

02Versioning support via chronological update sections and standardized file naming

031 GitHub stars

04Guided problem analysis including root cause identification and impact assessment

05Comparative evaluation of multiple technical solutions with detailed pros and cons

06Structured tracking of goals, non-goals, and cross-cutting concerns like security and observability

ユースケース

01Evaluating multiple architectural approaches for a new system feature before writing code

02Documenting complex breaking changes and their migration paths for team review

03Creating a historical record of architectural decisions to prevent knowledge loss

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add xobotyi/cc-foundry design-documents

For use in Claude.ai and ChatGPT

Download Skill