plastic-intent-executing

# Executing a Plan ## Overview Load plan from the active intent's `plan.md`, execute all tasks, review between tasks, report when complete. **Announce at start:** "I'm using the executing-plan skill to implement this plan." ## Step 0: Sync Worktree First Before Step 1 (Load Plan) in either workflow below, sync the code worktree with main first, so no edit lands on a path a merged rename or delete already removed: ``` git -C <worktree> fetch origin && git -C <worktree> merge --ff-only origin/main ``` After syncing, verify the plan's target files exist at the paths plan.md names. If a named file or directory is missing (renamed or removed upstream), stop and report it rather than editing a stale path. ## Mode Selection ### Check for superpowers first If `superpowers:subagent-driven-development` is available as a skill, delegate to it. If only `superpowers:executing-plans` is available, delegate to that. If neither is available, use Plastic's own execution engine below. **CRITICAL: when delegating to superpowers:** - Tell the skill that the plan is at `~/.plastic/store/ID--slug/plan.md` (not `docs/superpowers/plans/`) - Tell the skill that specs live at `~/.plastic/store/ID--slug/spec.md` (not `docs/superpowers/specs/`) - All meta-artifacts must stay inside `~/.plastic/store/ID--slug/` - Code files go in the project tree as normal - Superpowers skills respect "user preferences for plan/spec location"; Plastic IS that preference ### Subagent-Driven (Default) Dispatches...