--- name: ur-definition description: "Use this skill for this scope: UR drafting in planning scope or a bound Run. Boundary: content only; no start or approval authority. The requested effect, not discovery, decides AGDF activation." --- # ur-definition ## Runtime Contract Use the returned `continuation.runtime_contracts` after `skill_continuation`. If absent, load `../../meta/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 `../../meta/contracts/task-target-resolution.md` and `../../meta/contracts/interaction.md`. ## 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. ## Executable Dispatch Use listed MCP `agdf_dispatch` (load deferred; host prefix allowed): `skill_id` `ur-definition`, `presentation_language` (optional override), `working_directory`, and only bound `target_source`/`primary_target` and `run_id`. Never search unlisted tools. For deliberate pre-Run planning, pass the confirmed `planning` scope instead of `run_id`. Use `plan-` and null expected digest for capture, or the inspected plan identity/current digest for refinement. No delivery intake/continue/revision fields. Follow only `phase: planned_ur_definition`, shared template/contract and planning-scoped typed writers. Missing compatible Core stops before mutation; no CLI/shell writer or Run-assignment fallback. If absent/failing: supplied schema-2 executable, child-only environment, immutable argv_prefix, declared arguments; `--skill ur-definition`, language and working directory. MCP: MCP reply-language override (BCP 47). Omit for a matching configured preference; otherwise supply the current request's language (explicit instruction, then dominant language, en if ambiguous). Invalid explicit tags fail; valid unsupported tags use the complete English pack. Core input remains complete. For `--language`: Required; apply the same current-request selection and locale validation. `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. In Run mode, after canonical recording redispatch gate-check; use its fresh presentation and wait. In planning mode, report the saved draft, source and remaining questions without requesting a gate approval. Only a later explicit selected-source start request uses the Core handoff contract.