Name: Shape Horizon Execution
Author: rhodiusjeff

Prompt file imported from rhodiusjeff/PokerNight (.github/prompts/shape-horizon-execution.prompt.md). Copyright stays with the author.

NEW-CONTEXT DISPATCH: after help handling, inspect the selected ID with planning-capture.py inspect --root ROOT --id ID. A resolved new-format capture uses work shaping's new-context branch directly under the current authorized caller, without mandatory delegation or old tracker laydown. Default is partial draft --section work; explicit --complete composes/proposes the complete result against supplied base/execution. Retain this command's timing and separate admission boundary. This dispatch overrides only conflicting legacy rules below; actual legacy packets retain them. Missing/malformed new documents refuse; never synthesize an ADHOC identity for a horizon.

INVOCATION CONTRACT: this prompt must be invoked from inside the Control Plane: Lifecycle Facilitator persona. The Facilitator resolves lifecycle context and invokes Project: Planning and Design as the bounded execution-laydown specialist. This workflow shapes proposed execution authority but does not admit the horizon.

For --help/-h, explain iterative default, complete laydown, outputs, verification and examples; do not write or open timing. Examples: /shape-horizon-execution H000, /shape-horizon-execution H000 Canon rework, /shape-horizon-execution H000 --exploratory, and /shape-horizon-execution H000 --complete.

Interpret [HNNN] [scope] [--complete | --exploratory]; refuse combined flags before writes. Default to candidate work shaping. --exploratory is a compatibility alias for that default. Load .github/skills/work-plan-shaping/SKILL.md, resolve the inception packet and shaping branch, then delegate to Project: Planning and Design with the exact inputs, requested mode and scope. The specialist follows the skill; it must not infer complete-laydown permission from candidate work.

Verify its outputs and summarize candidate deltas or complete laydown, actual checks, gaps and next decision. Keep complete-laydown requirements intact. Neither mode invokes preparation, readiness review, approval, admission, or start; admission and exit mechanics are unchanged.

Timing-log required actions

Contract: control-plane/framework/governance/timing/timing-log.spec.md section "Prompt Timing Contract".

Record proposal or complete-laydown mode in invocation and terminal metadata; success describes the requested pass, never admission. Follow blocked/interrupted closure rules as applicable.

Open + invoke under LC-HORIZON, emitting /shape-horizon-execution-invoked with --harness, --model-id, Facilitator --persona, and --invocation-source. Record the delegated Planning persona in event metadata or the specialist's own evidence.
On terminal success emit /shape-horizon-execution-complete --outcome success, then close the timing session.

Install Shape Horizon Execution and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

NEW-CONTEXT DISPATCH: after help handling, inspect the selected ID with `planning-capture.py inspect --root ROOT --id ID`. A resolved new-format capture uses [work shaping](../skills/work-plan-shaping/SKILL.md)'s new-context branch directly under the current authorized caller, without mandatory delegation or old tracker laydown. Default is partial `draft --section work`; explicit `--complete` composes/proposes the complete result against supplied base/execution. Retain this command's timing and separate admission boundary. This dispatch overrides only conflicting legacy rules below; actual legacy packets retain them. Missing/malformed new documents refuse; never synthesize an ADHOC identity for a horizon. INVOCATION CONTRACT: this prompt must be invoked from inside the `Control Plane: Lifecycle Facilitator` persona. The Facilitator resolves lifecycle context and invokes `Project: Planning and Design` as the bounded execution-laydown specialist. This workflow shapes proposed execution authority but does not admit the horizon. For `--help`/`-h`, explain iterative default, complete laydown, outputs, verification and examples; do not write or open timing. Examples: `/shape-horizon-execution H000`, `/shape-horizon-execution H000 Canon rework`, `/shape-horizon-execution H000 --exploratory`, and `/shape-horizon-execution H000 --complete`. Interpret `[HNNN] [scope] [--complete | --exploratory]`; refuse combined flags before writes. Default to candidate work shaping. `--exploratory` is a compatibility alias for that default. Load `.github/skills/work-plan-shaping/SKILL.md`, resolve the inception packet and shaping branch, then delegate to `Project: Planning and Design` with the exact inputs, requested mode and scope. The specialist follows the skill; it must not infer complete-laydown permission from candidate work. Verify its outputs and summarize candidate deltas or complete laydown, actual checks, gaps and next decision. Keep complete-laydown requirements intact. Neither mode invokes preparation, readiness review, approval, admission, or start; admission and exit mechanics are unchanged. ## Timing-log required actions Contract: `control-plane/framework/governance/timing/timing-log.spec.md` section "Prompt Timing Contract". Record `proposal` or `complete-laydown` mode in invocation and terminal metadata; success describes the requested pass, never admission. Follow blocked/interrupted closure rules as applicable. - Open + invoke under `LC-HORIZON`, emitting `/shape-horizon-execution-invoked` with `--harness`, `--model-id`, Facilitator `--persona`, and `--invocation-source`. Record the delegated Planning persona in event metadata or the specialist's own evidence. - On terminal success emit `/shape-horizon-execution-complete --outcome success`, then close the timing session.

