Write the implementation plan
Translate the approved design into file-level steps with relevant tests and a visible acceptance check.
Superpowers
Superpowers is an installable software development workflow for coding agents. It connects design decisions, implementation planning, test-first changes, and evidence that the work meets its agreed checks.
Plan and verify a bounded code change
Start with an approved design and a repository whose tests the agent can run.
Provide the repository, acceptance criteria and relevant test commands.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatYour request for Floatboat
Preview and copy the request. It is not sent automatically from this page.
Reference: Superpowers https://github.com/obra/superpowers Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Check that Superpowers is available in this coding agent. Turn my approved change into file-level steps and show me the plan. After I approve implementation, add the regression test, record the failing and passing runs, and share the resulting diff and fresh verification output. Expected deliverable: A reviewable plan and patch with fresh test evidence.
About Superpowers
Superpowers is a workflow plugin from Jesse Vincent (obra) for coding agents such as Codex and Claude Code. The suite helps the agent move from clarifying the design to testing and reviewing a patch. Its individual Skills activate at different points in the work.
Writing Plans turns an approved design into file-level tasks, implementation notes and verification commands. Test-Driven Development guides applicable behavior changes through an observed failing test and a passing fix. Verification Before Completion calls for fresh results before a success claim.
The host provides the editor, shell, and any available delegation tools. Supply a bounded repository task, project test commands and explicit permissions. An inspectable plan, diff and command results let a reviewer verify the handoff.
How the Superpowers Workflow Fits Together
Start from an approved specification and choose the next workflow step based on the project state. Keep the proposed checks with the eventual results so implementation and verification can be reviewed together.
Run a test-first change
For a behavior change, reproduce the failure with a test, make the smallest fix, then rerun the test and inspect the patch.
Verify before reporting completion
Run the relevant checks again before claiming success. Include the command, result, and any skipped work in the handoff.
Superpowers Use Cases for Coding Workflows
Use the suite for a task with explicit acceptance conditions. A plan, reproduction, behavior test, and release handoff give reviewers different evidence depending on where the work starts.
Turn a design into an implementation plan
Give the agent an approved design for a new endpoint and the repository’s test conventions. Ask Writing Plans for the files, interfaces, first failing test, and acceptance checks so an engineer can review the scope before changes begin.
Reproduce a bug before writing a patch
Share a failing fixture and its expected behavior. Use the test-driven workflow to capture the failure, make a focused change, and confirm the regression test passes. Keep the failing and passing commands with the patch.
Coordinate a small multi-step change
Provide a reviewed plan for a change that touches configuration and code. Execute the steps in order or delegate only when the host supports it, recording which checks prove the pieces still work together.
Verify a handoff for review
Ask the agent to run the agreed build and test commands against the current branch. Request the exact outputs, known skips, and a short summary of the diff so the reviewer can distinguish verified behavior from open questions.
What Superpowers Needs From Your Agent
Install the suite in a documented host, then provide the repository and test commands it can access. Confirm the approved change scope before running steps that modify files.
A compatible host
Install Superpowers from the documented Codex or Claude Code plugin channel and verify it is enabled in the current session.
Repository and tools
Give the agent a reviewed workspace and access to the project test commands. Configure delegation separately where the host offers it.
Approved work scope
State which files may change and which checks must pass before the result is ready to hand off.
Related Software Projects
Compare the workflows, operating requirements, and source licenses of these projects.
Superpowers FAQ
Which coding agents support Superpowers?
The repository documents installation for Codex and Claude Code, among other hosts. Check the official instructions for your host and version.
Where does Writing Plans fit?
Use it after the design is agreed. It produces implementation steps and checks that can be reviewed before code changes start.
How does its TDD workflow handle a regression?
For applicable behavior changes, first observe the failing test, implement the smallest fix, then run the test again and review the resulting change.
Does every task need a separate agent?
No. Follow the host’s supported execution path. The upstream suite also documents inline execution for approved plans.
What does verification before completion require?
Run the relevant checks against the current work and report the evidence. Keep any skipped checks or failed conditions in the handoff.
Is there a separate guide for debugging?
Yes. The marketplace’s Systematic Debugging guide covers root-cause investigation. The suite page explains how that investigation fits into planning and verification.