feat: add definition of ready and done policies

Add bundled Definition of Ready and Definition of Done policy files, include them in the shared agent prompt, and reflect them in task and subtask templates with lightweight readiness, completion, and per-AC verification mapping checklists.

Author: shantur

Agents_Common.md

@@ -55,6 +55,7 @@ That document defines:
 
 *   **Documentation Reading:** Whenever reading any file under `docs/` or `tasks/`, the file MUST be read fully to ensure complete understanding of the context and requirements. 
 *   **Role-Specific Guidelines:** Every agent is responsible for reading the core guidance and any applicable repository policy includes that are part of their prompt.
+*   **Definition Of Ready / Done:** All execution should follow the repository's active Definition of Ready and Definition of Done policies.
 *   **Signed Agent Messages:** Agent-to-agent interactions must begin with a signed first message that clearly identifies the sending and receiving agents. Use this exact format on the first line: `[Agent Message] From: <agent_name> To: <agent_name>`. Example: `[Agent Message] From: product_manager To: tech_lead`. If a message does not begin with an agent signature, agents should assume they are speaking directly with the user.
 *   **Pre-task Clarification:** Before starting any task, thoroughly review requirements. If anything is missing, ambiguous, or insufficient, immediately stop and clearly state what is needed, requesting clarification from the manager agent. Do not proceed until all requirements are clear.
 *   **CodeMap-First Navigation:** Before broad repository search, agents should consult the most relevant `codemap.yml` chain for the area they are trying to understand. Use local, parent, root, or explicitly targeted module CodeMaps as the first navigation pass. If no suitable CodeMap exists or it is insufficient, agents may then expand into direct search and source inspection.
@@ -95,5 +96,7 @@ All documentation updates must follow the repository's documentation policy for:
 - documentation ownership, naming, and layout conventions
 
 <include:plugin:docs/core/role_contracts.md>
+<include:policy:definition-of-ready.md>
+<include:policy:definition-of-done.md>
 <include:policy:documentation-guidelines.md>
 <include:plugin:docs/core/task_model.md>

docs/domains/task-lifecycle/OVERVIEW.md

@@ -13,6 +13,7 @@ This domain includes:
 - task classification by `tiny`, `standard`, and `complex`
 - task routing by `implementation`, `investigation`, and `spec`
 - slice-based task planning using `foundation`, `core`, `logic`, `ui`, `polish`, `qa`, and `docs`
+- definition-of-ready and definition-of-done expectations for task execution
 - pre-sync quorum rules
 - task execution flow and handoff expectations
 - verification and archiving expectations
@@ -61,6 +62,8 @@ This domain does not include:
 
 - `docs/core/task_model.md`
 - `docs/core/agent_orchestration.md`
+- `.nomadworks/policies/definition-of-ready.md`
+- `.nomadworks/policies/definition-of-done.md`
 - `tasks/task-template.md`
 - `tasks/subtask-template.md`
 - `docs/core/documentation_structure.md`

policies/README.md

@@ -25,6 +25,14 @@ Files under `.nomadworks/generated/policies/` are reference copies only. They ar
   - Documentation layout, naming, ownership, and update expectations.
   - Used by all agents through the shared prompt.
 
+- `definition-of-ready.md`
+  - Canonical readiness criteria before execution begins.
+  - Used by all agents through the shared prompt and reflected in task templates.
+
+- `definition-of-done.md`
+  - Canonical completion criteria before closure.
+  - Used by all agents through the shared prompt and reflected in task templates.
+
 - `git-commit-messaging.md`
   - Commit subject and body rules.
   - Used by: `tech_lead`, `workflow_runner`

policies/definition-of-done.md

@@ -0,0 +1,26 @@
+# Definition Of Done
+
+A task is done only when the implementation, verification, documentation, and workflow closure requirements are all complete.
+
+## Completion Criteria
+
+- All in-scope acceptance criteria are satisfied or explicitly marked blocked with documented reason.
+- Required tests, builds, and other verification commands pass according to the repository testing policy.
+- Required evidence and verification artifacts are recorded.
+- Product and technical documentation impact is resolved according to the repository documentation policy.
+- Relevant CodeMap updates are completed when the changed code affects entrypoints, wiring, or maintained source structure.
+- Task files, discussion references, and workflow registries are updated as needed.
+- The authorized review and closure roles have completed their required checks.
+- The final committed state includes all required code, documentation, and registry updates for closure.
+
+## Not Done Conditions
+
+- Any required test or build fails.
+- Evidence is missing for claimed verification.
+- Documentation or CodeMap impact remains unresolved.
+- Acceptance criteria are incomplete, unclear, or unverified.
+- Required finalization or archiving steps are missing.
+
+## Operational Rule
+
+A task must not be marked complete while any Definition of Done item remains open.

policies/definition-of-ready.md

