diff --git a/agents/product_manager.md b/agents/product_manager.md index b3c6212..822cb82 100644 --- a/agents/product_manager.md +++ b/agents/product_manager.md @@ -43,6 +43,7 @@ You are the Product Manager Agent (PMA). You are the central orchestrator for al * **Post-Task Sync & Evidence:** You are the gatekeeper of implementation evidence. Ensure the Developer/QA has provided the verification artifacts required by the repository testing/evidence policy before calling the specialists for the Post-Task Sync. Instruct each specialist to **introduce themselves and their role** when providing verification feedback. * **Bounce Back Protocol:** If an implementation is rejected during the Post-Task Sync, reuse the original Task tool `task_id` when sending it back to the agent. This ensures they have the full execution history of the rejection. * **Formal Reopen Protocol:** If a task was marked done but later needs discrepancies fixed or minor same-scope changes after implementation, move that same task back into `Active`, append a `Reopen History` entry, and continue using the same task file ID. Reuse the same Task tool `task_id` when resuming delegated task work, and when resuming Workflow Runner execution, reuse both the same Task tool `task_id` and the same Workflow Runner `session_id` when possible. +* **Drive-To-Done:** When the user or repository workflow explicitly asks you to drive work to completion, use Drive-To-Done as an operating discipline: keep the task lifecycle moving until `DONE`, `HARD BLOCKER`, or `CYCLE LIMIT`. Do not treat planning, delegation, or partial evidence as completion. * **Commit Authority:** You own final closure in all modes. Tech Lead is the default commit authority for direct execution paths, while Workflow Runner may perform the final commit only when you explicitly delegated a full-team complex workflow to it. ## Autonomous Delivery Readiness @@ -119,3 +120,4 @@ Record routine PO-proxy decisions in the task file under `Decisions Taken On PO + diff --git a/agents/workflow_runner.md b/agents/workflow_runner.md index 019117d..6fcdf45 100644 --- a/agents/workflow_runner.md +++ b/agents/workflow_runner.md @@ -83,6 +83,12 @@ Your final summary must include `Decisions Taken On PO Behalf`. If none were mad 8. **Finalize:** Once approved, update task/SCR registries, run required validation, archive the task, and perform the authorized final commit for full-team complex workflows. 9. **Return Final Summary:** End with a concise PMA-facing report including Summary, Work Performed, AC Coverage, Evidence, Documentation Impact, Decisions Taken On PO Behalf, Commit, Open Risks, and Closure Recommendation. +## Drive-To-Done Discipline + +When PMA starts this workflow with Drive-To-Done expectations, treat it as an explicit PMA/repository instruction rather than a separate runtime mode. Do not stop at a partial lifecycle stage; continue through the existing Operational Cycle until one terminal state is reached: `DONE`, `HARD BLOCKER`, or `CYCLE LIMIT`. + +At the end of each continuation cycle, inspect the task's Definition of Done and choose the next smallest concrete action needed for closure. Do not expand scope, skip required evidence, or perform implementation directly. + ## Hard Blocker Mechanism If you cannot proceed after reasonable orchestration attempts: @@ -102,3 +108,4 @@ If PMA later reopens the same task because discrepancies or minor same-scope cha + diff --git a/docs/core/drive_to_done.md b/docs/core/drive_to_done.md new file mode 100644 index 0000000..b478f78 --- /dev/null +++ b/docs/core/drive_to_done.md @@ -0,0 +1,30 @@ +# Drive-To-Done + +Drive-To-Done is an explicit NomadWorks execution discipline. It does not replace PMA, Workflow Runner, task files, SCRs, or evidence requirements. + +## Terminal States + +When Drive-To-Done is explicitly requested by the user, PMA, or repository workflow, PMA or Workflow Runner should keep the current task lifecycle moving until one terminal state is reached: + +- `DONE`: Definition of Done is satisfied, evidence is recorded, required docs/registries are updated, and closure authority has approved the result. +- `HARD BLOCKER`: a specific missing input, failed dependency, rejected verification result, or unresolved contradiction prevents further safe progress. +- `CYCLE LIMIT`: the agreed continuation limit is reached before `DONE` or `HARD BLOCKER`. + +## Operating Rules + +- Use the existing task file, acceptance criteria, verification map, and Definition of Done as the source of truth. +- Do not broaden scope to achieve completion. If scope must change, return to PMA/user for approval. +- After each continuation cycle, identify the next concrete unfinished closure requirement. +- If an implementation or verification handoff fails, bounce back to the responsible specialist with the same task context when possible. +- If progress cannot continue safely, stop with `HARD BLOCKER:` and name the exact missing input or failed condition. + +## Cycle Limit + +A 5-cycle continuation limit is the default PMA/Runner discipline recommendation unless the user or PMA explicitly sets a different limit for the current task. This is not runtime-enforced configuration; it is an operating expectation for deciding when to report `CYCLE LIMIT` instead of continuing indefinitely. + +When the limit is reached, report: + +- completed cycles +- remaining Definition of Done gaps +- recommended owner for the next action +- whether the task should be resumed with the same Task tool `task_id` or Workflow Runner `session_id` diff --git a/docs/guides/WORKFLOW.md b/docs/guides/WORKFLOW.md index c6a15e2..9d8f183 100644 --- a/docs/guides/WORKFLOW.md +++ b/docs/guides/WORKFLOW.md @@ -93,6 +93,16 @@ Track these task files under `Active Discussions` in `tasks/current.md` until th - `investigation`: produce findings, reproduction notes, logs when useful, and a recommended next step. - `spec`: produce SCR and documentation updates that capture the accepted change definition and product/architecture impact. +## Drive-To-Done + +When Drive-To-Done is explicitly requested by the user, PMA, or repository workflow, PMA or Workflow Runner should keep the current task lifecycle moving until `DONE`, `HARD BLOCKER`, or `CYCLE LIMIT`. + +- `DONE`: Definition of Done is satisfied and closure authority approves the result. +- `HARD BLOCKER`: safe progress is impossible without a specific missing input or external fix. +- `CYCLE LIMIT`: the agreed continuation limit is reached before closure. + +Drive-To-Done uses existing task files, acceptance criteria, evidence, and registries. It is not a separate workflow model or code-enforced runtime mode. + SCR files use similarly lightweight frontmatter: ```yaml