scry

Final mile for scry. Land a merge-ready backlog branch, archive the shipped backlog files into backlog.d/_done/ before squash, preserve backlog trailers in the squash commit, pull master, invoke /reflect, and route any reflect harness edits to harness/reflect-outputs. Assumes /settle already proved the branch merge-ready against scry's Quality Checks merge-gate; /ship does not refactor, review, or run a fresh CI campaign. Use when: "ship it", "merge and close out", "land this scry ticket", "finish this backlog item", "merge and reflect". Trigger: /ship.

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.

Run and repair scry's actual quality gates. The ship gate is GitHub Actions Quality Checks merge-gate, with pnpm local parity and Lefthook as defense in depth. This repo does not use Dagger; never scaffold it or describe it as canonical here. Bounded self-heal may fix lint, formatting, stale generated artifacts, and obvious focus markers, but must not lower coverage, weaken TypeScript, disable tests, or bypass audit. Use when: "run ci", "check ci", "fix ci", "audit ci", "is ci passing", "run the gates", "why is ci failing", "strengthen ci", "tighten ci", "ci is red", "gates failing". Trigger: /ci, /gates.

Parallel multi-agent code review for scry. Launch reviewer team, synthesize findings, auto-fix blocking issues, loop until clean. Use when: "review this", "code review", "is this ready to ship", "check this code", "review my changes". Trigger: /code-review, /review, /critique.

Safe Convex schema/data migrations in scry, including schema removals, dry-runs, diagnostics, target verification, and production approval gates.

scry inner-loop composer. Takes one file-driven backlog item from backlog.d/ to merge-ready code by composing /shape -> /implement -> {/code-review + /ci + /refactor + /qa as applicable}. Stops at merge-ready. Does not push, merge, deploy, archive backlog tickets, or inject backlog-closing trailers; /ship owns closure. Use when: building one shaped backlog item, "deliver this", "make it merge-ready", driving one scry ticket through implementation, review, verification, and evidence. Trigger: /deliver.

Deploy scry to its real production surface: Convex backend first, validation second, Vercel frontend last. This skill is approval-gated for every command that can mutate non-local Convex or Vercel state. It stops at a healthy deploy receipt and hands ongoing observation to /monitor. Use when: "deploy scry", "ship to production", "release", "run the production deploy", "deploy this merged ref". Trigger: /deploy, /ship-it, /release.

scry-specific diagnosis for bugs, test failures, production incidents, Sentry/Vercel/Convex triage, Langfuse cost or quality anomalies, prompt eval regressions, and durable issue logging. Reproduce first, prove root cause, then fix and verify against the scry gate. Use for: "diagnose", "debug", "why is this broken", "production down", "is production ok", "Sentry issue", "Convex deploy failed", "migration failed", "generation quality dropped", "cost spike", "prompt eval failed", "audit", "triage", "log issues". Trigger: /diagnose.

scry outer-loop shipping orchestrator. Picks the next backlog item, composes /shape, /implement, /yeet, /settle, /ship, and /monitor, then loops. Closure (backlog archive, trailers, /reflect, and harness routing) lives in /ship; flywheel does not invoke /reflect directly. Use when: "flywheel", "run the outer loop", "next N items", "overnight queue", "cycle". Trigger: /flywheel.

Always-on backlog grooming. Tidy, brainstorm, interrogate, investigate, research, and simplify in a single loop. Tidy is not a mode — it happens every time. Strategic-layer work fans out parallel subagents: /office-hours on raw items, /ceo-review on shaped packets, a technical-review bench on code hotspots, /research for external context. Use when: "groom", "what should we build", "rethink this", "biggest opportunity", "backlog", "prioritize", "backlog session". Trigger: /groom, /backlog, /rethink, /moonshot, /scaffold.

Atomic TDD build skill. Takes a context packet (shaped ticket) and produces code + tests on a feature branch. Red → Green → Refactor. Does not shape, review, QA, or ship — single concern: spec to green tests. Use when: "implement this spec", "build this", "TDD this", "code this up", "write the code for this ticket", after /shape has produced a context packet. Trigger: /implement, /build (alias).

