Write Specs

Specification

The words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are interpreted as described in RFC 2119.

Purpose

Use this skill to turn loose project intent into a specification that implementors can build against and reviewers can validate. Prefer explicit contracts over narrative explanation. Make hidden decisions visible.

Core Workflow

1. Ground the spec in available evidence.
   • Read any linked docs, code, issues, PRs, diagrams, user notes, or product context before drafting.
   • Separate confirmed facts from assumptions.
   • Mark unresolved decisions as open questions only when they materially affect implementation.