The pre-execution workflow of obra/superpowers: For any new feature, new component, or even non-software project, the agent first clarifies what the user wants and why, lists two or three approaches for the user to choose from, writes a design document and obtains approval, and then hands it over to the writing-plans skill for planning. No code is written before this stage.
skills.sh install count 411049 (+1309 / 24h)
Security Audit: Not audited
- Not yet scanned
Rationale
- Read before asking: If an existing project is provided or materials are given, first read enough to clearly understand the current state and where changes might impact, without asking questions that already have answers within the project.
- Ask only one question per message; if the user does not explicitly request brainstorming, add a note saying "You can also start directly," and if the user chooses to proceed directly, skip the entire workflow.
- Write design documents according to scale: For small changes, use one or two lines; for project-level changes, write a complete document (intent, goals and non-goals, constraints, alternative approaches), place it in docs/superpowers/specs/ within the software repository, and commit it; for project-level documents, first dispatch a sub-agent to read through it as an implementer and ask a follow-up round of questions.
- If visual inspection is needed, a "Visual Companion" browser tab can be opened to display sketches and clickable prototypes, enabled only after user consent.
- skills.sh installed 1309 times in 24 hours, with a cumulative total of 411049; the same repository contains 14 other skills (representing only attention level).
Usage
- Automatically triggered before starting any creative task; calls the writing-plans skill from the same repository upon completion, and it is best to install them together.
- To skip, state "start directly" in the first reply.
Risks
- Not audited in this period, fixed at Grade C, and install commands are not displayed; the Visual Companion requires starting a local server according to visual-companion.md, but that file and builder-check-prompt.md were not read in this instance.
- Design documents will be committed to the repository; the workflow is heavy, increasing time and token usage.
- Note the distinction from cloned accounts such as skills-shell/superpowers, which are automatically excluded from the leaderboard; this entry comes from obra/superpowers.