PWDEV Power — Disciplined Spec-Driven Development

Plugin pwdev-power from marketplace pwdev-claude-marketplace in pwdev-solucoes/pwdev-claude-marketplace. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• power-brainstorm

  Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation

• power-debug

  Use when encountering any bug, test failure, or unexpected behavior, before proposing any fix

• power-execute

  Use when an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks

• power-finish

  Use when implementation is complete, tests pass, and the work needs integrating - merging, opening a pull request, or being left in place

• power-fleet

  Use when approved phases should run in parallel — visually in a cmux panel or unattended — when fleet status is requested, or when a fleet member must be stopped or merged

• power-init

  Use when a repository has no PWDEV Power workspace yet, when resuming one, when the codebase map needs refreshing, or when the setup should be checked

• power-plan

  Use when a design or set of requirements exists and work needs decomposing into tasks, before touching any code

• power-product

  Use when a product requirement, PRD, or executable roadmap is requested, or when an approved requirement needs decomposing into phases, epics, features and tasks

• power-quick

  Use when a change is small and already understood - at most three files, such as a typo, a config value, a rename, or a one-line bugfix - and a plan file would cost more than the change

• power-review

  Use when work needs reviewing before it is merged, and when review feedback has arrived and needs acting on

• power-roadmap-status

  Use when the status, progress, completeness, traceability, or next valid action of a PWDEV Power product roadmap is requested

• power-skill-refactor

  Use when an existing skill must be refactored to cut context and ambiguity without losing behavior, safety or fallbacks — 'refatorar a skill', 'reduzir esta SKILL.md', 'revisar skill com métricas' — with before/after metrics, preserved invariants and three review rounds.

• power-tdd

  Use when implementing any feature or fixing any bug, before writing implementation code

• power-verify

  Use when about to claim work is complete, fixed, or passing, and when a finished feature needs adversarial verification before integration

• power-worktree

  Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan

• power

  Use when starting any conversation in a repository that uses PWDEV Power - establishes how to find and apply Power skills before any response, including clarifying questions

Slash commands (7)

• /pwdev-power:exec

  Execute an approved plan task by task, with a durable ledger and review between tasks

• /pwdev-power:fleet

  Launch a visual cmux panel of 1-4 phase sessions, or an unattended fleet, and inspect or tear it down

• /pwdev-power:init

  Initialize or resume the PWDEV Power workspace, map the codebase, and check its runtime surface

• /pwdev-power:plan

  Brainstorm, design, and decompose a feature into an executable plan

• /pwdev-power:product

  Create an approval-gated product requirement or decompose an approved one into an executable roadmap

• /pwdev-power:quick

  Deliver a small bounded change without a plan file

• /pwdev-power:verify

  Adversarially verify an implementation and decide how to integrate it

Subagents (5)

• implementer

  Implements exactly ONE task from an approved PWDEV Power plan: writes the failing test first, implements the minimum that passes, verifies, and commits. Dispatched by /pwdev-power:exec, one at a time, never in parallel. Does not plan, does not review, and does not dispatch anyone.

• mapper

  Maps an existing repository into the four context documents under .planning/power/context/ — project, stack, domain and pitfalls. Dispatched by /pwdev-power:init. Read-only: it observes and records, and never decides an approach, proposes a refactor, or writes implementation code.

• roadmap

  Decomposes an approved product requirement into the multi-file executable roadmap under .planning/power/product/roadmap/ — the Phase→Epic→Feature→Task hierarchy with full traceability. Dispatched by /pwdev-power:product roadmap. Never interviews the human and never writes implementation code.

• task-reviewer

  Reviews ONE completed PWDEV Power task against its brief and the plan's global constraints, returning two independent verdicts — spec compliance and task quality. Dispatched by /pwdev-power:exec after each task and after each fix round. Reports findings; never edits code.

• verifier

  Adversarially verifies that a PWDEV Power feature is complete: tries to REFUTE each truth the spec states — objective, acceptance criteria, definition of done, prohibitions — using real commands, and reports what survived. Dispatched by /pwdev-power:verify. Writes a verdict and, on rejection, a boun

Hooks (6)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/scripts/guard-secrets.sh"

• SubagentStart

  "${CLAUDE_PLUGIN_ROOT}/scripts/audit-hook.sh" subagent_start

• SubagentStop

  "${CLAUDE_PLUGIN_ROOT}/scripts/audit-hook.sh" subagent_stop

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/scripts/audit-hook.sh" artifact

• Stop

  "${CLAUDE_PLUGIN_ROOT}/scripts/audit-hook.sh" stop

Similar plugins