Plan contents can trigger commands or code without action-specific approval
Source references: 6After one review, the skill says to “execute all tasks” and “follow each step exactly,” but does not require renewed authorization before uploads, software installation, credential access, or destructive commands. A separate worktree mainly protects branch state; it does not prevent credential disclosure, external-account actions, or effects outside the worktree.
If a plan is untrusted, altered, or contains steps beyond the user's purpose, the agent could run installers, transmit data, change files, or act on accounts. Critical review and stop-on-concern rules reduce this risk, but only if the agent recognizes the dangerous step.
The skill tells the agent to execute every task after one plan review and to “follow each step exactly.” It does require workspace isolation, escalation of identified concerns, and verification, but it does not explicitly require renewed authorization when a plan uploads data, installs software, accesses credentials, changes external accounts, or performs destructive actions. If a plan contains such steps, broad permission to “execute the plan” could be treated as sufficient. This supports a conditional risk, not evidence that any dangerous plan or command ran. A user can ask the author to add explicit per-action authorization boundaries for sensitive operations.
## OverviewLoad plan, review critically, execute all tasks, report when complete.Show 5 other places
### Step 1: Load and Review Plan1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one2. Read plan file3. Review critically - identify any questions or concerns about the plan4. If concerns: Raise them with your human partner before starting5. If no concerns: Create todos for the plan items and proceed### Step 2: Execute TasksFor each task:1. Mark as in_progress2. Follow each step exactly (plan has bite-sized steps)3. Run verifications as specified4. Mark as completedLoad plan, review critically, execute all tasks, report when complete.### Step 1: Load and Review Plan1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one2. Read plan file3. Review critically - identify any questions or concerns about the plan4. If concerns: Raise them with your human partner before starting5. If no concerns: Create todos for the plan items and proceedFor each task:1. Mark as in_progress2. Follow each step exactly (plan has bite-sized steps)3. Run verifications as specified4. Mark as completed