"Write a specification" can mean anything. A Semantic Contract makes it precise:
Specification = Use Cases with Activity Diagrams (all paths) + acceptance criteria in Gherkin format.
This is not prompt engineering. It is a definition that every LLM reads at session start and follows. Like a Semantic Anchor, but for terms that don't exist in training data.
"arc42" activates 12 sections of architecture documentation in every model. "Operations Manual" activates nothing. A Contract gives the term meaning: it composes established anchors into a precise definition or defines completely custom rules.
We published 12 Contracts that cover a complete development workflow:
- Requirements Discovery: Socratic Method + MECE + PRD
- Specification: Gherkin + BDD
- Architecture: arc42 + C4 + ADR (Nygard) with Pugh Matrix
- Backlog: INVEST + MoSCoW
- Implement Next: TDD London School + Conventional Commits + Definition of Done
- Quality Review: Fagan Inspection + OWASP Top 10 + ATAM
- Docs-as-Code: AsciiDoc + PlantUML + docToolchain
Plus three communication Contracts: Concise Response (BLUF), Simple Explanation (Feynman Technique), Writing Style (Wolf Schneider + custom rules).
On the website, select the Contracts you need, download them as semantic-contracts.md, and drop the file into your AGENTS.md or CLAUDE.md. Next session start, the LLM works by your rules.