hackersandwizards

Run the plan stage of the sdlc workflow

Run the report stage of the sdlc workflow

Run the tests stage of the sdlc workflow

Run the implement stage of the sdlc workflow

Run the simplify stage of the sdlc workflow

Run the review-claude stage of the sdlc workflow

Run the review-codex stage of the sdlc workflow

Run the converge stage of the sdlc workflow

Use after /refine — takes a bean that carries a `## Refined Plan`, creates a `feat/<bean-id>-<slug>` branch, walks each refined-plan step (edit → build → test → commit) with a hard build+test gate, and logs the commits back to the bean. Never pushes, never merges, never commits on `main`.

Use when starting a new feature — creates a new bean via beans CLI with description + High-Level Plan + AC. No code, no file paths.

Use after /planner — takes a bean that carries a `## High-Level Plan`, dispatches a read-only Explore subagent, and appends a `## Refined Plan` with real file paths, signatures, and a test sketch. Hand-off ready for /implement.

Use after /planner — takes a bean that carries a `## High-Level Plan`, dispatches a read-only Explore subagent, and appends a `## Refined Plan` with real file paths, signatures, and a test sketch. Hand-off ready for /implement.

Use after /refine — takes a bean that carries a `## Refined Plan`, creates a `feat/<bean-id>-<slug>` branch, walks each refined-plan step (edit → npm run build → npm test → commit) with a hard build+test gate, and logs the commits back to the bean. Never pushes, never merges, never commits on `main`.

Rephrase text in pirate language. Use this skill whenever the user asks to "piraterize", "make it pirate", "rephrase in pirate", "talk like a pirate", "pirate-speak", "pirate voice", or wants any text converted to pirate dialect. Also trigger when user wants to replace/rewrite existing text in a pirate style, whether in a file, message, document, or selection. Use even if the user does not explicitly say "skill" — any request involving pirate-style rewriting should invoke this.

Use when the user wants to plan a non-trivial change before writing code — refactor, migration, new feature, debugging strategy. Produces a written plan file, not implementation.

Use when starting a new feature — creates a new bean via beans CLI with description + High-Level Plan + AC. No code, no file paths.

Turn follow-up corrections to skill-generated work into minimal reusable skill improvements. Use after a user corrects, refines, or externally edits an output, or answers a question the skill should have resolved itself, to decide whether the owning skill should change and update it without encoding the specific case.

MUST be loaded before drafting, writing, composing, editing, or rewriting any human-readable prose that represents h&w or the user: emails, replies, Slack messages, WhatsApp and other personal messages, LinkedIn posts, proposals, quotes, talks, abstracts, speaker outreach, client comms, blog posts, articles, headlines, captions, slide decks, README copy, announcements, summaries, documentation prose, FAQs, surveys, notes for review. Skip only for code, code comments, command output, raw data, internal commit messages, log lines, and machine-readable config.

Full-repo quality pass. Sweeps every source file for comment hygiene and minimalism, reviews quality, performance, and security, runs /simplify and /code-review high on the resulting diff, then commits and pushes. Run when the user asks to polish, clean up, or quality-pass the repo.

Scaffold one stage of a multi-step pipeline: a per-stage subagent (with a SubagentStop gate), a manual launcher skill, and a dynamic-workflow script that orchestrates the stages deterministically. Run once per step you want to add.

Run a dynamic workflow on a real input, observe it without flooding context, verify its assumptions (gates fire, structured returns thread and branch, parallel stages overlap), then turn what you learn into edits to the workflow, its agents and skills, and the build-pipeline generator that produced it. Use after generating or changing a pipeline, or to dogfood and harden any Claude Code dynamic workflow.

Use when the user wants to plan a non-trivial change before writing code — refactor, migration, new feature, debugging strategy. Produces a written plan file, not implementation.