メニュー
Investigate failures in Gradient contracts, docs, schemas, profiles, harness wiring, and future validation commands. Trigger: /diagnose.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | diagnose |
| description | Investigate failures in Gradient contracts, docs, schemas, profiles, harness wiring, and future validation commands. Trigger: /diagnose. |
| argument-hint | <symptom or failing artifact> |
Diagnose Gradient as a contract scaffold, not as an application. The likely failure is a contradiction between docs, schemas, profiles, examples, and the public-safe boundary.
docs/architecture.mddocs/module-contracts.mddocs/decision-log.mdprofiles/*.yamlschemas/gradient.schema.jsonThe 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.
Diagnosis must not imply CI, tests, or deploy verification exist in this repo. Name those paths as absent or unverified when they matter.
Return root cause, affected lifecycle stage, evidence, fix, and any residual unverified path.
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.
Assess Gradient's readiness for governed agent work across docs, schemas, profiles, harness, validation, evidence, and public-safe boundaries. Trigger: /agent-readiness, /readiness.
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.