Intent-Driven Development

Vague instructions produce vague code. If you can't write down what the module must do, must not do, and how you'll know it works — you're not ready to build it.

Hard Rules

These are non-negotiable. Violating any of them means the work is wrong.

1. ALL intent artifacts go in .idd/ at project root. Not specs/, design/, docs/requirements/, or scattered markdown files. One folder, one source of truth — same discipline as .bdd/ for tests.

2. Every INTENT.md opens with an anchor — one sentence declaring why this module exists. Every section must justify itself against that anchor. If it can't, cut it.