메뉴
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.
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.
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.
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 | deliver |
| description | 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. |
| argument-hint | [task|context-packet] |
Deliver one coherent public-safe change. In this repo, merge-ready means the change strengthens a named lifecycle stage, respects module boundaries, and has evidence for the current manual gate.
/code-review against public-safe, lifecycle, and profile semantics.
When using the triad, this is the critic step; blocking critique loops back
to planning or execution before proceeding./ci for the current gate./qa for changed artifact inspection./demo when a reviewer needs a transcript, fixture, or walkthrough./refactor only to simplify the changed surface; do not broaden scope.Use the planner/executor/critic triad when the task changes a module contract, schema, profile, harness primitive, generated repo guidance, policy/context surface, or user-facing workflow. Skip it for tiny documentation fixes, mechanical moves, and one-command checks.
The planner packet must name the objective, non-goals, authority order, repo anchors, executor ownership boundary, and executable evidence. The executor must stay inside that boundary and report changed files. The critic must review cold against the packet and fail on missing evidence, unnecessary complexity, module-boundary drift, or unapproved scope growth. The lead agent/operator integrates the result and owns the final decision.
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.
Report changed files, lifecycle stage strengthened, evidence gathered, and remaining unverified paths.