Spec Authoring

Purpose

Produce detailed, engineering-grade specifications similar in depth and structure to a full platform spec. The output must be explicit, testable, and implementation-ready without needing back-and-forth clarification.

Core Principles

1. State intent clearly and early.
2. Define scope and non-scope to avoid ambiguity.
3. Make every requirement verifiable.
4. Prefer concrete examples over vague descriptions.
5. Use consistent naming and types across the document.
6. Include failure modes and edge cases.
7. Avoid assumptions; write them down.
8. Define canonical data models in a single spec and reference them elsewhere to prevent duplication.

Required Structure