メニュー
Enforces Gantry planning and handoff discipline for meaningful feature, fix, refactor, or replacement work. Use when a task needs a plan, Surface Impact Matrix, no-legacy cleanup evidence, verification selection, or PR-ready handoff.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate a Gantry plan to a finished PR — Claude writes a goal-prompt doc, delegates implementation stages to the Codex plugin (xhigh + ponytail), verifies and commits between stages, and closes with the autoreview loop. Use when the user asks to implement a plan/goal prompt, "run the goal pipeline", "same as the goal", or hands over a docs/architecture/*-goal-prompt.md to execute.
End-to-end Gantry plan implementation pipeline. Use when the user asks to implement or pursue a plan, goal prompt, feature, fix, refactor, PR update, or "same as the goal" workflow with subagent implementation, ponytail simplicity, no-commentary implementation, autoreview, build, launchctl restart, Knacklabs lead gen smoke, and PR/pipeline closeout.
Gantry self-administration reference for current host runtime operations: CLI commands, settings.yaml runtime settings, .env credential keys, agent management, scheduler tools, memory tools, browser tools, diagnostics, and service control. Use when asked to manage Gantry itself.
Guides Gantry tool, skill, MCP server, browser, local CLI, semantic capability, inventory, and permission lifecycle work. Use when changing durable capability selection, visible attached sources, transient request_permission flows, or agent access review paths.
Drives Gantry agent-chat tests through the local Control API session path and captures assistant responses. Use when testing an agent response, permission prompt, skill behavior, or runtime chat flow without needing Telegram UI rendering.
Use when creating or revising a Gantry product, UX, permission, job, ingress, provider, settings, or agent-flow plan that must be decision-complete with no room for assumptions. Triggers for PM plan, product manager plan, no assumptions, UX flow, user flow, agent flow, acceptance criteria, validation plan, provider-neutral plan, or Surface Impact Matrix.
| name | gantry-change-contract |
| description | Enforces Gantry planning and handoff discipline for meaningful feature, fix, refactor, or replacement work. Use when a task needs a plan, Surface Impact Matrix, no-legacy cleanup evidence, verification selection, or PR-ready handoff. |
Use this skill before implementation when a change affects runtime behavior, configuration, persistence, APIs, CLI, MCP/admin tools, docs/prompts, audit events, or tests.
WORKFLOW.md, docs/FACTORY.md, docs/QUALITY.md, and docs/architecture/current-verification-commands.md.settings.yaml, Postgres/runtime projection, control API, SDK/contracts, CLI, Gantry MCP tools/admin skill, channel/provider adapters, docs/prompts, audit/events, and tests/verification.Changed, Read-only/observable, Unchanged by design, Deferred, or Not applicable.Deferred and Unchanged by design entry.docs/architecture/current-verification-commands.md, then run broader gates when the surface or risk requires them.