executing-plans

<!-- Adapted from obra/superpowers executing-plans skill (v5.0.7), MIT-licensed, copyright 2025 Jesse Vincent. Modifications copyright 2026 Joe Amditis. v0.1.0 added a per-task drift check (default-on research). v0.2.0 replaced that with a one-time freshness check at execution start, default-skip with explicit triggers (cross-session plan, external API, main/master branch), fixing the "execution journal undefined" and "master-branch guardrail not in drift check" bugs surfaced by smoke testing. See CREDITS.md. --> # Executing Plans ## Overview Load plan, review critically, execute all tasks, report when complete. **Announce at start:** "I'm using the superjawn:executing-plans skill to implement this plan." **Note:** Tell your human partner that superjawn works much better with access to subagents. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use superjawn:subagent-driven-development instead of this skill. ## Freshness check (when artifact is stale) The plan was written at a point in time. **Default-skip.** Run only when one of these triggers fires: - **Cross-session execution.** The plan was drafted in a prior session — different cwd, different transcript, or different day. If you wrote the plan yourself in this session, the freshness check is not needed. - **External API/service touched.** Any task in the plan calls an external API, service, or file outside t...