القائمة
Outer-loop Gradient work cycle. Pick, shape, implement, settle, ship, monitor, and feed learnings back into docs, schemas, profiles, or harness. Trigger: /flywheel.
التثبيت باستخدام 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.
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.
| name | flywheel |
| description | Outer-loop Gradient work cycle. Pick, shape, implement, settle, ship, monitor, and feed learnings back into docs, schemas, profiles, or harness. Trigger: /flywheel. |
| argument-hint | [--max-cycles N] |
Use /flywheel when running repeated Gradient improvement cycles. This repo has
no backlog runner yet, so the cycle starts from an explicit user request or a
tracked docs/schema debt item.
This repo now has backlog.d as the Work adapter v0, but no closure
detector beyond the tracer-bullet fixture. Until a detector exists, preserve
work references manually and mark closure mechanics unverified.
pick -> /shape -> /implement -> /yeet -> /settle -> /ship -> /monitor -> loop
/ship owns final closure and reflection. /flywheel consumes the result; it
does not archive tickets or invoke /reflect directly.
master only after evidence is recorded.The tracker and closure detector gap is P0 harness/product debt because it
prevents /ship, /groom, /settle, /flywheel, and /implement from
mechanically proving work closure.