Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Enable or disable a strict engineering workflow for coding tasks enforcing goal clarification, specs, planning, test-driven small steps, and verification.
Enable or disable a strict engineering workflow for coding tasks enforcing goal clarification, specs, planning, test-driven small steps, and verification.
This item is timing out or returning errors right now. Review the source page and try again later.
Use the source page and any available docs to guide the install because the item is currently unstable or timing out.
I tried to install a skill package from Yavira, but the item is currently unstable or timing out. Inspect the source page and any extracted docs, then tell me what you can confirm and any manual steps still required.
I tried to upgrade a skill package from Yavira, but the item is currently unstable or timing out. Compare the source page and any extracted docs with my current installation, then summarize what changed and what manual follow-up I still need.
Use this only when the user explicitly asks to enable/disable this mode, or when mode is already enabled for coding tasks.
Track mode in: memory/superpowers-mode.md Format: enabled: true|false updatedAt: <ISO> notes: <optional>
Enable phrases: включи superpowers, enable superpowers, superpowers on Write enabled: true to the state file. Confirm in 1 short message. Disable phrases: выключи superpowers, disable superpowers, superpowers off Write enabled: false. Confirm in 1 short message. Status phrases: статус superpowers, superpowers status Read state and report enabled/disabled.
For coding/build/debug requests, follow this order: Clarify objective and constraints quickly. Produce a short spec (chunked, easy to review). Produce an implementation plan with small tasks. (Optional, 30 sec) Run a mini risk review: How can this fail in production? What is the weakest dependency/state assumption? What signal will show regression + how to rollback fast? Execute task-by-task (prefer test-first for risky changes). Verify against acceptance criteria, then summarize outcome + next step. Use templates from references/ when useful.
If you notice these thoughts, slow down and apply the workflow: "Сейчас быстро вкачу без плана" for non-trivial changes. "И так понятно, тесты потом" on risky edits. "Откат не нужен" before touching config/auth/cron/system files. "Похоже работает" without explicit verification.
Do not force this workflow for non-coding chat. If user asks for speed (quick, без плана, just do it), skip to minimal plan and execute. Keep updates concise; avoid process spam.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.