Skip to content

stbenjam/stevestack

v0.1.0

Steve's workflow for shipping code: brainstorming, model panels, design docs, working principles, deep review, PR shepherding, diagrams, and Git and test hygiene.

ask-me

Brainstorm an unsettled idea together, one question at a time.

braintrust

Convene a mini or mega panel of different models on a design, codebase or decision, and lead with the findings only one panelist raised. Use when the user asks for a braintrust, panel, council, mini-panel or mega-panel, or wants several independent opinions.

deep-review

Use when a deeper level of code review is requested. Multi-agent panel code review with specialist reviewers and forced runtime reproducers for all BLOCKING bug findings. Optionally posts to GitHub/GitLab as a PENDING review.

design-doc

Write a short, accurate design doc in Google Docs with diagrams. Use when asked to write or update a design doc.

diagrams

Draw minimal monospace box diagrams (architecture, trust boundaries, data flow, sequence of steps) for a design doc, RFC, README or slide, rendered to a light-and-dark SVG plus PNGs from hand-placed coordinates with the bundled Python script. Use whenever a document needs a diagram and the ask is for a clean, high-level picture rather than an auto-laid-out graph.

git-rules

Use this skill for critical Git rules whenever working with Git, especially before committing, pushing, rebasing, comparing branches, or preparing a pull request.

land

Authorize merging the current PR yourself once it meets the bar.

pr-loop

Shepherd a PR: merge base branch, fix CI, address review comments, resolve threads, and monitor until merged. Use when asked to drive a pull request through to merge.

principles

stbenjam's working principles. Use before making, reviewing, or shipping a change.

ship

Take work from any stage to an open, deep-reviewed PR.

test-failures

Use this skill whenever any test fails. Follow the required investigation process before deciding whether a failure is pre-existing or what to fix.