using-superpowers

Topics in the source

• Using Superpowers

Use a skill when the user requests it or its workflow materially helps the task. Read the relevant skill once before applying it, and briefly state its purpose. A matching keyword or a small chance of relevance alone does not require loading a skill. Ordinary questions and read-only exploration can proceed directly. User instructions and project policy take precedence. Reuse decisions and authorization already present in the conversation; do not restart an approved design or ask again merely because a skill was loaded. Ask only for information or authorization that is still needed. After the design approval, "ask your human partner" in an upstream skill means: decide within the approved design, record a deviation, and report it in the final message; stop only for the exceptions in documents/development/development-policy.md §1.0 "承認後の進め方". Scale process to the work, not the gate. Every implementation change passes the brainstorming Design Gate (design review, then user approval) before code is written, except the exemption defined there (a typo fix that involves no design choice, or an obviously correct change of a few lines; a fix within an already approved design, such as a quali

This is an excerpt. Refer to the complete source and its current requirements.