create-agdf 0.2.3 → 0.2.5

package/generated/AGENTS.md

@@ -32,18 +32,24 @@ Use Structured Delivery Mode for new capabilities, architecture, policy, persist
 Any new product semantics, functional change or user-visible behaviour change requires a durable UR first.
 Persist it in `.agdf/control/` or link it from there to the target repository's authoritative source of truth before PRD, SD, TP, Brownfield Analysis or implementation.
 Treat approval text and durable artefact presence as separate checks for UR, PRD, SD, TP and QA report decisions.
-
-Quick Task Mode must still cite evidence and close with a concrete result.
+Do not infer approval from "ok", "go ahead", "do it", "approved", "continue", "leg los" or similar wording.
+Those phrases may express intent to proceed, but they do not unlock a gate unless the exact gate formula is present.
+After `Approval: UR`, run lightweight Brownfield Review before PRD when Brownfield, ownership, runtime, policy, persistence, architecture, UI or UX impact is possible.
+Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `structured_slice`, `structured_delivery` or `block`.
+Make that decision visible before coding or drafting later artefacts: state the selected path, scope reason, evidence and next required gate in the live control state or linked artefact.
+Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies.
+
+Quick Task Mode must still use the Runtime Contract mini-output: `result`, `evidence`, `risk`, `next_step`.
 Structured Delivery Mode must respect gates, reviews and closeout discipline.
 
 ## Skill Routing
 | Skill | Use For | Boundary |
 |---|---|---|
-| `agdf-brownfield-analysis` | after gate-check permits implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners and risks; never bypasses gate-check |
+| `agdf-brownfield-analysis` | after gate-check permits Brownfield Review or implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners, risks and Mode/Slice Decision; never bypasses gate-check; Brownfield Review is not implementation permission |
 | `agdf-clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
 | `agdf-code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |
 | `agdf-delivery-closeout` | commit/PR-near handoff after QA/OR/UAT | never performs VCS actions automatically |
-| `agdf-gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
+| `agdf-gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts or skip Mode/Slice Decision after Brownfield Review |
 | `agdf-qa-gate` | final QA decision | only instance for `pass | revise | block` |
 | `agdf-release-or` | auditable closeout for every relevant run | not a QA substitute |
 | `agdf-task-plan-review` | after implementation and before QA, verify TP coverage | no final QA decision |
@@ -51,6 +57,7 @@ Structured Delivery Mode must respect gates, reviews and closeout discipline.
 Select exactly one primary skill first.
 Add more only when they cover a distinct concrete risk dimension.
 Do not choose `agdf-brownfield-analysis` as the first primary skill for a fresh "I want to build/change X" prompt unless `agdf-gate-check` or existing live AGDF control state already makes implementation preparation the next allowed action.
+Never jump directly from `Approval: UR`, implicit consent, or a generic "start" request to implementation. Route to Brownfield Review, then a visible Mode/Slice Decision with evidence, then the smallest safe next gate or Quick Task execution.
 
 ## Runtime Contract
 For repeated output, gate, Quality Contract and Context Graph rules, use:
@@ -65,6 +72,9 @@ Use templates as starting points only.
 
 Do not let chat history become the source of truth for gate state, approvals, evidence, backlog status or durable Brownfield knowledge.
 
+AGDF is a native agent workflow first: read the live control state, apply the active skill and make the next allowed step explicit.
+Use `doctor`, `gate-check --json` or `delivery-map --json` as validators when a machine-readable proof is useful, not as a substitute for the router or skills.
+
 ## Closeout
 After relevant code, documentation, skill or governance changes:
 

