powerups

Use for any code change — bug fix, small feature, refactor, or improvement. Ensures TDD, clarifying questions, codebase investigation, DRY, proper branching/worktrees, UI skills, and doc updates. PDD invokes this automatically for large features.

Use when fixing a bug — enforces reproduce-first-then-fix discipline with a strict step-by-step protocol. Prevents wrong-approach loops by gating each step on success criteria.

Use after completing a feature or bug fix to log the change in CHANGELOG.md using plain, business-user-friendly language

Use when building any feature that involves database changes (new table, new column, alter column, etc.) — fork the database like a git branch. Only applies to projects using Ghost DB.

Use when starting any feature (small or large), resuming work after context loss, or unsure if a feature plan already exists. For smaller features, use lightweight mode (no plan file, but all PDD rules still apply).