A structured conversation process for turning a vague creative or software request into an agreed design before implementation. It requires context discovery, one question at a time, alternative approaches, and written approval.
A method for assigning separate, unrelated tasks to different coding agents so they can be investigated at the same time. Each agent receives its own focused context.
A workflow for closing completed development work, such as deciding whether to merge changes, open a pull request, or clean up a branch. A pull request is a request for others to review and add your changes to the main codebase.
A set of coding guidelines based on observations about common mistakes made by language models. It emphasizes simple solutions, small targeted edits, clear assumptions, and checkable results.
A specification-driven development process that records proposed software changes, implementation tasks, and updates to the project’s current behavior specifications.
A procedure for asking another coding agent to inspect completed changes before they are merged. Code review means checking whether the implementation meets its requirements and finding defects.
A set of instructions for applying the Superpowers working method to non-trivial coding tasks. It explains how to load relevant skills, make plans, and coordinate work in this environment.
A test-driven development guide. Test-driven development, or TDD, means writing a test first, confirming that it fails, then writing the smallest code that makes it pass and improving the result.
A guide for turning a multi-step software requirement into a detailed implementation plan before changing code. It assumes the implementer knows software development but not the project’s tools or domain.