From superpowers-plus
Orchestrates the full development lifecycle for code changes: brainstorming, design, review, implementation, testing, commit. Default workflow that runs automatically unless opted out.
How this skill is triggered — by the user, by Claude, or both
Slash command
/superpowers-plus:feature-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Wrong skill?** Bug fix → `systematic-debugging`. Design comparison → `debate`. Pre-commit checks → `pre-commit-gate`. Workflow
Wrong skill? Bug fix →
systematic-debugging. Design comparison →debate. Pre-commit checks →pre-commit-gate. WorkflowPurpose: Orchestrate the full rigorous development lifecycle so no phase is skipped. Pattern: This skill SEQUENCES existing skills — it does not replace them. Scope: This is the DEFAULT workflow for ANY code change. Opt out ONLY if the user explicitly says to skip it.
Announce at start: "I'm using the feature-development skill to orchestrate this workflow."
Phase 1: BRAINSTORM → Phase 2: FRESH PERSPECTIVE → Phase 3: DESIGN →
Phase 4: HARSH REVIEW → Phase 5: PLAN & EXECUTE → Phase 6: HARSH REVIEW →
Phase 7: SHIP
Each phase has an exit gate — you cannot proceed until the gate passes.
Invoke: brainstorming
Invoke: think-twice
Invoke: debate
Invoke: progressive-code-review-gate
Invoke: plan-and-execute
todo-management / todo-crud.sh, then mirror to MCP tasksadversarial-searchoutput-verification after generating any artifactInvoke: progressive-code-review-gate
output-verification — read back all generated filesverification-before-completion — evidence before assertionsYou MUST NOT skip phases. "I already know the approach" → think-twice catches blind spots. "Only one design option" → debate requires ≥3. "Too small" → the 2026-03-27 incident was "just a small script."
Opt-out is user-initiated ONLY. The agent never decides to skip.
| Phase | Skill Invoked | Purpose |
|---|---|---|
| Brainstorm | brainstorming | Explore intent, gather context, surface assumptions |
| Fresh Perspective | think-twice | Sub-agent catches blind spots |
| Design | debate | ≥3 options, comparison, selection |
| Harsh Review (Design) | progressive-code-review-gate | Red-team the design |
| Plan & Execute | plan-and-execute + adversarial-search | Structured implementation with self-review |
| Harsh Review (Impl) | progressive-code-review-gate | Red-team the implementation (min 2 rounds) |
| Ship | output-verification, verification-before-completion | Inspect output, verify completion, merge |
2026-03-27: Agent skipped brainstorming, think-twice, and harsh review. Confabulated summary without reading output. Required 2 hostile review rounds. Every issue would have been caught by the full workflow.
# Pre-flight: verify branch, tests pass, no uncommitted changes
git status --short && npm test 2>&1 | tail -5
# Post-implementation: run full test suite + lint
npm run lint && npm test
| Failure | Recovery |
|---|---|
| Phase skipping (most common) | Every phase has an exit gate. No phase can be skipped without user opt-out. |
| Rushing through brainstorming in <2 exchanges | Brainstorming should explore ≥3 approaches with real trade-offs |
| Skipping harsh review after implementation | Phase 6 is mandatory. Fixes from review need their own review. |
| Not persisting phase state via TODO | Each phase must be enrolled as a TODO before starting |
npx claudepluginhub bordenet/superpowers-plus --plugin superpowers-plusGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.