Begin a brand-new project or module the claim-driven-development way: intent and claims are authored first, as the specification, and the implementation is written to satisfy them, the way tests lead in TDD and specs lead in spec-driven development. Covers scaffolding, writing intent before code, stating claims against signatures before bodies exist, and designing the code so its claims can be proved rather than only sampled. Use when the user is starting a new repository or module and asks to "do this claims-first", "spec it with claims", "set up CDD from scratch", or "design the claims before the code".