@@ -0,0 +1,27 @@
+# Definition Of Ready
+
+A task is ready to begin only when the repository has enough information to execute safely and efficiently without inventing scope.
+
+## Readiness Criteria
+
+- Scope is clear, bounded, and appropriate for the task's declared complexity.
+- The task objective is specific enough that the next responsible agent can act without guessing intent.
+- Acceptance criteria are present, testable, and aligned with the stated scope.
+- Complexity, track, and slice are set correctly for the work being requested.
+- Required dependencies, assumptions, blockers, and open questions are either resolved or explicitly recorded.
+- Required pre-sync specialists have reviewed the task definition according to the active task model.
+- An approved SCR exists whenever the workflow requires one.
+- The relevant repository areas are identified well enough to begin safe investigation, design, or implementation.
+
+## Not Ready Conditions
+
+- Requirements are ambiguous or contradictory.
+- Acceptance criteria are missing or too vague to verify.
+- The task is larger or riskier than its current routing metadata suggests.
+- Required specialist review has not happened yet.
+- A required SCR is missing or not approved.
+- Critical blockers or dependencies are unknown or unrecorded.
+
+## Operational Rule
+
+If the task fails the Definition of Ready, execution should pause until the missing information is resolved or explicitly recorded for follow-up.

tasks/subtask-template.md

@@ -15,12 +15,31 @@ parent: TASK-[PARENT]
 ### Task
 * [ ] [Assigned Agent]: [Action]
 
+### Definition Of Ready Check
+- [ ] Parent task, assigned slice, and local scope are clear.
+- [ ] Local acceptance criteria or expected outcome is clear.
+- [ ] Dependencies, blockers, and assumptions are known or recorded.
+
 ### Acceptance Criteria
 * [Criterion 1]
 
+### Acceptance Criteria Verification Map
+- [ ] AC-1
+  - **Method:** `[unit test | integration test | e2e | manual check | doc review]`
+  - **Owner:** `[agent_name]`
+  - **Evidence:** `[optional path or note]`
+
+Use this section to record the verification method for each local acceptance criterion. Evidence links are optional and should be added only when they materially improve traceability.
+
 ### Assigned To: [Primary Agent]
 ### Status: [todo / in_progress / review / done / blocked]
 
+### Definition Of Done Check
+- [ ] Assigned outcome is complete.
+- [ ] Relevant verification for this subtask is complete.
+- [ ] Evidence or notes are recorded in the parent task when required.
+- [ ] Parent task is updated with the subtask outcome.
+
 # Reviews
 ## [Reviewing Agent]:
 - [Comments]

tasks/task-template.md

@@ -27,13 +27,37 @@ reopened_count: 0
 - **Assigned To:** `[product_manager | business_analyst | tech_lead | technical_architect | developer | qa_engineer | ui_ux_designer | workflow_runner]`
 - **Handoff From:** `[agent_name or null]`
 
+## Definition Of Ready Check
+- [ ] Scope is clear, bounded, and appropriate for the task's declared complexity.
+- [ ] Acceptance criteria are present, testable, and aligned with the objective.
+- [ ] Complexity, track, and slice are set correctly.
+- [ ] Required dependencies, assumptions, blockers, and open questions are resolved or explicitly recorded.
+- [ ] Required pre-sync specialist review is complete.
+- [ ] Required SCR exists and is approved when the workflow requires it.
+
 ## Acceptance Criteria
 - [ ] AC-1: [Primary behavioral or task outcome]
 - [ ] AC-2: [Secondary outcome, validation, or edge-case requirement]
 - [ ] AC-3: Relevant verification is completed and evidence is recorded against each acceptance criterion.
 - [ ] AC-4: Product documentation reflects the latest state of the application for this change, or this task explicitly records that no product-truth update was required.
 - [ ] AC-5: Technical documentation reflects any architectural or implementation-significant change, or this task explicitly records that no technical-truth update was required.
 
+## Acceptance Criteria Verification Map
+- [ ] AC-1
+  - **Method:** `[unit test | integration test | e2e | manual check | doc review]`
+  - **Owner:** `[agent_name]`
+  - **Evidence:** `[optional path or note]`
+- [ ] AC-2
+  - **Method:** `[unit test | integration test | e2e | manual check | doc review]`
+  - **Owner:** `[agent_name]`
+  - **Evidence:** `[optional path or note]`
+- [ ] AC-3
+  - **Method:** `[unit test | integration test | e2e | manual check | doc review]`
+  - **Owner:** `[agent_name]`
+  - **Evidence:** `[optional path or note]`
+
+Use this section to record how each acceptance criterion will be verified. Evidence links are optional and should be added when they materially improve traceability. Shared evidence may cover multiple acceptance criteria.
+
 ### Source Authority (MANDATORY)
 *   **Spec Reference:** [Commit Hash or SCR ID from documentation update]
 *   **Documentation:** [Link to updated SPECIFICATION.md or FEATURES_LIST.md]
@@ -100,6 +124,16 @@ Use this section when a task that was thought to be done must be resumed using t
 * [ ] Product Manager: Acceptance Criteria and Evidence Coverage Verification
 * [ ] User: Final Approval
 
+## Definition Of Done Check
+- [ ] All in-scope acceptance criteria are satisfied or explicitly marked blocked with reason.
+- [ ] Required tests, builds, and verification commands pass.
+- [ ] Required evidence and verification artifacts are recorded.
+- [ ] Documentation impact is resolved according to repository policy.
+- [ ] Relevant CodeMap updates are complete when needed.
+- [ ] Task files and workflow registries are updated.
+- [ ] Authorized review and closure checks are complete.
+- [ ] Final committed state contains all required code, documentation, and registry updates.
+
 ### Finalization
 * [ ] [Assigned Agent]: CodeMap Update (Update `codemap.yml` if entrypoints/wiring changed)
 * [ ] [Assigned Agent]: Documentation Update (Update relevant docs in `docs/`)