zwrose

zwrose

@zwrose

GitHub
18 Skills
18 Total Stars
November 2026 Joined

Public Skills

showrunner

by zwrose

Use to run the long-lived advisor session for a superheroes project — the Showrunner — "be the advisor", "vet this PR", "route this issue", "what should we build next". It routes incoming work to one of four routes (discovery, detective, build-ready, micro), vets every PR from its artifacts against the issue/spec and the build brief, and coordinates releases. Not the builder (that is workhorse); not spec elicitation (discovery); not code review (review-code).

Code Review 1 8d ago

review-code

by zwrose

Use when reviewing code changes on a local branch or an open pull request before merging — including when you want the review's findings auto-fixed locally. Gives a multi-specialist review with a fix-and-re-review loop. Not a whole-repo debt sweep (that is guardian).

CLI Tools 1 10d ago

adopt-version

by zwrose

"Use in a live showrunner, workhorse, or detective seat after a newer superheroes version is installed — adopt it in place, no handoff and resume. Diffs the versions, re-reads what changed, runs TRANSITION's checklist, and briefs the owner. Not checkpoint or resume."

Code Review 1 11d ago

workhorse

by zwrose

Use to run the build — "build this issue", "run the builder". Workhorse is the entry point that takes a routed issue all the way to a ready PR; work still needing discovery or diagnosis is routed back, never elicited in-session. Full lane delegates all implementation to tiered subagents or engines under a shared contract; light lane — you type, one independent review. It independently re-runs every receipt they claim. Never merges or releases. Not advising the project (that is showrunner).

CLI Tools 1 11d ago

detective

by zwrose

"Use when a failure needs its cause demonstrated before a fix is scoped (why did this break, diagnose this, a first fix that already failed, or one symptom on more than one surface). Observe-only diagnosis by reproduction or A/B on disposable copies, delivering a diagnosis receipt for the advisor to vet. It never edits the surface under diagnosis and never produces a fix. Not the builder (that is workhorse)."

Comments 1 14d ago

review-init

by zwrose

"Internal helper reached from superheroes:configure to refresh review-crew's calibration layer for a project. Not a front door; owners run superheroes:configure instead."

Code Gen 1 17d ago

architect-init

by zwrose

"Internal helper reached from superheroes:configure to refresh the-architect's doc-policy layer (where definition-docs live). Not a front door; owners run superheroes:configure instead."

CLI Tools 1 20d ago

showrunner-resume

by zwrose

"First action in a new, restarted, or compacted showrunner advisor seat — no arguments; with or without handoff. Reads durable state only and brings every lane back under watch. Not checkpoint or handoff."

Automation 1 28d ago

guardian

by zwrose

Use to run the Guardian sweep — a periodic read-only sweep of repo health (duplication, complexity, coupling, dependency and doc freshness, dead code). Reports maintainability drift since the last sweep as plain-language consequences; it never edits code or files issues. Not code review of a change (that is review-code).

Code Review 1 1mo ago

checkpoint

by zwrose

"Use before compaction in a showrunner, workhorse, or detective charter session, a discovery session, or any session with no charter — freshen live state and emit a ready-to-paste /compact command, and save the checkpoint notes. /compact is not reachable from a skill; one paste is the floor on hosts without mods. Not configure, review, or discovery work itself."

CLI Tools 1 1mo ago

configure

by zwrose

"Use to set up, fix, view, or tune a project's superheroes calibration — the single front door for superheroes configuration. Lets you see the whole project's calibration on one screen, change a setting, or move a project between in-repo and out-of-repo storage. Not for code review, technical planning, or running the build loop."

CLI Tools 1 1mo ago

discuss-open-decisions

by zwrose

"Use when the owner needs to rule on open decisions — asking what is waiting on them, returning from time away, or when undelivered calls have piled up. Sweeps the standing-proposals collector, open parks, and in-session pending items and delivers batch 1 (decisions blocking the advisor, never new-issue filings) as numbered chat prose. Not routing, vetting, or building."

Code Review 1 1mo ago

test-pilot-init

by zwrose

"Internal helper reached from superheroes:configure to refresh test-pilot's profile, seeding blocks, and browser tooling layer. Not a front door; owners run superheroes:configure instead."

CLI Tools 1 1mo ago

showrunner-handoff

by zwrose

"Use in the showrunner advisor seat you are leaving while it is still alive — deliberate handover before the seat goes dark. Leaves durable state for the incoming seat. Emits no paste block. Not checkpoint (/compact); not showrunner-resume (incoming seat)."

Auth 1 1mo ago

test-pilot-execute

by zwrose

Use when a test-pilot plan should be exercised before human spot-check — "run the test plan", "pilot this PR", "verify the branch in the browser". Drives the app via a browser MCP, or the lane's simulated iPhone, and posts a results comment. Observe-and-report only — a bug it finds is a finding, never an edit.

Code Review 1 1mo ago

discovery

by zwrose

Use at the START of any new piece of work in a superheroes project — when a fuzzy idea needs to become an owner-approved requirements spec. It OWNS the requirements front-half, the what in plain language. Elicits requirements (incl. significant unhappy paths) with the owner into the spec definition-doc. Not the technical how (that is the build).

Code Review 1 1mo ago

writing-specs

by zwrose

Use to author the on-disk spec definition-doc once an owner has APPROVED a set of requirements, normally from the discovery skill. Mints the work-item slug and writes the self-reviewed spec. Does NOT elicit requirements (that is discovery) or design the technical approach (that is the build).

Design 1 1mo ago

test-pilot-plan

by zwrose

Use when a PR/branch needs a manual test plan with seeded data — "write a test plan", "seed test data for this PR", "set up manual testing". Seeds scenarios via the test-pilot engine and posts a checkbox plan to the PR. Does NOT execute the plan (that is test-pilot-execute).

Comments 1 1mo ago