Technical Spec

This enforces actual discipline in technical writing by requiring alternatives, diagrams, and measurable success criteria for every design doc. It won't let you skip the hard parts like risk assessment or let you write "we'll use PostgreSQL" without explaining why you rejected MongoDB. Covers the full spectrum from quick ADRs to full RFCs with C4 diagrams, all with opinionated templates that push you toward living documents instead of write-once artifacts. The hard rules about including at least two alternatives and defining concrete metrics (not "make it faster" but "reduce P95 from 500ms to 200ms") are the real value here. Best for teams that keep making design decisions in Slack threads and wondering six months later why they chose what they chose.

skills.sh installs: 141
GitHub stars: 153
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add majiayu000/claude-arsenal --skill technical-spec --agent claude-code

Installs into .claude/skills of the current project.

Files

Technical Specification & Design Documents

Expert guidance for writing effective technical design documents, RFCs, Architecture Decision Records, and technology evaluation frameworks.

Core Philosophy

Write before code — Design documents prevent costly rework and align teams
Living documents — Keep docs updated as the system evolves
Clarity over completeness — Simple, direct language reduces cognitive load
Diagrams as code — Version-controlled, maintainable architecture diagrams
Decisions over descriptions — Document why, not just what

Hard Rules (Must Follow)

These rules are mandatory. Violating them means the skill is not working correctly.

Alternatives Required

Every design document must include at least 2 alternative solutions.

❌ FORBIDDEN:
## Solution
We will use PostgreSQL for the database.
(No alternatives considered)

✅ REQUIRED:
## Proposed Solution
PostgreSQL for primary database.

## Alternatives Considered

### Option A: PostgreSQL (Recommended)
**Pros**: ACID compliance, JSON support, mature ecosystem
**Cons**: Vertical scaling limits
**Decision**: Chosen for reliability and team expertise

SKILL.md on GitHub

Details

Repository: github.com/majiayu000/claude-arsenal
First seen: Jun 3, 2026

More from majiayu000/claude-arsenal

All 8