package/generated/plugins/agdf/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agdf",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
   "author": {
     "name": "AI-native Governance & Delivery Framework",

package/generated/plugins/agdf/control/README.md

@@ -9,12 +9,14 @@ Use this scaffold when a target repository should keep AGDF state outside chat h
 | File | Purpose |
 |---|---|
 | `templates/AGDF_RUN.md` | Template for current run state: mode, gate, approvals, evidence, risks, next allowed action |
-| `templates/MASTER_BACKLOG.md` | Template for the living backlog pointer: active initiatives and current UR/PRD/SD/TP artefacts |
+| `templates/MASTER_BACKLOG.md` | Template for the living backlog pointer: active initiatives and current UR/Brownfield/PRD/SD/TP/QA/OR artefacts |
 | `templates/artefacts/UR.md` | Template for the durable user requirement artefact of a work item |
+| `templates/artefacts/BROWNFIELD_REVIEW.md` | Template for the durable Brownfield Review and Mode/Slice Decision |
 | `templates/artefacts/PRD.md` | Template for the durable product requirements artefact |
 | `templates/artefacts/SD.md` | Template for the durable solution design artefact |
 | `templates/artefacts/TP.md` | Template for the durable task and test plan artefact |
 | `templates/artefacts/QA_REPORT.md` | Template for the durable QA decision report |
+| `templates/artefacts/OR.md` | Template for the durable Orchestration Report closeout |
 | `templates/SOT_REGISTRY.md` | Template for the source-of-truth registry: one primary owner per domain |
 | `templates/CONTEXT_GRAPH.md` | Template for project memory: durable decisions, Brownfield findings, risks, evidence and exit criteria |
 | `templates/AGENT_QUALITY_CONTRACTS.json` | Template for machine-readable warning, revise and block contracts for review and QA |
@@ -29,10 +31,12 @@ Use this scaffold when a target repository should keep AGDF state outside chat h
     artefacts/
       <work-item>/
         UR.md
+        BROWNFIELD_REVIEW.md
         PRD.md
         SD.md
         TP.md
         QA_REPORT.md
+        OR.md
     SOT_REGISTRY.md
     CONTEXT_GRAPH.md
     AGENT_QUALITY_CONTRACTS.json
@@ -61,7 +65,9 @@ npm create agdf@latest gate-check --json
 
 - `AGDF_RUN.md` is the current run dashboard.
 - `MASTER_BACKLOG.md` points to active delivery work; detailed artefacts live beside the work item.
+- Brownfield Review records the post-UR Mode/Slice Decision before PRD depth or Quick Task execution is chosen.
 - UR, PRD, SD, TP and QA decisions require durable artefacts or links to the authoritative repository source of truth before the next gate can open.
+- OR records the run closeout and next permissible step; it does not approve later gates.
 - `SOT_REGISTRY.md` decides which document owns which domain.
 - `CONTEXT_GRAPH.md` records durable project knowledge only when it has evidence and an exit criterion.
 - `AGENT_QUALITY_CONTRACTS.json` names reusable block, revise and warning conditions.

package/generated/plugins/agdf/control/templates/AGDF_RUN.md

@@ -5,7 +5,7 @@
 - run_id:
 - started_at:
 - mode: `quick_task | structured_delivery`
-- current_gate: `none | UR | PRD | SD | TP | CD+Tests | CR | QA | UAT | OR`
+- current_gate: `none | UR | Brownfield Review | Mode/Slice Decision | PRD | SD | TP | Quick Task Execution | Brownfield Analysis | CD+Tests | CR | QA | UAT | OR`
 - decision: `pass | revise | block | in_progress`
 - owner:
 
@@ -44,10 +44,34 @@ Valid approval format for new runs: `Approval: <GateName>`.
 | PRD |  | `draft | approved | superseded | not_applicable` |  |
 | SD |  | `draft | approved | superseded | not_applicable` |  |
 | TP |  | `draft | approved | superseded | not_applicable` |  |
+| Brownfield Review |  | `missing | draft | done | not_applicable | superseded` |  |
 | Review |  | `missing | done | not_applicable` |  |
 | QA |  | `missing | pass | revise | block | not_applicable` |  |
 | OR |  | `missing | done | not_applicable` |  |
 
+## Mode / Slice Decision
+
+Set this after Brownfield Review. Do not assume the full gate chain before the existing-system impact is understood.
+Quick Task execution or implementation is not allowed until this decision is visible with scope reason and evidence.
+
+- decision: `undecided | quick_task | structured_slice | structured_delivery | block`
+- required_next_gate: `none | PRD | SD | TP | Brownfield Analysis`
+- scope_reason:
+- evidence:
+- transparency_note:
+
+## Artefact Chain
+
+Keep the active work item traceable. A gate may open only when the previous gate has both exact approval and a durable or linked artefact.
+
+| From | Relationship | To | Evidence |
+|---|---|---|---|
+| UR | `approved_by` | `Approval: UR` |  |
+| PRD | `derived_from` | UR |  |
+| SD | `derived_from` | PRD |  |
+| TP | `derived_from` | SD |  |
+| QA_REPORT | `tests` | TP |  |
+
 ## Evidence
 
 | Evidence | Source | Covers | Strength |

package/generated/plugins/agdf/control/templates/MASTER_BACKLOG.md

@@ -1,30 +1,32 @@
 # AGDF Master Backlog
 
-This file is the living control pointer for active AGDF delivery work. Detailed UR, PRD, SD, TP, QA and OR artefacts should live in stable paths and be linked from here.
+This file is the living control pointer for active AGDF delivery work. Detailed UR, Brownfield Review, PRD, SD, TP, QA and OR artefacts should live in stable paths and be linked from here.
 
 ## Rules
 
 1. New product semantics, functional change or user-visible behaviour change starts as a new UR draft in a stable local artefact path, for example `.agdf/control/artefacts/<key>/UR.md`, unless an authoritative repository SoT already exists and is linked here.
 2. `Approval: UR` adds or updates exactly one steering row with a link to the UR.
-3. PRD, SD, TP and QA report artefacts are created for the same work item after the previous gate is approved.
-4. `Approval: PRD`, `Approval: SD`, `Approval: TP` and `Approval: QA` require the corresponding durable artefact or linked repository SoT before the next gate can open.
-5. Keep only steering-relevant work in `Active Backlog`.
-6. Every active item has exactly one current spec pointer.
-7. Historical artefacts remain linkable but do not override the current pointer.
-8. If an item is superseded, mark the replacement.
-9. If active work grows beyond roughly ten items, triage the backlog.
+3. Brownfield Review is created for the same work item after UR approval when existing-system impact must be sized before PRD depth or Quick Task execution.
+4. PRD, SD, TP and QA report artefacts are created for the same work item after the previous gate is approved and persisted or linked.
+5. `Approval: PRD`, `Approval: SD`, `Approval: TP` and `Approval: QA` require the corresponding durable artefact or linked repository SoT before the next gate can open.
+6. Generic consent such as "ok", "go ahead", "do it", "continue", "leg los" or "approved" does not update a gate. Only `Approval: <GateName>` does.
+7. Keep only steering-relevant work in `Active Backlog`.
+8. Every active item has exactly one current spec pointer and a visible artefact chain.
+9. Historical artefacts remain linkable but do not override the current pointer.
+10. If an item is superseded, mark the replacement.
+11. If active work grows beyond roughly ten items, triage the backlog.
 
 ## Active Backlog
 
-| Prio | Key | Title | Status | Current Spec | Notes |
-|---:|---|---|---|---|---|
-| P1 |  |  | `in_progress | blocked` |  |  |
+| Prio | Key | Title | Status | UR | Brownfield Review | PRD | SD | TP | QA | OR | Current Spec | Notes |
+|---:|---|---|---|---|---|---|---|---|---|---|---|---|
+| P1 |  |  | `in_progress | blocked` |  |  |  |  |  |  |  |  |  |
 
 ## Planned / Parking Lot
 
-| Prio | Key | Title | Status | Current Spec | Notes |
-|---:|---|---|---|---|---|
-| P2 |  |  | `planned | review_needed` |  |  |
+| Prio | Key | Title | Status | UR | Brownfield Review | PRD | SD | TP | QA | OR | Current Spec | Notes |
+|---:|---|---|---|---|---|---|---|---|---|---|---|---|
+| P2 |  |  | `planned | review_needed` |  |  |  |  |  |  |  |  |  |
 
 ## Completed / Superseded Pointers
 

package/generated/plugins/agdf/control/templates/artefacts/BROWNFIELD_REVIEW.md

@@ -0,0 +1,67 @@
+# Brownfield Review: <Title>
+
+Gate: Brownfield Review
+Type: Brownfield Review
+Mode: `post_ur_review`
+Status: `draft | done | not_applicable | superseded`
+
+## Run
+
+- run_id:
+- related_ur:
+- current_gate:
+- reviewer:
+- reviewed_at:
+
+## Objective
+
+What approved UR scope is being sized and routed?
+
+## Existing-System View
+
+| Area | Existing owner or artefact | Evidence | Impact |
+|---|---|---|---|
+| Product semantics |  |  | `none | low | medium | high` |
+| Source of truth |  |  | `none | low | medium | high` |
+| Runtime path |  |  | `none | low | medium | high` |
+| UI / UX |  |  | `none | low | medium | high` |
+| Persistence / data |  |  | `none | low | medium | high` |
+| Tests / QA |  |  | `none | low | medium | high` |
+| Release / operations |  |  | `none | low | medium | high` |
+
+## Reuse And Parallel-Structure Risk
+
+| Finding | Evidence | Risk | Required action |
+|---|---|---|---|
+|  |  | `none | warn | revise | block` |  |
+
+## Mode / Slice Decision
+
+- decision: `quick_task | structured_slice | structured_delivery | block`
+- required_next_gate: `none | PRD | SD | TP | Brownfield Analysis`
+- scope_reason:
+- evidence:
+- transparency_note:
+
+## PRD / SD Open Questions
+
+| Question | Required gate | Impact |
+|---|---|---|
+|  | `none | PRD | SD | TP` | `warn | revise | block` |
+
+## Context Graph Impact
+
+- context_graph_impact: `none | link_only | update_existing_node | new_node_required | sot_drift`
+- context_graph_refs:
+- context_graph_required_action: `none | link | update | create | resolve_drift`
+- context_graph_gate_effect: `none | warning | revise | block`
+- context_graph_evidence:
+
+## Next Permissible Step
+
+- next_allowed_action:
+- forbidden_until_then:
+
+## Quality Outlook
+
+- quality_outlook:

package/generated/plugins/agdf/control/templates/artefacts/OR.md

@@ -0,0 +1,86 @@
+# OR: <Title>
+
+Gate: OR
+Type: Orchestration Report
+Report mode: `OR-lite | OR-full`
+Status: `draft | done | superseded`
+
+## Run
+
+- run_id:
+- related_ur:
+- related_prd:
+- related_sd:
+- related_tp:
+- related_qa_report:
+- mode_slice_decision:
+- current_gate:
+- decision: `pass | revise | block | in_progress`
+
+## Gate State
+
+| Gate or step | Status | Evidence |
+|---|---|---|
+| UR |  |  |
+| Brownfield Review |  |  |
+| Mode/Slice Decision |  |  |
+| PRD |  |  |
+| SD |  |  |
+| TP |  |  |
+| Brownfield Analysis |  |  |
+| CD+Tests |  |  |
+| CR |  |  |
+| QA |  |  |
+| UAT |  |  |
+
+## Delivered
+
+| Item | Evidence |
+|---|---|
+|  |  |
+
+## Not Delivered / Intentionally Deferred
+
+| Item | Reason | Next owner or gate |
+|---|---|---|
+|  |  |  |
+
+## Evidence
+
+| Evidence | Source | Covers | Strength |
+|---|---|---|---|
+|  |  |  | `direct | indirect | weak` |
+
+## Missing Evidence
+
+| Missing evidence | Impact | Required next step |
+|---|---|---|
+|  | `warn | revise | block` |  |
+
+## Risks And Open Items
+
+| Risk or open item | Impact | Owner or mitigation |
+|---|---|---|
+|  | `warn | revise | block` |  |
+
+## Context Graph Impact
+
+- context_graph_impact: `none | link_only | update_existing_node | new_node_required | sot_drift`
+- context_graph_refs:
+- context_graph_required_action: `none | link | update | create | resolve_drift`
+- context_graph_gate_effect: `none | warning | revise | block`
+- context_graph_evidence:
+
+## Next Permissible Step
+
+- next_allowed_action:
+- required_approval:
+- forbidden_until_then:
+
+## Quality Outlook
+
+- quality_outlook:
+
+## Approval
+
+OR does not approve later gates. It records the next permissible step.

package/generated/plugins/agdf/control/templates/artefacts/UR.md

@@ -32,7 +32,7 @@ Which existing repository artefacts, docs, code paths or decisions must be respe
 
 ## 7. Risks And Unknowns
 
-Which questions must PRD, SD or Brownfield Analysis clarify later?
+Which questions must Brownfield Review, PRD, SD or later implementation-preparation Brownfield Analysis clarify?
 
 ## 8. Next Step
 

package/generated/plugins/agdf/meta/agdf-agent-router.md

@@ -33,18 +33,24 @@ Use Structured Delivery Mode for new capabilities, architecture, policy, persist
 Any new product semantics, functional change or user-visible behaviour change requires a durable UR first.
 Persist it in `.agdf/control/` or link it from there to the target repository's authoritative source of truth before PRD, SD, TP, Brownfield Analysis or implementation.
 Treat approval text and durable artefact presence as separate checks for UR, PRD, SD, TP and QA report decisions.
-
-Quick Task Mode must still cite evidence and close with a concrete result.
+Do not infer approval from "ok", "go ahead", "do it", "approved", "continue", "leg los" or similar wording.
+Those phrases may express intent to proceed, but they do not unlock a gate unless the exact gate formula is present.
+After `Approval: UR`, run lightweight Brownfield Review before PRD when Brownfield, ownership, runtime, policy, persistence, architecture, UI or UX impact is possible.
+Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `structured_slice`, `structured_delivery` or `block`.
+Make that decision visible before coding or drafting later artefacts: state the selected path, scope reason, evidence and next required gate in the live control state or linked artefact.
+Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies.
+
+Quick Task Mode must still use the Runtime Contract mini-output: `result`, `evidence`, `risk`, `next_step`.
 Structured Delivery Mode must respect gates, reviews and closeout discipline.
 
 ## Skill Routing
 | Skill | Use For | Boundary |
 |---|---|---|
-| `brownfield-analysis` | after gate-check permits implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners and risks; never bypasses gate-check |
+| `brownfield-analysis` | after gate-check permits Brownfield Review or implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners, risks and Mode/Slice Decision; never bypasses gate-check; Brownfield Review is not implementation permission |
 | `clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
 | `code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |
 | `delivery-closeout` | commit/PR-near handoff after QA/OR/UAT | never performs VCS actions automatically |
-| `gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
+| `gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts or skip Mode/Slice Decision after Brownfield Review |
 | `qa-gate` | final QA decision | only instance for `pass | revise | block` |
 | `release-or` | auditable closeout for every relevant run | not a QA substitute |
 | `task-plan-review` | after implementation and before QA, verify TP coverage | no final QA decision |
@@ -52,6 +58,7 @@ Structured Delivery Mode must respect gates, reviews and closeout discipline.
 Select exactly one primary skill first.
 Add more only when they cover a distinct concrete risk dimension.
 Do not choose `brownfield-analysis` as the first primary skill for a fresh "I want to build/change X" prompt unless `gate-check` or existing live AGDF control state already makes implementation preparation the next allowed action.
+Never jump directly from `Approval: UR`, implicit consent, or a generic "start" request to implementation. Route to Brownfield Review, then a visible Mode/Slice Decision with evidence, then the smallest safe next gate or Quick Task execution.
 
 ## Runtime Contract
 For repeated output, gate, Quality Contract and Context Graph rules, use:
@@ -66,6 +73,9 @@ Use templates as starting points only.
 
 Do not let chat history become the source of truth for gate state, approvals, evidence, backlog status or durable Brownfield knowledge.
 
+AGDF is a native agent workflow first: read the live control state, apply the active skill and make the next allowed step explicit.
+Use `doctor`, `gate-check --json` or `delivery-map --json` as validators when a machine-readable proof is useful, not as a substitute for the router or skills.
+
 ## Closeout
 After relevant code, documentation, skill or governance changes:
 

package/generated/plugins/agdf/meta/agdf-constitution.md

@@ -184,11 +184,11 @@ Gate Discipline
 
 AGDF work follows a gate-driven flow:
 
-    UR → PRD → SD → TP → QA → UAT
+    UR → Brownfield Review → Mode/Slice Decision → PRD/SD/TP as needed → QA → UAT
 
 with internal process steps:
 
-    Brownfield Analysis → CD+Tests → CR → OR
+    Brownfield Review → Mode/Slice Decision → Brownfield Analysis → CD+Tests → CR → OR
 
 Rules:
 
@@ -199,8 +199,17 @@ Rules:
   `Approval: <GateName>`
   Legacy German runs may contain `Freigabe: <GateName>`; keep it as an
   interpretation alias only and write new artefacts with `Approval:`.
-* **Implicit consent is not consent**: "ok", "go", "approved" or similar
-  formulations do not count as gate approvals.
+* **Implicit consent is not consent**: "ok", "go", "approved", "go ahead",
+  "do it", "continue", "leg los" or similar formulations do not count as gate
+  approvals.
+* **No gate skipping**: Urgency, task wording, chat history, "start" requests
+  or implicit consent must not skip from one gate to implementation or to a
+  later artefact. The next allowed action is the next unsatisfied gate or
+  internal mandatory step.
+* **Size before ceremony**: After an approved durable UR, Brownfield Review
+  determines change size and routing before PRD depth is chosen. The Mode/Slice
+  Decision is one of `quick_task`, `structured_slice`, `structured_delivery` or
+  `block`.
 * **No gate leaks**: Later gate artefacts must not be produced when an
   earlier gate is still blocking.
 

package/generated/plugins/agdf/meta/agdf-plugin.definition.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "displayName": "AI Governance & Delivery Framework",
   "developerName": "AI-native Governance & Delivery Framework",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
@@ -42,8 +42,8 @@
   "skillSet": [
     {
       "slug": "brownfield-analysis",
-      "useFor": "after gate-check permits implementation preparation, before non-trivial changes in existing systems",
-      "boundary": "clarifies reuse, owners and risks; never bypasses gate-check"
+      "useFor": "after gate-check permits Brownfield Review or implementation preparation, before non-trivial changes in existing systems",
+      "boundary": "clarifies reuse, owners, risks and Mode/Slice Decision; never bypasses gate-check; Brownfield Review is not implementation permission"
     },
     {
       "slug": "clean-implementation-review",
@@ -63,7 +63,7 @@
     {
       "slug": "gate-check",
       "useFor": "new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested",
-      "boundary": "does not create later artefacts"
+      "boundary": "does not create later artefacts or skip Mode/Slice Decision after Brownfield Review"
     },
     {
       "slug": "qa-gate",

package/generated/plugins/agdf/meta/agdf-runtime-contract.md

@@ -15,26 +15,97 @@ Structured Delivery must not bypass missing approvals.
 New product semantics, functional change, user-visible behaviour, policy, persistence, architecture or release-critical work requires a durable UR in `.agdf/control/` or a linked authoritative repository SoT before later artefacts or implementation.
 UR, PRD, SD, TP and QA report approvals require durable artefacts or linked authoritative repository SoT entries before the next gate can open.
 
+## Quick Task Output
+
+Quick Tasks are intentionally lightweight, but they must not become invisible.
+Use this compact output shape when no formal gate artefact is required:
+
+- `result`: what changed or was concluded
+- `evidence`: files, commands, observations, or reasoning that support the result
+- `risk`: remaining risk or `none`
+- `next_step`: the single next useful action or `none`
+
+## Relevant Run
+
+A relevant run is any run that changes durable state, creates or updates an AGDF artefact, changes code or runtime behaviour, performs a gate decision, blocks on a governance condition, produces QA/UAT/release evidence, or closes a delivery slice.
+
+OR is not mandatory for a pure explanation, read-only inspection, small review, or local debugging step that produces no durable state change and no gate consequence.
+When in doubt, use a short OR-lite only if it clarifies gate state, evidence, risk, or the next permissible step.
+
 ## Gate Rules
 
 - User gates: `UR -> PRD -> SD -> TP -> QA -> UAT`
-- Internal mandatory steps: `Brownfield Analysis -> CD+Tests -> CR -> OR`
+- Internal mandatory steps: `Brownfield Review -> Mode/Slice Decision -> Brownfield Analysis -> CD+Tests -> CR -> OR`
 - Exact approval formula: `Approval: <GateName>`
 - Legacy alias: `Freigabe: <GateName>` may be accepted when reviewing older German runs, but all new outputs must use `Approval: <GateName>`.
-- Implicit consent is not approval.
+- Implicit consent is not approval. Phrases such as "ok", "go ahead", "do it", "approved", "continue", "leg los" or "looks good" are work intent, not gate approval.
 - The earliest blocking gate wins.
 - For UR, PRD, SD, TP and QA, approval and durable artefact presence are separate requirements. A gate is not satisfied by approval text alone when its artefact is missing from `.agdf/control/` or not linked to the authoritative repository SoT.
-- Approval of one user gate permits work on the next gate artefact only. It does not permit implementation unless the approved gate is `TP` and required internal implementation prerequisites are satisfied.
-- `Approval: UR` permits PRD drafting, not implementation.
+- Approval of one user gate permits work on the next allowed gate artefact or required internal step only. It does not permit implementation unless the approved gate is `TP` and required internal implementation prerequisites are satisfied.
+- Gates must never be skipped or inferred from urgency, tone, chat history, task wording or an instruction to "start". The next allowed action is always the next unsatisfied gate or internal mandatory step.
+- `Approval: UR` permits Brownfield Review after G-00 first, then a Mode/Slice Decision. It never permits implementation by itself.
+- PRD, SD and TP depth is chosen after Brownfield Review through the Mode/Slice Decision, not before existing-system impact is understood.
+- The Mode/Slice Decision must be visible before any PRD shortcut, Quick Task execution or implementation: record the decision, required next gate, scope reason and evidence in `AGDF_RUN.md` or an equivalent linked control artefact.
 - `Approval: PRD` permits Solution Design drafting, not implementation.
 - `Approval: SD` permits Task/Test Plan drafting, not implementation.
-- `Approval: TP` permits Brownfield Analysis and then CD+Tests when Brownfield evidence supports it.
+- `Approval: TP` permits implementation-preparation Brownfield Analysis and then CD+Tests when Brownfield evidence supports it.
 - `CD+Tests` is implementation and test status only, not a delivery signal.
 - `code-review` standardizes the mandatory `CR` step, but does not replace QA.
 - `qa-gate` decides final `pass | revise | block`.
 - `release-or` reports the run, but does not replace QA or produce the operative commit/PR handoff.
 - `delivery-closeout` owns the operative Git handoff text when QA/OR/UAT state allows it.
 
+## Brownfield Review After G-00
+
+After an approved and durable UR, perform a lightweight `Brownfield Review` before PRD when Brownfield, UI, UX, admin, runtime, policy, persistence, architecture, ownership or source-of-truth impact is possible.
+
+This review is not a new user approval gate, not PRD, not SD, not TP and not implementation permission.
+It is the sizing and routing step that decides how much later gate discipline is actually needed.
+
+Its output is limited to:
+
+- workstream or follow-up-slice classification
+- `Mode/Slice Decision`: `quick_task | structured_slice | structured_delivery | block`
+- affected existing owners, source-of-truth artefacts, contracts, policies, runtime paths or tests
+- reuse-before-create risks and parallel-structure risks
+- open questions that PRD or SD must resolve
+- whether implementation-preparation Brownfield Analysis will also be needed after TP
+
+Mode/Slice Decision rules:
+
+- `quick_task`: use only when Brownfield Review shows a narrow local change, no new product semantics beyond the approved UR, no architecture/policy/persistence/contract expansion, and evidence is sufficient to proceed with a small implementation plus relevant checks.
+- `structured_slice`: use when some formal artefacts are needed, but they can stay intentionally small and scoped to the approved slice.
+- `structured_delivery`: use when the change has broad product, architecture, runtime, policy, persistence, release or cross-owner impact.
+- `block`: use when ownership, SoT, impact, evidence or product direction is not clear enough to choose a safe path.
+
+A Mode/Slice Decision without scope reason and evidence is not recorded. Treat it as missing and keep the next step at `Mode/Slice Decision`.
+
+## Gate Transition Model
+
+This table is the canonical transition model. Skills may reference it, but must not carry a second complete copy.
+
+| State | Current gate or step | Allowed | Forbidden | Missing approval |
+|---|---|---|---|---|
+| No approved UR | `UR` | clarify user need, formulate and persist UR, request `Approval: UR` | PRD, SD, TP, Brownfield Analysis, implementation, QA, release | `Approval: UR` |
+| `UR` approved and UR artefact persisted or linked, Brownfield Review missing | `Brownfield Review` | classify workstream, existing owners, SoT, reuse risks, change size and PRD/SD open questions; mark review done or not_applicable | PRD, SD, TP, implementation, QA, release | none |
+| Brownfield Review done or not_applicable, Mode/Slice Decision missing or incomplete | `Mode/Slice Decision` | decide `quick_task`, `structured_slice`, `structured_delivery` or `block`; record scope reason, evidence and required next gate depth | PRD, SD, TP, implementation, QA, release | none |
+| Mode/Slice Decision is `quick_task` | `Quick Task Execution` | implement only the narrow approved UR scope, run relevant checks, record evidence and OR-lite when the run is relevant | broad PRD/SD/TP by ritual, scope expansion, QA or release claims without evidence | none |
+| Mode/Slice Decision is `structured_slice` or `structured_delivery`, PRD missing or draft | `PRD` | draft/refine PRD at the smallest justified depth, define scope, acceptance criteria and non-goals, persist/link PRD, request `Approval: PRD` | SD, TP, implementation-preparation Brownfield Analysis, implementation, QA, release | `Approval: PRD` |
+| `PRD` approved and PRD artefact persisted or linked, SD missing or draft | `SD` | draft/refine Solution Design, ownership and architecture, persist/link SD, request `Approval: SD` | TP, implementation, QA, release | `Approval: SD` |
+| `SD` approved and SD artefact persisted or linked, TP missing or draft | `TP` | draft/refine Task/Test Plan, task IDs, evidence plan, persist/link TP, request `Approval: TP` | implementation, QA, release | `Approval: TP` |
+| `TP` approved and TP artefact persisted or linked, Brownfield Analysis missing | `Brownfield Analysis` | run Brownfield Analysis for approved TP scope | implementation, QA, release | none |
+| Brownfield Analysis passed for approved TP | `CD+Tests` | implement approved TP tasks and run tests | QA pass, UAT, release | none |
+| `QA` approved but QA report missing or not pass | `QA` | persist/link QA report with `pass` decision or revise/block evidence | UAT, release | none |
+
+## Brownfield Modes
+
+The `brownfield-analysis` skill has two explicit modes:
+
+- `post_ur_review`: lightweight sizing and routing after approved durable UR; decides Mode/Slice Decision before PRD depth or implementation is chosen.
+- `pre_implementation_analysis`: implementation-preparation analysis after approved durable TP; verifies reuse path, owners, regression risk and fit before `CD+Tests`.
+
+Do not mix the modes silently. Name the active mode in Brownfield output.
+
 ## Quality Contract Output
 
 Structured Delivery skills use this shape when relevant:
@@ -68,12 +139,38 @@ When a repository needs durable AGDF state, use the plugin-local `control/` scaf
 
 - `AGDF_RUN.md` is the current run dashboard.
 - `MASTER_BACKLOG.md` is the living pointer for active delivery work.
+- `BROWNFIELD_REVIEW.md` records the post-UR existing-system view and Mode/Slice Decision before PRD depth or Quick Task execution is chosen.
 - `SOT_REGISTRY.md` prevents parallel sources of truth.
 - `CONTEXT_GRAPH.md` stores durable Brownfield findings, decisions, risks, evidence and exit criteria.
 - `AGENT_QUALITY_CONTRACTS.json` stores reusable block, revise and warning conditions.
+- OR reports live under `.agdf/control/artefacts/<key>/OR.md` when a run closeout is steering-relevant or should be auditable beyond the chat.
 
 The scaffold is not a second documentation site. Link to authoritative artefacts instead of copying them.
 
+## Native Runtime
+
+AGDF must work natively through the plugin router, skills and live `.agdf/control/` artefacts.
+Agents should read the live control state and apply the gate model directly before reaching for helper commands.
+
+Machine-readable commands such as `doctor --json`, `gate-check --json` and `delivery-map --json` are validators and automation interfaces.
+They make the repository state checkable, but they do not replace the native skill workflow or the durable control artefacts.
+
+## Delivery Map
+
+`delivery-map --json` is the machine-readable delivery picture for the active control state.
+It derives, but does not replace, the live `.agdf/control/AGDF_RUN.md` and `MASTER_BACKLOG.md` state.
+
+It must expose:
+
+- approved or active artefacts and approvals
+- `UR -> PRD -> SD -> TP -> QA_REPORT` relationships
+- evidence refs, missing evidence and declared risks
+- Context Graph impact and gate effect
+- findings that explain why the delivery picture is `pass | warn | revise | block`
+
+Missing relationship evidence in the Artefact Chain is at least `revise` once the related gate artefact is approved or passed.
+Declared missing evidence, declared risk or Context Graph gate effect may escalate the delivery map to `warn`, `revise` or `block`.
+
 ## Skill Output
 
 Every skill output should be as short as possible and as concrete as needed.