{ "prompt": "NEW-CONTEXT DISPATCH: after help handling, inspect the selected ID with\n`planning-capture.py inspect --root ROOT --id ID`. A resolved new-format capture uses\n[work shaping](../skills/work-plan-shaping/SKILL.md)'s new-context branch directly under the\ncurrent authorized caller, without mandatory delegation or old tracker laydown. Default is\npartial `draft --section work`; explicit `--complete` composes/proposes the complete result\nagainst supplied base/execution. Retain this command's timing and separate admission boundary.\nThis dispatch overrides only conflicting legacy rules below; actual legacy packets retain them.\nMissing/malformed new documents refuse; never synthesize an ADHOC identity for a horizon.\n\nINVOCATION CONTRACT: this prompt must be invoked from inside the `Control Plane: Lifecycle Facilitator` persona. The Facilitator resolves lifecycle context and invokes `Project: Planning and Design` as the bounded execution-laydown specialist. This workflow shapes proposed execution authority but does not admit the horizon.\n\nFor `--help`/`-h`, explain iterative default, complete laydown, outputs, verification and examples;\ndo not write or open timing. Examples: `/shape-horizon-execution H000`,\n`/shape-horizon-execution H000 Canon rework`, `/shape-horizon-execution H000 --exploratory`,\nand `/shape-horizon-execution H000 --complete`.\n\nInterpret `[HNNN] [scope] [--complete | --exploratory]`; refuse combined flags before writes.\nDefault to candidate work shaping. `--exploratory` is a compatibility alias for that default.\nLoad `.github/skills/work-plan-shaping/SKILL.md`, resolve the inception packet and shaping branch,\nthen delegate to `Project: Planning and Design` with the exact inputs, requested mode and scope.\nThe specialist follows the skill; it must not infer complete-laydown permission from candidate work.\n\nVerify its outputs and summarize candidate deltas or complete laydown, actual checks, gaps and\nnext decision. Keep complete-laydown requirements intact. Neither mode invokes preparation,\nreadiness review, approval, admission, or start; admission and exit mechanics are unchanged.\n\n## Timing-log required actions\n\nContract: `control-plane/framework/governance/timing/timing-log.spec.md` section \"Prompt Timing Contract\".\n\nRecord `proposal` or `complete-laydown` mode in invocation and terminal metadata; success describes\nthe requested pass, never admission. Follow blocked/interrupted closure rules as applicable.\n\n- Open + invoke under `LC-HORIZON`, emitting `/shape-horizon-execution-invoked` with `--harness`, `--model-id`, Facilitator `--persona`, and `--invocation-source`. Record the delegated Planning persona in event metadata or the specialist's own evidence.\n- On terminal success emit `/shape-horizon-execution-complete --outcome success`, then close the timing session.", "variables": [], "notes": "Iteratively shape proposed work through Planning and Design; request --complete explicitly for full Phase prompts and proposed tracker. Arguments: Optional HNNN and scope; --complete for full proposed laydown; --exploratory is a default-mode alias; or --help.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/rhodiusjeff/PokerNight", "path": ".github/prompts/shape-horizon-execution.prompt.md", "ref": "b26b33700e99f00c7edd1e46a0840c175f86aa90", "url": "https://github.com/rhodiusjeff/PokerNight/blob/b26b33700e99f00c7edd1e46a0840c175f86aa90/.github/prompts/shape-horizon-execution.prompt.md", "key": "rhodiusjeff/PokerNight/.github/prompts/shape-horizon-execution.prompt.md" } } }

Shape Horizon Execution

About

Timing-log required actions

Install Shape Horizon Execution and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews