decentpowers

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores intent, requirements, and design before implementation.

Use when you hit any bug, test failure, or unexpected behavior - find the root cause before proposing a fix.

Use to build a spec whose frontmatter says lane fast - same detailed tasks as implementing, but red-green per task with one gate run and one commit per acceptance criterion, and no subagents.

Use when implementation is complete and verified, to integrate the work - merge, PR, or cleanup - after a final evidence check.

Use to build a spec whose frontmatter says lane full - task by task in the current session, tests required, a self-check on every task, and subagents only for large or parallel work.

Use when starting any conversation - establishes how to find and use decentpowers skills and the workflow they form.

Use before claiming work is complete, fixed, or passing - runs the deterministic gate (tests, build, lint, types, acceptance) and one light judgment review, with evidence before any claim.

Use after a design is approved in brainstorming, to turn it into one layered detailed spec (acceptance criteria, tasks, and how to verify) before touching code.