Superpowers-NG is an enhanced fork of obra/superpowers with integrated Manus-style persistent planning for complex, long-running tasks.
The flagship feature is manus-planning, a file-based planning system that survives context resets and enables multi-session work.
Native vs Manus Planning:
| Aspect | Native (Original) | Manus (New) |
|---|---|---|
| Skills | writing-plans + executing-plans | manus-planning |
| Memory | In-memory (TodoWrite) | Persistent files (docs/manus/) |
| Best for | Short tasks (<30 min), interactive development | Long autonomous runs, multi-session projects, >50 tool calls |
| Progress tracking | Lost on context reset | Survives context resets |
| Research storage | Embedded in conversation | Persistent findings.md |
The 3 Files:
task_plan.md- Goal, 5 phases, decisions, errorsfindings.md- Requirements, research, resources (CRITICAL for visual/browser content)progress.md- Session log, test results, 5-question reboot check
When to use Manus:
- Tasks requiring >50 tool calls
- Multi-session projects spanning days
- Complex research with web searches/images
- When context might reset mid-task
How it works:
- Create marker file
docs/manus/.activeto enable PreToolUse hooks - Hooks automatically show plan preview before Write/Edit/Bash operations
- 2-Action Rule: Update
findings.mdafter every 2 search/view operations - On completion: Remove marker, invoke
finishing-a-development-branch
Brainstorming integration:
After design completion, brainstorming now offers both planning options. For Manus, design content is automatically copied into findings.md.
Superpowers is a complete software development workflow for your coding agents, built on composable "skills" that trigger automatically.
When you start building something, your agent:
- Asks questions to understand what you're really trying to do
- Shows the design in digestible chunks for your approval
- Creates an implementation plan clear enough for a junior engineer to follow
- Executes autonomously through subagent-driven development
The core philosophy: Test-Driven Development, YAGNI, DRY, and systematic over ad-hoc.
Note: Installation differs by platform. Claude Code or Cursor have built-in plugin marketplaces. Codex and OpenCode require manual setup.
# Will be available via marketplace:
/plugin marketplace add OniReimu/superpowers-ng-marketplace
/plugin install superpowers-ng@superpowers-ng-marketplace# Clone the repository
git clone https://github.com/OniReimu/superpowers-ng.git
cd superpowers-ng
# Install as a local plugin
# (Instructions TBD based on Claude Code local plugin support)In Cursor Agent chat, install from marketplace:
/plugin-add superpowers-ng
Cursor uses the same hook pipeline as Claude Code. On each SessionStart it now:
- checks
docs/manus/.active - resumes Manus by reading
task_plan.md/progress.md/findings.mdwhen active - falls back to native startup flow with a lightweight plan + "enable manus?" prompt when inactive
See docs/README.codex.md for detailed instructions.
See docs/README.opencode.md for detailed instructions.
OpenCode now uses the same planning bootstrap logic as Claude/Cursor/Codex:
- checks
docs/manus/.activeat startup context injection - emits
Planning mode: MANUSfor active Manus tasks (with continuation snapshot) - emits
Planning mode: NATIVEwhen no active task exists
Start a new session in your chosen platform and ask for something that should trigger a skill (for example, "help me plan this feature" or "let's debug this issue"). The agent should automatically invoke the relevant superpowers skill.
-
brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.
-
using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.
-
Choose your planning system:
- Native:
writing-plans→executing-plansfor short tasks - Manus:
manus-planningfor complex/long-running tasks
- Native:
-
subagent-driven-development or executing-plans - Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality), or executes in batches with human checkpoints.
-
test-driven-development - Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit.
-
requesting-code-review - Reviews against plan, reports issues by severity. Critical issues block progress.
-
finishing-a-development-branch - Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.
The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.
Native Planning (Original)
- writing-plans - Bite-sized implementation plans
- executing-plans - Batch execution with checkpoints
Manus Planning (New)
- manus-planning - 5-phase workflow with persistent files
- Phase 1: Requirements & Discovery
- Phase 2: Planning & Structure
- Phase 3: Implementation
- Phase 4: Testing & Verification
- Phase 5: Delivery
- test-driven-development - RED-GREEN-REFACTOR cycle (includes testing anti-patterns reference)
- systematic-debugging - 4-phase root cause process (includes root-cause-tracing, defense-in-depth, condition-based-waiting techniques)
- verification-before-completion - Ensure it's actually fixed
- brainstorming - Socratic design refinement (enhanced with planning choice)
- dispatching-parallel-agents - Concurrent subagent workflows
- requesting-code-review - Pre-review checklist
- receiving-code-review - Responding to feedback
- using-git-worktrees - Parallel development branches
- finishing-a-development-branch - Merge/PR decision workflow
- subagent-driven-development - Fast iteration with two-stage review
- writing-skills - Create new skills following best practices
- using-superpowers - Introduction to the skills system (updated with planning guidance)
- Test-Driven Development - Write tests first, always
- Systematic over ad-hoc - Process over guessing
- Complexity reduction - Simplicity as primary goal
- Evidence over claims - Verify before declaring success
- Persistent memory (New) - Filesystem as external memory for long tasks
Superpowers-NG works seamlessly with Ralph, the autonomous loop framework for Claude Code.
Ralph provides: Loop orchestration, session management, exit detection, rate limiting
Superpowers-NG provides: Development methodologies, TDD discipline, debugging workflows, persistent planning
Key features for Ralph users:
- brainstorming now auto-detects existing designs and skips in subsequent loops
- manus-planning designed for multi-loop persistence with auto-resume
- verification-before-completion ensures evidence-based exit signals
- Skills are autonomous-mode aware (no waiting for user input)
Get started:
# Copy enhanced PROMPT.md template to your Ralph project
cp docs/ralph-integration/PROMPT.template.md /path/to/ralph-project/PROMPT.mdSee docs/ralph-integration/README.md for complete integration guide.
Skills live directly in this repository. To contribute:
- Fork the repository
- Create a branch for your skill
- Follow the
writing-skillsskill for creating and testing new skills - Submit a PR
See skills/writing-skills/SKILL.md for the complete guide.
-
Jesse Vincent (obra) - obra/superpowers
- Original Superpowers framework and skills system
-
Ahmad Othman Ammar Adi (OthmanAdi) - planning-with-files
- Manus-style 3-file planning pattern
- OniReimu - Integration and enhancement
- Manus AI (acquired by Meta) - Context engineering principles
- Superpowers blog post
MIT License - see LICENSE file for details
- Issues: https://github.com/OniReimu/superpowers-ng/issues
- Original Superpowers: https://github.com/obra/superpowers
- Planning-with-files: https://github.com/OthmanAdi/planning-with-files