create-agdf 0.14.5 → 0.20.1

package/generated/plugins/copilot/agdf/skills/agdf-qa-gate/SKILL.md

@@ -0,0 +1,205 @@
+---
+name: agdf-qa-gate
+description: "Use this skill for this scope: sole final Quality Readiness decision. Boundary: only instance for `pass | revise | block`. The requested effect, not discovery, decides AGDF activation."
+---
+
+# qa-gate
+
+## Purpose
+Make the formal QA gate decision.
+
+This skill is the only final QA decision point for `pass | revise | block`.
+
+It answers:
+
+- whether `QA pass` is allowed
+- whether the implementation must be revised
+- whether a hard blocker remains
+- whether relevant TP tasks are sufficiently verified
+- whether P0/P1 tasks are complete
+- whether Brownfield fit is sufficient
+- whether solution integrity is sufficient
+- whether blockers, critical risks, or missing evidence remain
+
+## Runtime Contract
+Use `continuation.runtime_contracts` after `skill_continuation`. If absent: listed MCP `agdf_inspect` (`operation: contract`, `module: <name>`); else supplied schema-2 executable/argv_prefix[0] `contract --module <name>`; else bundled files below. MCP reads need no hook or shell. Missing module: stop; never infer/search for runtime.
+
+- `../contracts/quality.md`
+- `../contracts/context-graph.md`
+- `../contracts/gate-transition.md`
+
+`instruction_only`: first load `../contracts/task-target-resolution.md` and `../contracts/interaction.md`.
+
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:START -->
+## Request Activation
+
+- `owner`: `request_activation_contract`
+- `path`: `meta/contracts/request-activation.md`
+- `policy_version`: `1`
+- `guard_fingerprint`: `sha256:af2f01f9e18a3ba1c520faf0691aa1cd4a4299bdfa027cf83651c5d14319bfdc`
+
+Decide effect from loaded instructions before AGDF action.
+
+Abstain silently (no AGDF call) for assessment/explanation/comparison/recommendation/review/diagnosis/advice; hypothetical/example/error/code/quoted/negated delivery language; AGDF as subject; or a read-only constraint absent other delivery. Ambiguity is read-only: answer or ask one neutral question.
+
+Activate for any requested file/code change however small, a binding gate artefact, explicit AGDF/control-lifecycle operation or unambiguous active-run action; delivery wins mixed intent.
+
+Invocation proof: explicit user text/trusted ephemeral action, not discovery/selection, skill load, hooks, cwd, repo/control or prior runs.
+
+Then pick one catalog route; non-authorizing, downstream checks remain.
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:END -->
+
+## Executable Dispatch
+
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `qa-gate`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill qa-gate`, language and working directory.
+For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+`target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
+Quote shell values as data.
+For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
+On skill_continuation use only its target/control. Without that tool and a valid binding: `dispatcher_unavailable`; no runtime search, environment repair
+or help retries. Dispatch never authorizes.
+For a qa-gate skill_continuation, control.candidate_runs is the complete canonical active-run inventory when run selection is unresolved, otherwise an empty array. Use its run_id, objective, normalized current_gate, decision and revision_id fields as data; filter by current_gate: QA and do not rescan run files, invent candidates or omit returned QA candidates.
+
+QA-specific `decision` is exactly `pass | revise | block`.
+`pass` is allowed only when TP coverage, Brownfield fit, solution integrity, and relevant documentation/Context Graph impact are sufficiently evidenced.
+`sot_drift` must not pass silently as a warning.
+Consume applicable findings through `../contracts/quality.md` §Normalized Review Gaps.
+QA must not maintain a second mapping or reclassify review findings.
+
+An eligible evidence-only `revise` may include an explicit deviation proposal according to
+`../contracts/quality.md` §Human QA Acceptance With Deviations. This skill prepares
+the scope, risk, consequence, follow-up and owner; it cannot accept the proposal, turn missing
+evidence into `pass`, or claim native qualification. Only a deliberate human decision on the
+new exact presentation can accept deviations through the existing approval owner. The technical
+QA result and open findings remain unchanged and accompany UAT and OR.
+
+When post-CD+Tests review evidence exists, present the Runtime Contract's derived Quality
+Readiness projection before the detailed QA report: Plan coverage, Solution integrity, Code
+quality and QA decision in that order. Name `qa-gate` as the sole decision owner, show one
+decisive reason and one permissible next action, and keep detailed reports as evidence links or
+on-demand detail. The projection is non-authorizing and must not replace the Run Status Card,
+Gate Transition Card or the durable QA report.
+
+## Resolved Target Run And Evidence Discovery
+
+After the Direct Skill Invocation Preflight resolves one governance target, discover QA context from
+that target instead of asking the user to reconstruct repository evidence:
+
+1. Prefer an explicit run identifier only when it belongs to the resolved governance target and
+   matches the requested QA scope. Otherwise use the returned canonical candidate inventory.
+2. Select exactly one run whose objective matches the request and whose canonical gate state permits
+   QA. Validate the selected state through gate-check or the equivalent agent-native control
+   inspection.
+3. If no eligible run exists, report the current earlier gate or internal step and stop before a QA
+   decision. If several runs remain plausible, list only their identifiers and objectives, request
+   one run selection and stop before a QA decision. Run clarification is a pre-decision outcome, not
+   a fabricated `block` result.
+4. From the selected run and its Artefacts/Artefact Chain, resolve and read the approved TP,
+   Brownfield Analysis, CD+Tests evidence, Task Plan Review, Clean Implementation Review, Code
+   Review, normalized findings, test results and Context Graph state that are present and readable.
+5. Treat inaccessible external evidence and missing mandatory artefacts as explicit evidence gaps.
+   Do not ask the user to paste or relink repository files that the skill can read itself.
+6. Once one eligible QA run is established, evaluate the discovered evidence and emit exactly one
+   `pass | revise | block` decision with one permissible next step.
+
+QA owns the Quality Readiness and QA decision only. It must not reconstruct or promise a Run Status
+Card, Gate Transition Card, native QA card or interactive QA card. Operational run status and gate
+approval orientation remain owned by gate-check and the Interaction Contract.
+
+## Rules
+1. No QA pass without strong evidence.
+2. TP is the reference, not merely working code.
+3. P0/P1 gaps block `pass`.
+4. Brownfield fit is mandatory.
+5. UI surface integrity is mandatory for UI-impacting changes.
+6. Solution integrity is mandatory.
+7. After one eligible QA run is selected, always output exactly one decision: `pass`, `revise`, or `block`.
+8. Open risks, missing tests, partial TP coverage, or side effects must be visible.
+9. Applicable UX Intent Fidelity rows must all be `fulfilled` with suitable visible evidence before `pass`.
+10. A `requirements_gap` routes to PRD revision; QA must not invent or accept the missing criterion.
+11. Any applicable normalized finding that is `open`, missing, unknown, contradictory or supported by
+    insufficient evidence prevents `pass`.
+12. A `resolved` finding counts only when its durable review evidence proves the routed correction or decision.
+
+## When To Use
+- after `CD+Tests`
+- after `code-review`
+- after `task-plan-review`
+- after `clean-implementation-review`
+- before UAT
+- before any claim that implementation is done, releasable, or QA-ready
+- when evidence from Brownfield, TP, or clean-review skills exists
+
+Important:
+
+- `CD+Tests` is implementation and test status only.
+- Without review evidence and TP coverage, `QA pass` is not allowed.
+
+## Inputs
+Use what is available:
+
+- approved TP and TP Review
+- Brownfield Analysis
+- Clean Implementation Review
+- `code-review` or Code Review Report
+- test/build results
+- documentation impact review
+- runtime or UI evidence
+- known blockers and risks
+
+If evidence is missing, lower the decision accordingly.
+
+## Workflow
+1. Resolve the target, select exactly one eligible run and discover its durable evidence.
+2. Confirm the relevant gate context and verify TP coverage.
+3. Verify P0/P1 completion.
+4. Verify Brownfield fit.
+5. Verify UX Intent Fidelity when applicable, including visible evidence for visible-behavior claims.
+6. Consume normalized findings without reclassification; fail closed on every open or invalid row.
+7. Verify solution integrity.
+8. Verify tests and evidence strength.
+9. Verify documentation and Context Graph impact if relevant.
+10. Decide:
+   - `pass`
+   - `revise`
+   - `block`
+11. State the single required next step.
+
+## Output
+Use this shape:
+
+```text
+## QA Gate
+- decision: pass | revise | block
+- evidence:
+- missing_evidence:
+- risks:
+- required_next_step:
+- impact_codes:
+```
+
+If Context Graph impact is relevant, include the fields from `../contracts/context-graph.md`.
+
+### Compact Chat Output
+
+At `pass`: one line — `QA: pass — <one-line summary>`. Reference the durable QA report
+path. Do not show the Quality Readiness projection or evidence inventory in chat.
+At `revise`/`block`: show the decisive dimension, reason and next action.
+
+## Decision Guidance
+- `pass`: required TP tasks are done, evidence is strong, no blocking Brownfield or solution-integrity risk remains.
+- `revise`: implementation is plausible but missing evidence, partial tasks, UX gaps, or fixable integrity issues remain.
+- `block`: hard prerequisite, approval, product semantics, security/compliance, SoT drift, or critical behaviour is unresolved.
+
+## Forbidden
+This skill must not:
+
+- grant QA pass from a green build alone
+- hide partial task completion
+- replace UAT
+- treat missing reviews as completed
+- downgrade SoT drift to harmless warning
+- silently repair, normalize or reroute a review finding
+
+Apply interaction.md Bounded internal recovery and prepared observation for eligible bound follow-up. It adds no gate or approval authority.

