specs

name	specs
description	Use when working with software specifications, architecture documentation, and diagramming. Covers the full spectrum of spec-driven development — from architectural diagrams to requirements documents to specification tooling. USE FOR: specification-driven development, architecture documentation strategy, choosing diagram types, choosing requirements formats, spec-to-implementation workflows DO NOT USE FOR: specific diagram syntax (use diagramming sub-skills), specific document templates (use documentation sub-skills), specific tooling (use tools sub-skills)
license	MIT
metadata	{"displayName":"Specifications & Architecture Documentation","author":"Tyler-R-Kendrick"}
compatibility	claude, copilot, cursor
references	[{"title":"arc42 — Architecture Documentation Template","url":"https://arc42.org/"},{"title":"Documenting Software Architectures — SEI","url":"https://www.sei.cmu.edu/our-work/software-architecture/tools/documenting/"}]

Specifications & Architecture Documentation

Overview

Good architecture starts with good specs. This skill covers the full spectrum of specification-driven development — from visual diagrams that communicate system structure, to requirements documents that capture intent, to tools that automate the spec-to-code pipeline.