Spec Creator

Writes and updates a single SPEC.md at the repository root, conforming to a strict section template and wording guide. One file per project. Language-agnostic — the resulting spec describes behavior only, not implementation.

Reference files

Load on demand, not upfront. The three reference files are short (~100 lines each); read each fully when needed.

• references/template.md — the authoritative section structure. Read it when drafting a new spec and when checking whether a section lives in the right place.
• references/language.md — wording rules: voice, tense, obligation keywords, field format, annotation patterns, code-identifier casing, tone. Read it before writing prose and again during the validation pass.
• references/examples/reaper.md — a complete filled-in spec for a deployment-rollback monitor. Read it when the user asks "what does a good one look like" or when a concrete pattern helps.

Do not paraphrase the reference files from memory. Their rules are specific and easy to recall wrong.

Decide: create or update

Before writing anything:

1. Check whether SPEC.md exists at the repo root.