Scry post-deploy signal watch. Observe health, Sentry, Vercel, Convex, Langfuse, prompt eval, and Playwright surfaces through a bounded grace window. File crisp alerts, then hand incidents to /diagnose. Watcher, not fixer. Use when: "monitor signals", "watch the deploy", "is the deploy ok", "post-deploy watch", "watch production", "check Scry after deploy". Trigger: /monitor.

YC-partner-style interrogation of a raw idea. Six forcing questions before you shape anything: demand reality, status quo, desperate specificity, narrowest wedge, observation & surprise, future-fit. Named for Gary Tan's office-hours pattern; operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the ideation stage — problem-diamond, pre-/shape. Use when: user arrives with a rough idea, backlog item is fuzzy, you can't already write a one-sentence goal with a testable outcome, or the phrase "what should we build" would be useful. Trigger: /office-hours, /oh, /interrogate.

Scry browser QA, exploratory testing, smoke verification, dogfood evidence, and merge-readiness handoff. Drive the real Next.js/Convex/Clerk app and verify the spaced-repetition UX, not just green test output. Use when: "run QA", "test this", "verify the feature", "exploratory test", "check the app", "QA this PR", "capture evidence", "manual testing", "dogfood scry". Trigger: /qa.

Branch-aware simplification workflow for scry. Use it to delete dead surface area, extract the four known monoliths into agent-ready modules, or rationalize root topology without changing product behavior or public Convex APIs. Use when: "refactor this", "simplify this diff", "clean this up", "reduce complexity", "pay down tech debt", "make this easier to maintain", "extract this safely", "split the review chat", "split concepts", "split aiGeneration", "split iqc". Trigger: /refactor.

Session retrospective, operator coaching, harness postmortem, codification, and outer-loop cycle critique. Distills learnings into hooks/rules/skills, mutates the backlog from evidence, and emits harness-tuning suggestions to a branch. Learning engine of the outer loop. Use when: "done", "wrap up", "what did we learn", "retro", "reflect", "calibrate", "how could I have asked better", "prompt better", "teach me from this session", "what should I learn from this", "reflect on cycle", "cycle postmortem", post-/flywheel critique. Trigger: /reflect, /retro, /calibrate, /reflect cycle <cycle-ulid>.

Scry-tailored web research, repo evidence gathering, multi-AI delegation, and multi-perspective validation. /research [query], /research delegate [task], /research thinktank [topic]. Triggers: "search for", "look up", "research", "delegate", "get perspectives", "web search", "find out", "investigate", "introspect", "session analysis", "check readwise", "saved articles", "reading list", "highlights", "what are people saying", "X search", "social sentiment", "trending".

scry polish loop. Take a feature branch with code and tests and iterate CI -> code-review -> refactor -> QA until the branch is lean, green, and merge-ready under scry's GitHub Actions merge-gate and local parity checks. Stops at merge-ready. Does not merge. Does not archive backlog tickets. Hands off to /ship, never /land. Use when: "polish this", "get this merge-ready", "unblock", "clean up", "address reviews", "fix CI", "make this shippable". Trigger: /settle, /pr-fix, /pr-polish.

Shape a raw idea into something buildable. Product + technical exploration. Spec, design, critique, plan. Output is a context packet. Use when: "shape this", "write a spec", "design this feature", "plan this", "spec out", "context packet", "technical design". Trigger: /shape, /spec, /plan, /cp.

End-to-end "commit this scry work and push it" command. Reads the dirty worktree without trampling other workers, filters scaffold/harness drift, runs the scry ship gate, slices owned work into conventional commits, and pushes the current branch when safe. Use when: "yeet", "yeet this", "commit and push", "ship it", "tidy and commit", "wrap this up and push", "get this off my machine". Trigger: /yeet, /ship-local (alias).