From workshop
Use at the start of a "Build Your Idea" workshop build (4-hour scope). Runs the full superpowers pipeline (brainstorm → plan → execute → review → finish) with workshop-tuned extensions for product-design discipline, universal architecture rules, pragmatic testing, and frontend aesthetics.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workshop:workshop-pipelineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Single entry point for a 4-hour workshop build. Wraps the standard superpowers pipeline and injects workshop-specific rules at each stage. The phases stay visible so the participant learns the flow.
Single entry point for a 4-hour workshop build. Wraps the standard superpowers pipeline and injects workshop-specific rules at each stage. The phases stay visible so the participant learns the flow.
Trigger when ALL of:
Do NOT trigger on: continuing existing work, doc-only edits, or "fix this bug" requests in an existing workshop project.
Verify the following are installed before the pipeline starts. If any are missing, stop and tell the participant which /plugin install command to run.
superpowers (claude-plugins-official) — required, the pipeline wraps it.workshop-architecture — required, ships in the same plugin as this skill.frontend-design (claude-plugins-official) — required only for projects with a UI. START
│
▼
┌──────────────────────────────┐
│ superpowers:brainstorming │ ← Extension A (product-design overlay)
└──────────────────────────────┘
│ produces: spec doc
▼
┌──────────────────────────────┐
│ superpowers:writing-plans │ ← Extension B (workshop-architecture
│ │ auto-loaded at plan time)
└──────────────────────────────┘
│ produces: implementation plan
▼
┌──────────────────────────────────────┐
│ superpowers:subagent-driven- │ (default executor)
│ development │ ← Extensions G + H apply during exec
└──────────────────────────────────────┘
│ produces: committed code
▼
┌──────────────────────────────┐
│ superpowers:requesting- │ ← Extension D (workshop-tuned review)
│ code-review │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ Simplified finishing │ ← Extension F (replaces finishing-a-
│ (RECAP.md) │ development-branch)
└──────────────────────────────┘
Stage handoff: when one stage completes, immediately invoke the next (superpowers:brainstorming → superpowers:writing-plans → superpowers:subagent-driven-development → superpowers:requesting-code-review → Extension F). Do not wait for the participant unless a stage's own skill requires it.
Tag: v1 — revisit after dedicated product-design brainstorm
Apply during superpowers:brainstorming. Add these rules to the base brainstorming flow:
The spec produced by brainstorming MUST contain: user, pain, the-one-thing sentence, 4h-scoped feature list, "why not existing tool" answer, and (if UI) the aesthetic intent line.
Apply during superpowers:writing-plans. Before writing any task in the plan, you MUST:
skills/workshop-architecture/references/backend.md and/or skills/workshop-architecture/references/frontend.md accordingly. (These ship in the same plugin as this skill.)If the spec reveals a situational trigger listed in workshop-architecture/SKILL.md (plugin system, RBAC, audit, streaming, etc.), STOP and ask the participant how to proceed. Do NOT silently invent the pattern.
Apply during superpowers:requesting-code-review. The review checklist is the 25 universal rules from workshop-architecture.
REPLACES superpowers:finishing-a-development-branch. Do NOT invoke that skill. Instead, produce a recap at the workshop project root.
Create RECAP.md with these five sections:
workshop-architecture rules that shaped the build.No git push, no PR, no branch cleanup.
Apply throughout execution and review.
Interaction with superpowers:test-driven-development: the TDD skill is still invoked, but its iron law ("no production code without a failing test first") is scoped to the core value path. For auxiliary code, TDD is recommended, not enforced.
Apply to any project with a UI.
frontend-design. Before the first UI component is implemented, invoke the frontend-design skill (claude-plugins-official) with the spec's aesthetic intent as input. Commit to a direction: typography, color, motion, spatial composition.frontend-design must be installed (see Pre-reqs above).Interaction with workshop-architecture/frontend.md:
workshop-architecture/frontend.md controls structure (data direction, component tiers, state homes, error boundaries, types).frontend-design controls aesthetics (typography, color, motion, layout).For participants who finish early and want to see autonomous execution: install Ralph from https://github.com/snarktank/ralph, convert your spec to a prd.json via Ralph's /ralph skill, and run ralph.sh to watch a fresh Claude instance grind through stories autonomously. Out of scope for the main pipeline — recommend it in Extension F's "next steps" only.
Do NOT:
superpowers:finishing-a-development-branch (Extension F replaces it).npx claudepluginhub vladchs/workshop-skills --plugin workshopCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.