diff --git a/.agents/skills/atomic-plan-contract/SKILL.md b/.agents/skills/atomic-plan-contract/SKILL.md index 6dbcc4172..90bab03ba 100644 --- a/.agents/skills/atomic-plan-contract/SKILL.md +++ b/.agents/skills/atomic-plan-contract/SKILL.md @@ -73,9 +73,22 @@ After preflight all-clear on the minimal-audit plan: - orchestrator MUST checkpoint Phase 0 evidence before branching. Branching after Phase 0: -- `manual bootstrap` → save state and stop for manual resume, +- `manual bootstrap` → save state and stop for manual resume ONLY when the initial user request explicitly opted into manual orchestration from the beginning, - otherwise continue with constrained small-path development, then executor validation, then reduced audit/remediation loop. +## No-Manual-Step Contract (Mandatory) + +Unless the user's initial request explicitly opts into manual orchestration from the beginning, approved plans and remediation plans MUST remain fully automated. + +This prohibition includes: + +- manual bootstrap pauses, +- human-operator validation tasks, +- user-performed repro or QA steps, +- requests for screenshots, notes, or runtime evidence that the agent cannot collect itself. + +When a fully automated equivalent is unavailable, the plan MUST fail closed by recording blocked or remediation-required automated state. It MUST NOT introduce a new manual step later in the workflow. + ## Phase 0 Requirements Phase 0 must include tasks to read policy files in the order defined in `policy-compliance-order`. diff --git a/.agents/skills/feature-promotion-lifecycle/SKILL.md b/.agents/skills/feature-promotion-lifecycle/SKILL.md index 3fb96bc41..72f1c2460 100644 --- a/.agents/skills/feature-promotion-lifecycle/SKILL.md +++ b/.agents/skills/feature-promotion-lifecycle/SKILL.md @@ -89,9 +89,13 @@ When orchestrator routing selects short path, promotion/folder initialization st 6) Execute plan Phase 0 only via executor and checkpoint evidence. 7) Branch: -- manual bootstrap: save state and stop, +- manual bootstrap: save state and stop ONLY when the initial user request explicitly opted into manual orchestration from the beginning, - non-bootstrap: continue with constrained small-path development. +Automation rule: +- do not introduce manual bootstrap, human-operator validation, or any other manual handoff later in orchestration unless that initial explicit opt-in exists +- if automation cannot proceed, record blocked automated state instead of asking for manual intervention + 8) Validate delivery via executor against `issue.md`, then run reduced audit/remediation loop until ready-to-merge. ## Required Outputs for Downstream Handoffs diff --git a/.agents/skills/orchestrator-workflow/SKILL.md b/.agents/skills/orchestrator-workflow/SKILL.md index 620225bfc..7b9063c2a 100644 --- a/.agents/skills/orchestrator-workflow/SKILL.md +++ b/.agents/skills/orchestrator-workflow/SKILL.md @@ -154,7 +154,8 @@ Required behavior: 6. Spawn `atomic-executor` to execute Phase 0 only. - Record a delegation receipt and set `step6_status` to `verified` before branching - If the handoff cannot be started or does not return a receipt, set `step6_status` to `blocked`, set `blocked_reason`, and stop -7. If the request is manual bootstrap, persist the resume checkpoint and stop after Phase 0. +7. If and only if the initial user request explicitly opted into manual orchestration from the beginning, persist the resume checkpoint and stop after Phase 0. + - Otherwise manual bootstrap is prohibited; continue automated execution. 8. Otherwise continue with constrained implementation: - steps that are not modeled as required delegated handoffs may execute directly while staying within the approved plan and applicable repo policy 9. Validate the delivered work against `${feature-folder}/issue.md` and persist plan or acceptance-criteria checkoffs before review. diff --git a/.codex/prompts/orchestrate-work.md b/.codex/prompts/orchestrate-work.md index ccd4ceb0c..215b093d3 100644 --- a/.codex/prompts/orchestrate-work.md +++ b/.codex/prompts/orchestrate-work.md @@ -1,6 +1,6 @@ --- description: Route a request through budget-based orchestration and persist until the selected delivery path is complete -argument-hint: Provide objective, likely files, feature-or-bug hint, constraints, and whether small-path execution should stop after Phase 0 for manual bootstrap +argument-hint: Provide objective, likely files, feature-or-bug hint, constraints, and any explicit initial opt-in for manual bootstrap; otherwise orchestration must remain fully automated --- Spawn `orchestrator` to coordinate the current request from intake through completion. @@ -10,13 +10,14 @@ Inputs to provide or infer: - likely affected production and test files, when known - initial classification hint: `feature` or `bug`, when known - constraints, preserved APIs, or forbidden changes -- whether small-path execution should stop after Phase 0 for manual bootstrap +- whether the initial user request explicitly opted into manual bootstrap from the beginning Required behavior: - estimate change budget first and choose the correct small or large path - maintain and resume from the canonical orchestration checkpoint - use migrated Codex subagents when available - route host-specific lifecycle automation through the shared adapter rules -- continue until planning, execution, validation, and review are complete for the selected path, unless the request explicitly requires a manual-bootstrap pause +- continue until planning, execution, validation, and review are complete for the selected path +- do not introduce manual bootstrap, human-operator validation, or any other manual handoff unless the initial user request explicitly opted in from the beginning On completion, report the selected route, branch, key variables, `plan-path` when applicable, checkpoint path, created or updated artifact paths, and final readiness summary. diff --git a/.github/agents/csharp-orchestrator.agent.md b/.github/agents/csharp-orchestrator.agent.md index 2bfff8c63..afd96f241 100644 --- a/.github/agents/csharp-orchestrator.agent.md +++ b/.github/agents/csharp-orchestrator.agent.md @@ -111,6 +111,10 @@ Use these reusable skills to avoid duplicating shared operations: - `${feature-folder}`: created active feature folder path - `${plan-path}`: workspace-relative path to the single plan file that must be updated in-place across all planning/preflight iterations +5) **No manual steps by default** +- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning. +- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step. + # Workflow router ## Phase 0 — Intake and budget estimate (mandatory) @@ -198,11 +202,11 @@ Hard enforcement for S4: ### Step S5 — Branch by bootstrap mode -S5.1 If request is `manual bootstrap`: +S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning: - Save checkpoint with `next_step` at Phase 1 resume point. - Stop execution and return resume instructions. -S5.2 If request is small development (not manual bootstrap): +S5.2 Otherwise continue automated small development: - Continue to Step S6. ### Step S6 — Delegate constrained small-path development diff --git a/.github/agents/orchestrator.agent.md b/.github/agents/orchestrator.agent.md index 3043e000a..6830e3d5d 100644 --- a/.github/agents/orchestrator.agent.md +++ b/.github/agents/orchestrator.agent.md @@ -110,6 +110,10 @@ Use these reusable skills to avoid duplicating shared operations: - `${feature-folder}`: created active feature folder path - `${plan-path}`: workspace-relative path to the single plan file that must be updated in-place across all planning/preflight iterations +5) **No manual steps by default** +- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning. +- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step. + # Workflow router ## Phase 0 — Intake and budget estimate (mandatory) @@ -197,11 +201,11 @@ Hard enforcement for S4: ### Step S5 — Branch by bootstrap mode -S5.1 If request is `manual bootstrap`: +S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning: - Save checkpoint with `next_step` at Phase 1 resume point. - Stop execution and return resume instructions. -S5.2 If request is small development (not manual bootstrap): +S5.2 Otherwise continue automated small development: - Continue to Step S6. ### Step S6 — Delegate constrained small-path development diff --git a/.github/agents/powershell-orchestrator.agent.md b/.github/agents/powershell-orchestrator.agent.md index 20a1250dc..f59ad542f 100644 --- a/.github/agents/powershell-orchestrator.agent.md +++ b/.github/agents/powershell-orchestrator.agent.md @@ -111,6 +111,10 @@ Use these reusable skills to avoid duplicating shared operations: - `${feature-folder}`: created active feature folder path - `${plan-path}`: workspace-relative path to the single plan file that must be updated in-place across all planning/preflight iterations +5) **No manual steps by default** +- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning. +- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step. + # Workflow router ## Phase 0 — Intake and budget estimate (mandatory) @@ -198,11 +202,11 @@ Hard enforcement for S4: ### Step S5 — Branch by bootstrap mode -S5.1 If request is `manual bootstrap`: +S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning: - Save checkpoint with `next_step` at Phase 1 resume point. - Stop execution and return resume instructions. -S5.2 If request is small development (not manual bootstrap): +S5.2 Otherwise continue automated small development: - Continue to Step S6. ### Step S6 — Delegate constrained small-path development diff --git a/.github/agents/python-orchestrator.agent.md b/.github/agents/python-orchestrator.agent.md index 939920c2c..c7a7916b4 100644 --- a/.github/agents/python-orchestrator.agent.md +++ b/.github/agents/python-orchestrator.agent.md @@ -109,6 +109,10 @@ Use these reusable skills to avoid duplicating shared operations: - `${feature-folder}`: created active feature folder path - `${plan-path}`: workspace-relative path to the single plan file that must be updated in-place across all planning/preflight iterations +5) **No manual steps by default** +- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning. +- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step. + # Workflow router ## Phase 0 — Intake and budget estimate (mandatory) @@ -196,11 +200,11 @@ Hard enforcement for S4: ### Step S5 — Branch by bootstrap mode -S5.1 If request is `manual bootstrap`: +S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning: - Save checkpoint with `next_step` at Phase 1 resume point. - Stop execution and return resume instructions. -S5.2 If request is small development (not manual bootstrap): +S5.2 Otherwise continue automated small development: - Continue to Step S6. ### Step S6 — Delegate constrained small-path development diff --git a/.github/prompts/orchestrate-csharp-work.prompt.md b/.github/prompts/orchestrate-csharp-work.prompt.md index 9828eb19c..8e508d148 100644 --- a/.github/prompts/orchestrate-csharp-work.prompt.md +++ b/.github/prompts/orchestrate-csharp-work.prompt.md @@ -17,6 +17,7 @@ Coordinate the user request from intake to completion using the correct path bas - **Likely affected files (optional):** any known production/test files - **Initial classification hint (optional):** `feature` or `bug` - **Constraints (optional):** APIs/paths/behavior that must remain unchanged +- **Manual orchestration opt-in (optional):** allowed only when the initial user request explicitly asked from the beginning for a manual bootstrap pause ## Required orchestration behavior @@ -29,8 +30,8 @@ Coordinate the user request from intake to completion using the correct path bas 4) Require `atomic_executor` preflight until `PREFLIGHT: ALL CLEAR` 5) Delegate to `atomic_executor` to execute **Phase 0 only** 6) Branch behavior: - - manual bootstrap: save state and stop for manual resume - - non-bootstrap small development: delegate constrained implementation to `csharp-typed-engineer` + - explicit initial manual bootstrap opt-in: save state and stop for manual resume + - otherwise continue automated small development and delegate constrained implementation to `csharp-typed-engineer` 7) Delegate post-delivery validation to `atomic_executor` for validation against issue.md, using only the explicit `## Acceptance Criteria` section for minor-audit acceptance validation, and persist checklist/doc updates 8) Run reduced small-path audit and remediation loop until ready-to-merge 3. If budget is **>3 production C# files** or **>3 test C# files**: @@ -48,6 +49,7 @@ Coordinate the user request from intake to completion using the correct path bas - Maintain orchestration state in `artifacts/orchestration/csharp-orchestrator-state.json`. - Resume from the next incomplete step if interrupted. - Do not end early while required downstream steps remain. +- Do not introduce manual validation or other human-operator steps later in the workflow unless the initial user request explicitly opted in from the beginning. ## Output expectations @@ -62,5 +64,5 @@ On completion, report: For small path also report: - approved `plan-path` - preflight result (`PREFLIGHT: ALL CLEAR`) -- whether `manual bootstrap` branch was taken +- whether an explicit initial manual-bootstrap opt-in was present and used - Phase 0 execution evidence and stored `next_step` for resume diff --git a/.github/prompts/orchestrate-work.prompt.md b/.github/prompts/orchestrate-work.prompt.md index bc4a1fdd2..79cb300cf 100644 --- a/.github/prompts/orchestrate-work.prompt.md +++ b/.github/prompts/orchestrate-work.prompt.md @@ -17,6 +17,7 @@ Coordinate the user request from intake to completion using the correct path bas - **Likely affected files (optional):** any known production/test files - **Initial classification hint (optional):** `feature` or `bug` - **Constraints (optional):** APIs/paths/behavior that must remain unchanged +- **Manual orchestration opt-in (optional):** allowed only when the initial user request explicitly asked from the beginning for a manual bootstrap pause ## Required orchestration behavior @@ -29,8 +30,8 @@ Coordinate the user request from intake to completion using the correct path bas 4) Require `atomic_executor` preflight until `PREFLIGHT: ALL CLEAR` 5) Delegate to `atomic_executor` to execute **Phase 0 only** 6) Branch behavior: - - manual bootstrap: save state and stop for manual resume - - non-bootstrap small development: delegate constrained implementation to the small-path engineer + - explicit initial manual bootstrap opt-in: save state and stop for manual resume + - otherwise continue automated small development and delegate constrained implementation to the small-path engineer 7) Delegate post-delivery validation to `atomic_executor` against `issue.md`, using only the explicit `## Acceptance Criteria` section for minor-audit acceptance validation, and persist checklist/doc updates 8) Run reduced small-path audit and remediation loop until ready-to-merge 3. If budget is **>3 production files** or **>3 test files**: @@ -48,6 +49,7 @@ Coordinate the user request from intake to completion using the correct path bas - Maintain orchestration state in `artifacts/orchestration/orchestrator-state.json`. - Resume from the next incomplete step if interrupted. - Do not end early while required downstream steps remain. +- Do not introduce manual validation or other human-operator steps later in the workflow unless the initial user request explicitly opted in from the beginning. ## Output expectations @@ -62,5 +64,5 @@ On completion, report: For small path also report: - approved `plan-path` - preflight result (`PREFLIGHT: ALL CLEAR`) -- whether `manual bootstrap` branch was taken +- whether an explicit initial manual-bootstrap opt-in was present and used - Phase 0 execution evidence and stored `next_step` for resume diff --git a/.github/skills/atomic-plan-contract/SKILL.md b/.github/skills/atomic-plan-contract/SKILL.md index 6dbcc4172..90bab03ba 100644 --- a/.github/skills/atomic-plan-contract/SKILL.md +++ b/.github/skills/atomic-plan-contract/SKILL.md @@ -73,9 +73,22 @@ After preflight all-clear on the minimal-audit plan: - orchestrator MUST checkpoint Phase 0 evidence before branching. Branching after Phase 0: -- `manual bootstrap` → save state and stop for manual resume, +- `manual bootstrap` → save state and stop for manual resume ONLY when the initial user request explicitly opted into manual orchestration from the beginning, - otherwise continue with constrained small-path development, then executor validation, then reduced audit/remediation loop. +## No-Manual-Step Contract (Mandatory) + +Unless the user's initial request explicitly opts into manual orchestration from the beginning, approved plans and remediation plans MUST remain fully automated. + +This prohibition includes: + +- manual bootstrap pauses, +- human-operator validation tasks, +- user-performed repro or QA steps, +- requests for screenshots, notes, or runtime evidence that the agent cannot collect itself. + +When a fully automated equivalent is unavailable, the plan MUST fail closed by recording blocked or remediation-required automated state. It MUST NOT introduce a new manual step later in the workflow. + ## Phase 0 Requirements Phase 0 must include tasks to read policy files in the order defined in `policy-compliance-order`. diff --git a/.github/skills/feature-promotion-lifecycle/SKILL.md b/.github/skills/feature-promotion-lifecycle/SKILL.md index cb857aaed..431bb32e2 100644 --- a/.github/skills/feature-promotion-lifecycle/SKILL.md +++ b/.github/skills/feature-promotion-lifecycle/SKILL.md @@ -89,9 +89,13 @@ When orchestrator routing selects short path, promotion/folder initialization st 6) Execute plan Phase 0 only via executor and checkpoint evidence. 7) Branch: -- manual bootstrap: save state and stop, +- manual bootstrap: save state and stop ONLY when the initial user request explicitly opted into manual orchestration from the beginning, - non-bootstrap: continue with constrained small-path development. +Automation rule: +- do not introduce manual bootstrap, human-operator validation, or any other manual handoff later in orchestration unless that initial explicit opt-in exists +- if automation cannot proceed, record blocked automated state instead of asking for manual intervention + 8) Validate delivery via executor against `issue.md`, then run reduced audit/remediation loop until ready-to-merge. ## Required Outputs for Downstream Handoffs