Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Complete software development workflow enforcing design → plan → execution with checkpoints
Complete software development workflow enforcing design → plan → execution with checkpoints
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Disciplined software development workflow for OpenClaw agents Based on obra/superpowers by Jesse Vincent.
Superclaw prevents your agent from jumping straight into code. It enforces a three-phase workflow: 🧠 Brainstorming (brainstorming/SKILL.md) — Design before code 📋 Writing Plans (writing-plans/SKILL.md) — Plan before implementation ⚙️ Executing Plans (executing-plans/SKILL.md) — Batched execution with checkpoints All three skills chain automatically when building software.
Triggers: When creating features, building components, adding functionality Process: Check context (MEMORY.md, USER.md, daily logs) Ask Socratic questions (requirements, constraints, trade-offs) Propose 2-3 approaches with pros/cons Present design Get approval Save design document to workspace/docs/plans/YYYY-MM-DD-<topic>-design.md Automatically invoke writing-plans skill Hard Gate: No code until design approved.
Triggers: When you have an approved design Process: ASK about methodology (TDD? Direct implementation?) Ask about commit frequency Break work into 2-5 minute tasks Save implementation plan to workspace/docs/plans/YYYY-MM-DD-<topic>-plan.md Automatically invoke executing-plans skill Key Feature: Questions, not mandates. Respects user preferences and time constraints.
Triggers: When you have an implementation plan Process: Load plan from document Batch tasks into groups of 3-5 Execute batch (using sessions_spawn for isolation) Review outputs Checkpoint ("Batch N complete. Continue?") Update memory/YYYY-MM-DD.md with progress Repeat until complete Hard Gate: Maximum 5 tasks per batch. Checkpoints cannot be skipped.
Without Superclaw: Agent jumps to code in seconds (no design, no plan) Errors compound across many tasks No checkpoints → can't pause/resume Mental plans disappear With Superclaw: Design → Plan → Execute (enforced) Errors caught early (batching prevents cascades) Progress tracked in memory Resumable, reviewable, auditable
npx clawhub@latest install superclaw Skills auto-load when relevant tasks are detected.
Memory Integration — Checks MEMORY.md, USER.md, daily logs Methodology Questions — "Should we use TDD?" not "You must use TDD" Sessions_spawn — Fresh subagent per task for isolation Workspace Conventions — Saves to workspace/docs/plans/
All skills pressure-tested with RED-GREEN-REFACTOR methodology: SkillRED (without skill)GREEN (with skill)BrainstormingCoded in 12sAsked questions, got approvalWriting-PlansCoded in 73sAsked methodology, created planExecuting-Plans10 tasks in 40s4 batches with checkpoints Integration test: All 3 skills chained automatically and delivered working CLI ✅
User: "Build a markdown notes CLI" → Brainstorming skill: Asks: Storage format? Search needed? Tagging? Proposes: 3 approaches (flat files vs SQLite vs JSON) Presents design, gets approval Saves: workspace/docs/plans/2026-02-25-notes-cli-design.md Invokes writing-plans → Writing-plans skill: Asks: TDD or direct? Commit frequency? Creates plan: 24 tasks, 2-5 min each Saves: workspace/docs/plans/2026-02-25-notes-cli-plan.md Invokes executing-plans → Executing-plans skill: Batch 1 (tasks 1-5): Project setup → Checkpoint ✓ Batch 2 (tasks 6-10): Create note feature → Checkpoint ✓ Batch 3 (tasks 11-15): List notes feature → Checkpoint ✓ (continues until complete) Result: Working CLI tool, fully documented, tested, and memory-tracked.
brainstorming/SKILL.md — 279 lines, full process + rationalization counters writing-plans/SKILL.md — 10KB, methodology questions + task templates executing-plans/SKILL.md — 9KB, batching logic + sessions_spawn integration Each skill can be used independently or as part of the complete workflow.
Based on obra/superpowers by Jesse Vincent. Adapted for OpenClaw's personal assistant architecture with memory integration, methodology questions (not mandates), sessions_spawn workflow, and single workspace model.
MIT (following obra/superpowers)
GitHub: https://github.com/brothaakhee/superclaw (coming soon) Original Framework: https://github.com/obra/superpowers OpenClaw Docs: https://docs.openclaw.ai
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.