Menu
Use when starting any conversation - establishes how to find and use decentpowers skills and the workflow they form.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use to build an approved detailed spec task by task in the current session - tests required, single-agent by default, subagents only for large or parallel tasks.
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 implementation is complete and verified, to integrate the work - merge, PR, or cleanup - after a final evidence check.
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.
Use when you hit any bug, test failure, or unexpected behavior - find the root cause before proposing a fix.
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.
| name | using-decentpowers |
| description | Use when starting any conversation - establishes how to find and use decentpowers skills and the workflow they form. |
You have decentpowers: a small set of workflow skills that keep two disciplines intact - no code before an approved design, and no "done" without verification evidence - while staying lean and cheap to run.
Evidence over claims. Prefer judgment backed by evidence - a test you ran, a diff you read, output you saw - over assertions, and over mechanical checklists. When a skill gives you a rule, it is because the evidence says it earns its place, not for ritual.
Use the Skill tool to load a skill, then follow what it says. Do not read SKILL.md files by hand - load them so they activate. When a skill plausibly applies, invoke it.
One hard gate: before any creative work - a feature, a component, new behavior - go through brainstorming first. That gate is not negotiable. The rest is judgment.
brainstorming → writing-spec → implementing → verifying → finishing
(design, (one detailed (single-agent (deterministic (merge / PR
approve) spec file) build, tests) gate + review) / cleanup)
debugging is called whenever a bug, test failure, or surprising behavior appears - at any point.
| Thought | Reality |
|---|---|
| "This is too simple to design" | Simple tasks hide the costliest assumptions. Brainstorm briefly, then go. |
| "I'll verify later / it should pass" | "Should" is not evidence. Run the check now. |
| "I'll just start coding" | Creative work goes through brainstorming first. |
| "Tests after are fine" | A test you never watched fail proves nothing. |