Writing Plans
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only planning skill with no code, install steps, credentials, or hidden execution; users should just review generated plans before using them to guide later agents.
This skill appears safe to install as an instruction-only planning aid. Before letting another session or subagent execute a generated plan, read the saved markdown file and confirm the file changes, commands, and execution handoff match your intent.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A future agent may follow the saved plan’s instructions, so mistakes or overly broad steps in the plan could carry into implementation.
The skill intentionally writes persistent plan files that include instructions aimed at a future Claude session. This is transparent and aligned with the planning workflow, but persisted instructions can influence later agent behavior.
**Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md` ... `> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.`
Review generated plan files before using them to drive execution, especially the listed files, commands, and handoff instructions.
If the user chooses subagent-driven execution, separate agents may act on portions of the plan, making review checkpoints important.
The skill describes an optional workflow where tasks are handed to fresh subagents. This is disclosed and user-selected, but it introduces inter-agent handoff that users should supervise.
**1. Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration
Use the subagent option only when comfortable with task-by-task delegation, and keep the stated review-between-tasks checkpoint.