package/generated/plugins/copilot/agdf/{copilot-skills → skills}/agdf-release-or/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: agdf-release-or
-description: Use this skill at the end of every relevant run to produce a compact, auditable Orchestration Report. It summarizes gate status, delivered and intentionally not delivered work, TP coverage, Brownfield fit, solution integrity, open risks, and the next permissible step.
+description: "Use this skill for this scope: auditable closeout for every relevant run. Boundary: not a QA substitute. The requested effect, not discovery, decides AGDF activation."
 ---
 
 # release-or
@@ -26,16 +26,49 @@ It reports:
 - whether further quality follow-up or a separate delivery closeout is useful
 
 ## Runtime Contract
-Use these focused runtime-contract modules:
+Use `continuation.runtime_contracts` after `skill_continuation`. If absent: listed MCP `agdf_inspect` (`operation: contract`, `module: <name>`); else supplied schema-2 executable/argv_prefix[0] `contract --module <name>`; else bundled files below. MCP reads need no hook or shell. Missing module: stop; never infer/search for runtime.
 
 - `../contracts/closeout.md`
 - `../contracts/quality.md`
 - `../contracts/context-graph.md`
 - `../contracts/control-scaffold.md`
 
+`instruction_only`: first load `../contracts/task-target-resolution.md` and `../contracts/interaction.md`.
+
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:START -->
+## Request Activation
+
+- `owner`: `request_activation_contract`
+- `path`: `meta/contracts/request-activation.md`
+- `policy_version`: `1`
+- `guard_fingerprint`: `sha256:af2f01f9e18a3ba1c520faf0691aa1cd4a4299bdfa027cf83651c5d14319bfdc`
+
+Decide effect from loaded instructions before AGDF action.
+
+Abstain silently (no AGDF call) for assessment/explanation/comparison/recommendation/review/diagnosis/advice; hypothetical/example/error/code/quoted/negated delivery language; AGDF as subject; or a read-only constraint absent other delivery. Ambiguity is read-only: answer or ask one neutral question.
+
+Activate for any requested file/code change however small, a binding gate artefact, explicit AGDF/control-lifecycle operation or unambiguous active-run action; delivery wins mixed intent.
+
+Invocation proof: explicit user text/trusted ephemeral action, not discovery/selection, skill load, hooks, cwd, repo/control or prior runs.
+
+Then pick one catalog route; non-authorizing, downstream checks remain.
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:END -->
+
+## Executable Dispatch
+
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `release-or`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill release-or`, language and working directory.
+For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+`target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
+Quote shell values as data.
+For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
+On skill_continuation use only its target/control. Without that tool and a valid binding: `dispatcher_unavailable`; no runtime search, environment repair
+or help retries. Dispatch never authorizes.
+
 OR-specific output must make gate status, delivered and intentionally not delivered content, missing approvals, missing evidence, risks, retained fallbacks, and the next permissible step visible.
 When `.agdf/control/` is present, persist or link the OR under `.agdf/control/artefacts/<key>/OR.md` and reference it from the selected canonical `RUN_STATE.md` or `MASTER_BACKLOG.md` when it is steering-relevant.
 Use the Runtime Contract definition of `Relevant Run` to decide whether OR is mandatory or whether a Quick Task mini-closeout is enough.
