author-item

Topics in the source

• Author an Outcome Item (author-item)
• 1. Stage 1 ATDD: Write Acceptance Test Cases First
• 2. Granularity & Splitting Rules
• 3. Domain Reference Standards (Load When Needed)

An outcome item states the goal, observable acceptance tests, constraints and references. The executing agent chooses the implementation path. This applies acceptance test-driven development (ATDD) to software, product, commercial and operational work. Before drafting a client UI brief, read the executable backend contract using references/client-contract.md. This applies even when the request supplies a plausible screen sketch. When authoring an item, use four fields: 1. Goal (goal): One plain sentence stating who benefits and what changes in the real world (for users, customers, partners, or operators), plus the parent objective and economic value inputs (cost of delay / duration, see references/priority.md). If the request is a list of tasks or steps, extract the single outcome those steps were trying to achieve. 2. Acceptance Test Cases (acceptance): Write concrete, externally observable positive test cases (what must succeed on the real user/partner/operator surface) and negative/invariant test cases (what must be refused, prevented, or left unbroken). Every acceptance criterion must be verifiable without reading the author's session transcript: Software / Product: end-state d

This is an excerpt. Refer to the complete source and its current requirements.