Building GTD Domain Packs

Create a focused domain extension that inherits Get Things Done instead of copying it.

Load references/domain-pack-spec.md at the start — the required headings, field contracts, and validation rules live there. Load references/core-contract.md to confirm what the core already handles before extending it.

Build method

1. Collect failure examples first Gather at least four realistic tasks: messy in-domain, well-formed in-domain, deceptive near-complete, and adjacent out-of-domain

2. Prove the core is insufficient Identify which field-specific vocabulary, readiness, review, or completion behavior is missing. If the core already handles the examples, do not create a pack

3. Define selection boundaries Write positive and negative selection signals based on intent and artifacts, not isolated keywords

4. Extract only consequential vocabulary Keep terms whose confusion would change decisions, execution, or verification