Specification Writing

Governing Rule — NO PROCEDURAL REDUCTION

ABSOLUTE RULE: Never condense, summarize, shortcut, or skip detail when creating or updating specification files, PRDs, architecture docs, or any project artifact. Every rewrite must preserve ALL prior depth. Procedural reduction = loss of engineering knowledge = unacceptable.

When updating a spec file:

• Never replace detailed content with summaries
• Never collapse user stories into bullet-point descriptions
• Never remove Gherkin scenarios, edge cases, or error messages
• Never strip UI design system detail (spacing, elevation, radius, states, motion, accessibility)
• Never remove business rules, glossaries, or traceability matrices
• Add new decisions ON TOP of existing depth, not replacing it

Governing Rule — SKILL CONTENT SEPARATION

Hard-learned: 2026-07-26. The user rejected newly-created skills because their SKILL.md files mixed general patterns with project-specific audit data (mentioning Hermex, CarSah, Azdal by name). A skill that references specific projects cannot be reused by future projects.

ABSOLUTE RULE: SKILL.md is the universal pattern — it MUST remain project-agnostic. Project-specific context belongs ONLY in reference files, never in the skill body.