executing-specslisted

# Executing Specifications Implement a specification by orchestrating parallel background agents across dependency-aware batches, with incremental persistence to survive context compaction. ## Supporting Files | File | When Loaded | Purpose | | ------------------------------------ | ------------------- | ----------------------------------------- | | `implementation-summary-template.md` | Phase 1 (once) | Scaffold for `04-implementation.md` | | `analysis-agent-prompt.md` | Phase 2 (once) | Full prompt for the analysis agent | | `implementation-agent-prompt.md` | Phase 3 (per batch) | Full prompt for each implementation agent | **Key rule**: Read supporting files on demand, not upfront. This keeps context lean. --- ## Phase 0: Choose Workspace Execution changes code — decide where it runs before any agent starts. ### 0.1 Detect Current State ```bash git rev-parse --git-dir --git-common-dir && git branch --show-current && git status --porcelain ``` If the two rev-parse paths **differ**, the session is already in a secondary worktree — skip the rest of this phase and execute here. ### 0.2 Worktree Triggers Recommend an isolated worktree when any of these hold: - the working tree has uncommitted changes unrelated to this spec - the current branch is a different topic than this spec - another agent or session is working in this checkout - a dev server in the m