Spec-First Planning

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY in this skill are to be interpreted as described in BCP 14 (RFC 2119, RFC 8174) when, and only when, they appear in all capitals.

Turn "we should probably add X" into two mechanically linked artifacts: a spec whose every requirement is falsifiable, and a task plan whose every task names the check that proves it done. In this house, planning the work means planning the verification — a requirement nobody can fail is an opinion, and a task without a verify step can only ever be "looks done". The tooling holds that line deterministically: a linter rejects unfalsifiable specs, and a compiler refuses to emit a plan with coverage holes.

Locating this skill's helpers (do this first). The steps below run bundled scripts. You execute from the target repo, not from this skill's directory, so a path written relative to this skill will not resolve. Resolve the base directory once and use it everywhere — including in any subagent prompt, which MUST receive the literal absolute path: