abd-acceptance-criteria

To write acceptance criteria for a story graph, use provided Markdown templates to craft WHEN/THEN/AND/BUT statements anchored to domain terms. This ensures consistent structure and machine-checkable quality across epic, sub-epic, and story levels.

The best way to validate behavioral acceptance criteria is running Python scanners that enforce behavioral AC structure, domain-term emphasis, and channel-specific language. Scanners check atomic segments within your story-graph.json to ensure quality.

Yes, you can use keep-ac-consistent rules and templates to maintain acceptance criteria consistency across connected domains. They support story sizing for coverage and apply a unified voice across all project levels.

Domain terms improve machine-checkable acceptance criteria by anchoring WHEN/THEN/AND/BUT statements to specific project vocabulary. Scanners use these domain terms to validate atomic segments and enforce channel-specific language within story-graph.json.

Templates for exploration phase acceptance criteria require strict adherence to atomic segment constructs and domain terms to function properly. Without consistent voice and structure across epic, sub-epic, and story levels, scanner validation may fail.

Yes, you need Python to execute the included scanners that validate acceptance criteria structure and domain-term usage. Scanners integrate with project rules to automatically check your story-graph.json file quality.