spec-driven-development

To write a specification before coding, document the objective, constraints, non-goals, acceptance criteria, and verification plan. This forces a concise, testable spec that prevents ambiguous requirements and scope creep.

Acceptance criteria and verification plans should include explicit objectives, constraints, non-goals, and concrete verification steps. These verification-ready guidelines prove completion and ground the project scope in repository rules.

You need to define a compact spec for a new feature or refactor when requirements are under-specified and need explicit boundaries. This applies to starting new features, refactors, or architectural changes to prevent misinterpretation.

Ground project management specifications in repository rules by aligning objectives and constraints with local AGENTS.md and vault notes. This ensures the specification respects existing repository rules before coding begins.

The best way to define explicit boundaries for under-specified architectural changes is drafting a compact spec. List the objective, target user, constraints, non-goals, acceptance criteria, and a verification plan to enforce testable requirements.