release-or
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.
SKILL.mdplugins/agdf/skills/release-or/SKILL.md
GitHubrelease-or
Purpose
Produce the Orchestration Report (OR) as the mandatory closeout for a relevant run.
It reports:
- current user gate
- whether the run is
pass,revise,block, or not yet QA-decided - what was delivered
- what was intentionally not delivered
- missing approvals
- TP coverage status
- Brownfield fit
- solution integrity
- documentation impact
- Context Graph impact
- evaluated Parent reconciliation and programme aggregation from Delivery Map
- open risks, blockers, retained fallbacks, and exit criteria
- next permissible step
- whether further quality follow-up or a separate delivery closeout is useful
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.
../../meta/contracts/closeout.md../../meta/contracts/quality.md../../meta/contracts/context-graph.md../../meta/contracts/control-scaffold.md
instruction_only: first load ../../meta/contracts/task-target-resolution.md and ../../meta/contracts/interaction.md.
Request Activation
owner:request_activation_contractpath:meta/contracts/request-activation.mdpolicy_version:1guard_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
- OR is always allowed and mandatory for relevant runs as defined in the Runtime Contract.
- OR is an audit report, not a blocking gate.
- Do not leak artefacts from blocked later gates.
- Use OR-lite when early gates block.
- Use OR-full only within the allowed scope.
- Report status, not marketing language.
- Name missing approvals, partial implementation, risks, fallbacks, Brownfield issues, and open defects.
- Retained fallbacks require visible exit criteria and cleanup path.
- End with the immediately permissible next step.
CD+Testsis not completion.- When moving a backlog item to Completed or Superseded, use the canonical human-readable table and link the final OR with a document-relative Markdown link.
- For an executed
verified_change, a lifecycle-consistent complete Mini-Closeout in the linkedVERIFIED_CHANGE.mdis the compact OR target; do not require a separateOR.mdby ritual. - Keep machine status normalization in the CLI; do not write internal snake_case status values into the human-facing backlog.
- Reconcile Context Graph impact before clean closeout: report
context_graph_reconciliation: resolved | not_applicable | open_gap. - If Context Graph work remains unresolved, report it as an explicit open gap and do not describe the run as cleanly handoff-ready.
- After writing or updating
MASTER_BACKLOG.md, runagdf_inspectwithoperation: doctorwhen the host lists it, otherwisedoctor --json(or the locally available equivalent) and resolve anyAGDF_BACKLOG_STATUS_UNKNOWNorAGDF_BACKLOG_ARTEFACT_LABEL_UNKNOWNfinding before closeout. See the AGDF control scaffold'sMASTER_BACKLOG.mdtemplate Rules section for the canonical status/artefact label vocabulary. - When Delivery Map exposes
parent_reconciliation, report that evaluated object without rediscovering or reclassifying the relationship. Keep Child completion and Parent coordination visibly separate. Anopenresult retains exactly one next action and does not invalidate Child QA, UAT or OR completion. - Report
programme_aggregationonly when applicable. Preservestartableandfinal_readyas non-authorizing evidence values; never treat either as a gate or approval.
When To Use
- at the end of every relevant run
- after artefact creation
- when a gate blocks
- after
CD+Tests - after
code-review - after QA
- after UAT
- whenever a compact audit closeout is needed
Do not force OR onto a pure explanation, read-only inspection, small review, or local debugging step that produces no durable state change and no gate consequence.
Inputs
Use what is available:
- current gate
- existing approvals
- artefacts created in this run
- intentionally not delivered content
- Task Plan
task-plan-reviewbrownfield-analysisclean-implementation-reviewcode-review- QA Report
- UAT Report
- documentation impact review
- Context Graph impact
- known risks, defects, fallbacks, and open questions
- test/build status and relevant metrics
If information is missing, state the gap instead of guessing.
Workflow
- Determine the current gate and earliest blocker.
- Determine report depth:
OR-lite: gate status, allowed/forbidden outputs, missing approval, next stepOR-full: also delivered artefacts, TP coverage, Brownfield fit, solution integrity, risks, fallbacks, QA/UAT status
- Record the selected
Report modeand durable OR target or link when.agdf/control/exists. - Record delivered vs intentionally not delivered content.
- Summarize TP coverage if a TP exists.
- Summarize Brownfield fit and solution integrity if reviewed.
- Summarize tests and verification.
- Summarize documentation and Context Graph impact if relevant.
- Record Context Graph reconciliation as
resolved,not_applicable, oropen_gap. - Copy applicable evaluated Parent reconciliation and programme aggregation from Delivery Map into the OR without mutating another run.
- Name retained fallbacks and exit criteria.
- Set exactly one next permissible step.
- Set exactly one quality outlook.
- State whether
delivery-closeoutis the next operational handoff step when code changes exist and the delivery state allows it.
Output
Use a compact structure:
## OR
- gate:
- report_mode:
- artefact:
- status:
- delivered:
- intentionally_not_delivered:
- evidence:
- missing_evidence:
- risks:
- retained_fallbacks:
- required_next_step:
- quality_outlook:
When Context Graph impact is relevant, include the fields from ../../meta/contracts/context-graph.md.
Include context_graph_reconciliation whenever Context Graph impact is present. If the value is open_gap, required next step must resolve or explicitly retain that gap before commit-ready or release-ready handoff.
Forbidden
This skill must not:
- decide QA in place of
qa-gate - call
CD+Testscomplete, 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
delivery-closeout - execute commit, push, or PR actions
- infer Parentage, scan sibling runs independently or mutate a Parent