dev-bootcamp-factory-workshop

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.