メニュー
This skill should be used when the user asks to "execute the plan", "run the plan", "implement the plan", or wants to follow through on a plan created by /write-plan.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
Use this skill when reviewing production code for dead code, duplication, unnecessary complexity, and non-idiomatic patterns. Use after implementing a feature, after refactors, or whenever code quality feedback is requested.
Use this skill to review tests for false confidence, excessive mocking, meaningless assertions, and weak behavior coverage. Use after writing tests or when a suite passes but bugs still escape.
Multi-agent debate with visible transcripts where agents respond to each other. USE WHEN council, debate, perspectives, weigh options, deliberate, multiple viewpoints. Unlike RedTeam (adversarial), Council is collaborative-adversarial.
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
Use this skill when the user asks to "commit", "make a commit", "commit my changes", "create a commit", or invokes /commit. Detects the active VCS (git, jj, or hg), inspects the working copy, drafts a commit message in the project's standard format (terse summary + detailed paragraph + test plan), and creates the commit. Honors staged-files-only when files are already staged in git. Handles jj-specific traps (interactive editors, conflict states, the operation log, the post-commit working copy gotcha) without dropping into TUIs that block non-interactive shells.
| name | execute-plan |
| description | This skill should be used when the user asks to "execute the plan", "run the plan", "implement the plan", or wants to follow through on a plan created by /write-plan. |
| version | 0.1.0 |
| superpowers | executing-plans |
Follow a plan generated by /write-plan sequentially, executing tasks efficiently while staying token-efficient through batching and subagents.
docs/plans//write-plandocs/plans/ or ask user which plan to executeFor each task:
Group related tasks when efficient:
But always:
Use Task tool with subagents for heavy operations:
This keeps the main context lean and token-efficient.
After each task or batch:
If a task fails:
When resuming a partially complete plan:
When all tasks are done: