メニュー
Assess Gradient's readiness for governed agent work across docs, schemas, profiles, harness, validation, evidence, and public-safe boundaries. Trigger: /agent-readiness, /readiness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Maintain Gradient's repo-local agent harness: skills, agents, settings, repo brief, and gate-aligned instructions. Trigger: /harness, /skill, /primitive.
Take one shaped Gradient docs/schema/profile task to merge-ready. Composes /shape, /implement, /code-review, /ci, /qa, /demo, and /refactor as needed. Stops before merge. Trigger: /deliver.
Dialectical premise-and-alternatives audit for a plan, spec, or context packet. Four moves: premise challenge (is this the right problem?), mandatory structurally-distinct alternatives, cross-model outside voice, user-ratified convergence. Named for Gary Tan's plan-ceo-review pattern; operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the plan-review stage. Use when: about to commit to a plan/spec/design, reviewing a ticket before shape, when "is this the right problem" would be useful, or any time a proposal smells like a symptom fix instead of a root-cause fix. Trigger: /ceo-review, /challenge, /premise-check.
Gradient gate audit and validation workflow. Use when checking whether a docs/profile/schema change is safe to ship in this scaffold. Trigger: /ci.
Review Gradient docs, profiles, schemas, and harness changes for public-safe boundaries, lifecycle consistency, and contract depth. Trigger: /code-review, /review, /critique.
Produce evidence that a Gradient docs/schema/profile change is understandable and reviewable. For this repo, demos are validation transcripts, synthetic fixtures, before/after contract walkthroughs, or release-note blurbs. Trigger: /demo.
| name | agent-readiness |
| description | Assess Gradient's readiness for governed agent work across docs, schemas, profiles, harness, validation, evidence, and public-safe boundaries. Trigger: /agent-readiness, /readiness. |
| argument-hint | [--assess-only] [--fix] |
Readiness here is not framework setup. It is whether agents can safely move Gradient work from intent to evidence without leaking private context or making unsupported claims.
Strong: architecture docs, decision log, profile examples, public-safe rules.
Weak: no automated gate, no evidence packet schema, no local Work adapter, no Fleet run schema, no Context packet schema, no backlog lifecycle detector.
The load-bearing ship gate is ./scripts/validate.sh, plus reviewer
judgment for lifecycle semantics in docs/architecture.md and
docs/module-contracts.md when docs change.
Score each pillar, name the highest-impact fix, and implement it only when the scope is bounded and public-safe.
