phahadek

deploy

Deploy a managed project to production, executed strictly from that project's structured deploy playbook — confirm-gated, never improvised. Use when the user says "deploy", "deploy <project>", "ship <project> to prod", "run the deploy", or "push <project> live". Reads the project's context.md + the deploy playbook it points to (e.g. a repo README "Deploy" section), presents the full ordered plan, then runs it one step at a time, pausing before each production-mutating step.

Web & Frontend Listed

design

Run a Design Execution session for a milestone. Loads full project context deterministically (via design-load.mjs), investigates the open questions in each Ready / In-Progress 📐 Design and 📋 Planning task, proposes a thematic execution order for human sign-off, then walks each task one open-question at a time — debating trade-offs, locking decisions, updating architecture pages, and filing follow-on 🔲 Backlog Code tasks. Use when the user says "design", "design session", "let's run a design session for milestone X", "execute the design tasks", or starts a Design Execution session. Requires a grooming manifest in the central config tree (config/projects/<dir>/grooming.json), shared with the /groom skill.

wrap

Wrap up a session: scan it for durable information that was produced or decided but never persisted to its proper home, surface each item with a proposed home, and — on your confirmation — write it there. Use when the user says "wrap", "wrap up", "wrap the session", "let's close out", or before ending a long working session. Nothing important should die with the session.

gate

Run the Manual Verification Gate for a milestone against the gate-state API (readiness �� pull runnable items by tier → human disposition → record). Use when the user says "run the gate", "gate check", "verify the gate for milestone X", or starts a Manual Verification Gate pass. Requires the gate-verification service's gate_item / gate_item_event tables and the backend's /api/gate/* routes to be live for the target milestone.

groom

Run a Backlog Grooming session for a milestone. Loads full project context deterministically (via the backend's GET /api/groom-context route), explores the code regions tasks touch with a git-fresh cache, presents 🔲 Backlog tasks in batches for human sign-off, and marks them 🗂️ Ready. Use when the user says "groom", "grooming session", "let's groom milestone X", "bring the backlog to Ready", or starts a Backlog Grooming session. Requires a grooming manifest in the central config tree (config/projects/<dir>/grooming.json).

ops

Execute a milestone's interactive 🔧 Operational and 🔎 Investigation tasks — the judgment-bound work that is NOT auto-dispatched. Two modes in one pass: Operational changes production/environment state through a sanctioned surface (config/catalog/entity authoring, backfills, alarm config, dependency installs, session/machine setup); Investigation produces a defensible decision from live data (diagnoses, spikes, zero/anomaly triage) and files follow-on tasks. Enforces: autonomous runs STAGE (never verdicts, never ✅ Done), read-only diagnosis before any write, falsify every "it's fine", audited read-modify-write, reconcile+capture, "Done ≠ deployed ≠ seeded ≠ working". Records durable research to a staging journal. Use when the user says "work the ops tasks", "run ops/tooling for milestone X", "work the operational/investigation tasks", or starts an overnight or interactive ops run on a project's task board.

Code & Development Listed

sync-guidelines

Re-vendor EVERYTHING this repo deploys into a live tree — the universal guideline docs (task-writing.md, procedures.md), the /groom /design /ops /deploy /wrap /sync-guidelines /gate skill directories, the sanctioned route-client scripts, and the config-tree hook — via a Claude-led three-way merge, never a file overwrite. The repo copy is the upstream source; the live copy may carry local edits (a vendored skill refined in place, an emergency script hotfix) that must be preserved. Use when the user says "sync guidelines", "re-vendor the skills", "deploy the grooming skills", "integrate the guideline updates", "pull the procedures/task-writing changes into config", or after merging a PR that changed config-template/, skills/**, scripts/*.mjs, or packages/backend/scripts/*.mjs.

Web & Frontend Listed

docs

Run an interactive Docs authoring session for a single 📝 Docs task: load the task, read its declared Source domain(s) live over the web, author into its declared Target surface (a repo file or a Notion page), and open the never-auto-merge output (a draft PR for a repo-file target, or a staged notion.pageEdit intent for a Notion-page target) for a human to review and merge/apply. Use when the user says "docs", "docs session", "run the docs task", "write the docs for X", or starts an interactive Docs-authoring session on a 📝 Docs task. Requires the task to declare a Target surface and Source domain(s) in its body (see § Docs task-body convention below) — do not improvise either.

milestone-wrap

Close out a completed milestone: confirm all its tasks are terminal and the Manual Verification Gate is green, mark the milestone done + the next one active across every place that tracks it, advance main to dev, and cut the release tag. Use when the user says "wrap up milestone X", "close M11", "let's close out the milestone", or "cut the release for milestone X". A confirm-gated procedure, never improvised — pauses before the outward-facing tag/release. Distinct from /wrap (which closes a SESSION, not a milestone).

investigate

Operator-driven, live-symptom investigation: turn a reported issue into well-formed 🔲 Backlog tasks grounded in the live operational record, not memory. The upstream of /groom — grooming brings Backlog to Ready; this produces the grounded Backlog. Read-only diagnosis by default, with a spelled-out ladder for operator-authorized in-session mutations: pull a live-health snapshot (true deployed SHA, active milestone, errored + idle/killed planning sessions, failed deploys, GitHub-verified needs-attention PRs, the active board), reconstruct the symptom by value, root-cause to file:line under an evidence law that matches each claim shape to its admissible proof, frame (caused-vs-exposed, transient-vs-systemic, cascade/blast-radius, re-verify deployed state), classify (Code-vs-Design, check ✅ Done designs, recognize subsumption), then draft and file 🔲 Backlog tasks with SHA-stamped file:line anchors + 🤖/👁️ acceptance. Use when the operator says "investigate X", "look into why Y", "something's wrong with Z — dig

milestone-seed

Stand up a NEW milestone: ground in the prior milestone's real state and the live dispatch switches, audit the Future Scope deferral list, frame and lock a charter with the operator, create the milestone board, and seed it with decision-shaped 📐 Design (and 🔎 Investigation) tasks grounded in real code. Use when the user says "let's start planning milestone X", "seed milestone X", "let's seed M15", or opens a session to stand up the next milestone. Ends with the board SEEDED AND REGISTERED (a `milestones` row + grooming-manifest entry) but NOT ACTIVATED — that belongs to /milestone-wrap. Distinct from /groom and /design, which work an EXISTING milestone's backlog.