+Close a `quick_task` with the validator's `run-step --step closeout --result --evidence --risk --next`.
 
 ## Rules
 1. OR is always allowed and mandatory for relevant runs as defined in the Runtime Contract.
@@ -53,7 +86,7 @@ Use the Runtime Contract definition of `Relevant Run` to decide whether OR is ma
 13. Keep machine status normalization in the CLI; do not write internal snake_case status values into the human-facing backlog.
 14. Reconcile Context Graph impact before clean closeout: report `context_graph_reconciliation: resolved | not_applicable | open_gap`.
 15. If Context Graph work remains unresolved, report it as an explicit open gap and do not describe the run as cleanly handoff-ready.
-16. After writing or updating `MASTER_BACKLOG.md`, run `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before closeout. See the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section for the canonical status/artefact label vocabulary.
+16. After writing or updating `MASTER_BACKLOG.md`, run `agdf_inspect` with `operation: doctor` when the host lists it, otherwise `doctor --json` (or the locally available equivalent) and resolve any `AGDF_BACKLOG_STATUS_UNKNOWN` or `AGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWN` finding before closeout. See the AGDF control scaffold's `MASTER_BACKLOG.md` template Rules section for the canonical status/artefact label vocabulary.
 17. When Delivery Map exposes `parent_reconciliation`, report that evaluated object without
     rediscovering or reclassifying the relationship. Keep Child completion and Parent coordination
     visibly separate. An `open` result retains exactly one next action and does not invalidate Child
@@ -66,7 +99,7 @@ Use the Runtime Contract definition of `Relevant Run` to decide whether OR is ma
 - after artefact creation
 - when a gate blocks
 - after `CD+Tests`
-- after `agdf-code-review`
+- after `code-review`
 - after QA
 - after UAT
 - whenever a compact audit closeout is needed
@@ -81,10 +114,10 @@ Use what is available:
 - artefacts created in this run
 - intentionally not delivered content
 - Task Plan
-- `agdf-task-plan-review`
-- `agdf-brownfield-analysis`
-- `agdf-clean-implementation-review`
-- `agdf-code-review`
+- `task-plan-review`
+- `brownfield-analysis`
+- `clean-implementation-review`
+- `code-review`
 - QA Report
 - UAT Report
 - documentation impact review
@@ -111,7 +144,7 @@ If information is missing, state the gap instead of guessing.
 11. Name retained fallbacks and exit criteria.
 12. Set exactly one next permissible step.
 13. Set exactly one quality outlook.
-14. State whether `agdf-delivery-closeout` is the next operational handoff step when code changes exist and the delivery state allows it.
+14. State whether `delivery-closeout` is the next operational handoff step when code changes exist and the delivery state allows it.
 
 ## Output
 Use a compact structure:
@@ -138,10 +171,10 @@ Include `context_graph_reconciliation` whenever Context Graph impact is present.
 ## Forbidden
 This skill must not:
 
-- decide QA in place of `agdf-qa-gate`
+- decide QA in place of `qa-gate`
 - call `CD+Tests` complete, QA-ready, or release-ready
 - hide missing approvals
 - provide later-gate content while an earlier gate blocks
-- produce the operative commit/PR handoff owned by `agdf-delivery-closeout`
+- produce the operative commit/PR handoff owned by `delivery-closeout`
 - execute commit, push, or PR actions
 - infer Parentage, scan sibling runs independently or mutate a Parent

package/generated/plugins/copilot/agdf/skills/agdf-runtime-contract.md

@@ -0,0 +1,24 @@
+# AGDF Runtime Contract
+
+This manifest indexes the thematic runtime-contract modules used by AGDF skills and runtime validation.
+
+<!-- AGDF-RUNTIME-CONTRACT-MODULES:START -->
+| Module | Path | Coverage |
+|---|---|---|
+| Request Activation | `contracts/request-activation.md` | Canonical focused module; follow the linked source for semantics. |
+| Task Target Resolution | `contracts/task-target-resolution.md` | Canonical focused module; follow the linked source for semantics. |
+| Gate Transition | `contracts/gate-transition.md` | Canonical focused module; follow the linked source for semantics. |
+| Gate Artifact Preparation | `contracts/gate-artifact-preparation.md` | Canonical focused module; follow the linked source for semantics. |
+| Interaction | `contracts/interaction.md` | Canonical focused module; follow the linked source for semantics. |
+| Modes | `contracts/modes.md` | Canonical focused module; follow the linked source for semantics. |
+| Quality | `contracts/quality.md` | Canonical focused module; follow the linked source for semantics. |
+| Context Graph | `contracts/context-graph.md` | Canonical focused module; follow the linked source for semantics. |
+| Control Scaffold | `contracts/control-scaffold.md` | Canonical focused module; follow the linked source for semantics. |
+| Closeout | `contracts/closeout.md` | Canonical focused module; follow the linked source for semantics. |
+| UR Definition | `contracts/ur-definition.md` | Canonical focused module; follow the linked source for semantics. |
+| PRD Definition | `contracts/prd-definition.md` | Canonical focused module; follow the linked source for semantics. |
+| SD Definition | `contracts/sd-definition.md` | Canonical focused module; follow the linked source for semantics. |
+| TP Definition | `contracts/tp-definition.md` | Canonical focused module; follow the linked source for semantics. |
+<!-- AGDF-RUNTIME-CONTRACT-MODULES:END -->
+
+The explanatory framework lives in `docs/`, the operating philosophy in `plugins/agdf/meta/agdf-constitution.md`, and the principles in `plugins/agdf/meta/agdf-tenets.md`.

package/generated/plugins/copilot/agdf/skills/agdf-sd-definition/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: agdf-sd-definition
+description: "Use this skill for this scope: bound SD content. Boundary: content only; preserves approved intent. The requested effect, not discovery, decides AGDF activation."
+---
+
+# sd-definition
+
+## Runtime Contract
+
+Use the returned `continuation.runtime_contracts` after `skill_continuation`. If absent, load
+`../contracts/sd-definition.md` and `../contracts/gate-artifact-preparation.md`
+through the supplied contract reader or bundled files.
+Missing contract or invalid binding: stop. This skill owns SD content; gate-check owns readiness.
+
+`instruction_only`: first load `../contracts/task-target-resolution.md` and `../contracts/interaction.md`.
+
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:START -->
+## Request Activation
+
+- `owner`: `request_activation_contract`
+- `path`: `meta/contracts/request-activation.md`
+- `policy_version`: `1`
+- `guard_fingerprint`: `sha256:af2f01f9e18a3ba1c520faf0691aa1cd4a4299bdfa027cf83651c5d14319bfdc`
+
+Decide effect from loaded instructions before AGDF action.
+
+Abstain silently (no AGDF call) for assessment/explanation/comparison/recommendation/review/diagnosis/advice; hypothetical/example/error/code/quoted/negated delivery language; AGDF as subject; or a read-only constraint absent other delivery. Ambiguity is read-only: answer or ask one neutral question.
+
+Activate for any requested file/code change however small, a binding gate artefact, explicit AGDF/control-lifecycle operation or unambiguous active-run action; delivery wins mixed intent.
+
+Invocation proof: explicit user text/trusted ephemeral action, not discovery/selection, skill load, hooks, cwd, repo/control or prior runs.
+
+Then pick one catalog route; non-authorizing, downstream checks remain.
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:END -->
+
+## Executable Dispatch
+
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `sd-definition`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill sd-definition`, language and working directory.
+For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+`target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
+Quote shell values as data.
+For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
+On skill_continuation use only its target/control. Without that tool and a valid binding: `dispatcher_unavailable`; no runtime search, environment repair
+or help retries. Dispatch never authorizes.
+
+## Workflow
+
+Follow the focused SD contract using the original request and answered conversation context.
+Write only the supplied unapproved SD from approved PRD and analyses, preserving uncertainty and explicit human approval.
+After canonical recording, redispatch gate-check; use its fresh presentation and wait.

package/generated/plugins/copilot/agdf/{copilot-skills → skills}/agdf-task-plan-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: agdf-task-plan-review
-description: Use this skill after code changes and before QA to verify whether the approved Task Plan was actually fulfilled. It checks each task_id against implementation, acceptance criteria, tests, visible evidence, and deviations, and provides TP coverage for QA.
+description: "Use this skill for this scope: evidence dimension: verify whether the approved Task Plan was fulfilled. Boundary: supports Quality Readiness; no final QA decision. The requested effect, not discovery, decides AGDF activation."
 ---
 
 # task-plan-review
@@ -14,17 +14,49 @@ For each relevant task, this skill determines:
 - which acceptance criteria are done, partial, missing, or not verifiable
 - which files, tests, runtime evidence, or UI evidence support the finding
 - evidence strength
-- which gaps must be handed to `agdf-qa-gate`
+- which gaps must be handed to `qa-gate`
 
 This skill provides TP coverage. It is not the final QA decision.
 
 ## Runtime Contract
-Use these focused runtime-contract modules:
+Use `continuation.runtime_contracts` after `skill_continuation`. If absent: listed MCP `agdf_inspect` (`operation: contract`, `module: <name>`); else supplied schema-2 executable/argv_prefix[0] `contract --module <name>`; else bundled files below. MCP reads need no hook or shell. Missing module: stop; never infer/search for runtime.
 
 - `../contracts/quality.md`
 - `../contracts/context-graph.md`
 - `../contracts/gate-transition.md`
 
+`instruction_only`: first load `../contracts/task-target-resolution.md` and `../contracts/interaction.md`.
+
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:START -->
+## Request Activation
+
+- `owner`: `request_activation_contract`
+- `path`: `meta/contracts/request-activation.md`
+- `policy_version`: `1`
+- `guard_fingerprint`: `sha256:af2f01f9e18a3ba1c520faf0691aa1cd4a4299bdfa027cf83651c5d14319bfdc`
+
+Decide effect from loaded instructions before AGDF action.
+
+Abstain silently (no AGDF call) for assessment/explanation/comparison/recommendation/review/diagnosis/advice; hypothetical/example/error/code/quoted/negated delivery language; AGDF as subject; or a read-only constraint absent other delivery. Ambiguity is read-only: answer or ask one neutral question.
+
+Activate for any requested file/code change however small, a binding gate artefact, explicit AGDF/control-lifecycle operation or unambiguous active-run action; delivery wins mixed intent.
+
+Invocation proof: explicit user text/trusted ephemeral action, not discovery/selection, skill load, hooks, cwd, repo/control or prior runs.
+
+Then pick one catalog route; non-authorizing, downstream checks remain.
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:END -->
+
+## Executable Dispatch
+
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `task-plan-review`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill task-plan-review`, language and working directory.
+For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+`target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
+Quote shell values as data.
+For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
+On skill_continuation use only its target/control. Without that tool and a valid binding: `dispatcher_unavailable`; no runtime search, environment repair
+or help retries. Dispatch never authorizes.
+
 TP-specific output must evaluate every relevant `task_id` with completion status, AC coverage, evidence, missing evidence, and QA-relevant gaps.
 If `context_graph_required_action` is not `none`, the affected task is complete only if follow-up, evidence, or an intentionally open gap is visible.
 Applicable review gaps must use `../contracts/quality.md` §Normalized Review Gaps. This skill

package/generated/plugins/copilot/agdf/skills/agdf-tp-definition/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: agdf-tp-definition
+description: "Use this skill for this scope: bound TP content. Boundary: content only; preserves approved sources. The requested effect, not discovery, decides AGDF activation."
+---
+
+# tp-definition
+
+## Runtime Contract
+
+Use the returned `continuation.runtime_contracts` after `skill_continuation`. If absent, load
+`../contracts/tp-definition.md` and `../contracts/gate-artifact-preparation.md`
+through the supplied contract reader or bundled files.
+Missing contract or invalid binding: stop. This skill owns TP content; gate-check owns readiness.
+
+`instruction_only`: first load `../contracts/task-target-resolution.md` and `../contracts/interaction.md`.
+
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:START -->
+## Request Activation
+
+- `owner`: `request_activation_contract`
+- `path`: `meta/contracts/request-activation.md`
+- `policy_version`: `1`
+- `guard_fingerprint`: `sha256:af2f01f9e18a3ba1c520faf0691aa1cd4a4299bdfa027cf83651c5d14319bfdc`
+
+Decide effect from loaded instructions before AGDF action.
+
+Abstain silently (no AGDF call) for assessment/explanation/comparison/recommendation/review/diagnosis/advice; hypothetical/example/error/code/quoted/negated delivery language; AGDF as subject; or a read-only constraint absent other delivery. Ambiguity is read-only: answer or ask one neutral question.
+
+Activate for any requested file/code change however small, a binding gate artefact, explicit AGDF/control-lifecycle operation or unambiguous active-run action; delivery wins mixed intent.
+
+Invocation proof: explicit user text/trusted ephemeral action, not discovery/selection, skill load, hooks, cwd, repo/control or prior runs.
+
+Then pick one catalog route; non-authorizing, downstream checks remain.
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:END -->
+
+## Executable Dispatch
+
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `tp-definition`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill tp-definition`, language and working directory.
+For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+`target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
+Quote shell values as data.
+For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
+On skill_continuation use only its target/control. Without that tool and a valid binding: `dispatcher_unavailable`; no runtime search, environment repair
+or help retries. Dispatch never authorizes.
+
+## Workflow
+
+Follow the focused TP contract using the original request and answered conversation context.
+Write only the supplied unapproved TP from approved PRD/SD and analyses, preserving uncertainty and explicit human approval.
+After canonical recording, redispatch gate-check; use its fresh presentation and wait.

package/generated/plugins/copilot/agdf/skills/agdf-ur-definition/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: agdf-ur-definition
+description: "Use this skill for this scope: bound UR drafting, clarification or revision. Boundary: content only; preserves approved intent. The requested effect, not discovery, decides AGDF activation."
+---
+
+# ur-definition
+
+## Runtime Contract
+
+Use the returned `continuation.runtime_contracts` after `skill_continuation`. If absent, load
+`../contracts/ur-definition.md` through the supplied contract reader or bundled file.
+Missing contract or invalid binding: stop. This skill owns UR content; gate-check owns readiness.
+
+`instruction_only`: first load `../contracts/task-target-resolution.md` and `../contracts/interaction.md`.
+
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:START -->
+## Request Activation
+
+- `owner`: `request_activation_contract`
+- `path`: `meta/contracts/request-activation.md`
+- `policy_version`: `1`
+- `guard_fingerprint`: `sha256:af2f01f9e18a3ba1c520faf0691aa1cd4a4299bdfa027cf83651c5d14319bfdc`
+
+Decide effect from loaded instructions before AGDF action.
+
+Abstain silently (no AGDF call) for assessment/explanation/comparison/recommendation/review/diagnosis/advice; hypothetical/example/error/code/quoted/negated delivery language; AGDF as subject; or a read-only constraint absent other delivery. Ambiguity is read-only: answer or ask one neutral question.
+
+Activate for any requested file/code change however small, a binding gate artefact, explicit AGDF/control-lifecycle operation or unambiguous active-run action; delivery wins mixed intent.
+
+Invocation proof: explicit user text/trusted ephemeral action, not discovery/selection, skill load, hooks, cwd, repo/control or prior runs.
+
+Then pick one catalog route; non-authorizing, downstream checks remain.
+<!-- AGDF-REQUEST-ACTIVATION-GUARD:END -->
+
+## Executable Dispatch
+
+Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `ur-definition`, `presentation_language`, `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools.
+If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill ur-definition`, language and working directory.
+For `--language`: Required presentation language for the latest natural-language user request as one well-formed BCP 47 tag. If the request explicitly asks for a response language, use that tag; otherwise use the dominant request language. Use en when mixed or ambiguous. A valid unsupported tag renders through the complete English pack. Missing or invalid input fails before governance evaluation.
+`target_source`: `explicit_target` if request names `primary_target`; `continued_target` if it unambiguously continues confirmed target; `current_repository` if request names this/current repo with one matching repo active. Otherwise omit the pair; cwd has no target authority.
+Quote shell values as data.
+For a result with `terminal: true`, the entire assistant response must consist only of host_action.text, copied verbatim. Add no question, explanation, heading, citation, link or other surrounding text; do not translate or reformat it; invoke no later tool and stop.
+On skill_continuation use only its target/control. Without that tool and a valid binding: `dispatcher_unavailable`; no runtime search, environment repair
+or help retries. Dispatch never authorizes.
+
+## Workflow
+
+Follow the focused UR contract using the original request and answered conversation context.
+Preserve explicitly requested previews and other clarification deliverables, their purpose and
+review timing in the UR; creation belongs to the later bound analytical step.
+Set the initial `Preview requirement` metadata according to the UR contract; a required
+interactive before-PRD preview uses `before_prd_interactive`, otherwise `none`.
+Write only the supplied unapproved UR, preserving uncertainty and explicit human approval.
+After canonical recording, redispatch gate-check; use its fresh presentation and wait.