Refine Superpowers Lite execution workflow

skills/writing-plans/SKILL.md

@@ -18,7 +18,9 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
 **Save plans to:** `.superpowers-lite/plans/YYYY-MM-DD-<feature-name>-implementation.md`
 - (User preferences for plan location override this default)
 
-**Git tracking:** Generated design and implementation plans are local artifacts, not project deliverables. Before saving a plan in a git repository, ensure `.superpowers-lite/` is listed in `.git/info/exclude`. Do not add or commit generated plans unless the user explicitly asks.
+**Project plan storage:** Before saving a plan, check whether `.superpowers-lite/` exists. If it does not, ask whether Superpowers Lite plans/specs should be tracked by git for this project, then create `.superpowers-lite/config.json` with `planGitTracking` set to `"tracked"` or `"local"`. If `.superpowers-lite/` exists but `.superpowers-lite/config.json` is missing, ask the same question once and create the config. If the config already exists, follow it without asking again. If `planGitTracking` is `"local"`, ensure `.superpowers-lite/` is listed in `.git/info/exclude`; if it is `"tracked"`, do not exclude it.
+
+**Diagrams:** If the plan needs diagrams, prefer PlantUML. Use fenced `plantuml` blocks with complete `@startuml` / `@enduml` content. Use Mermaid only if the user explicitly asks for it or PlantUML is a poor fit.
 
 ## Scope Check
 
@@ -44,7 +46,7 @@ This structure informs the task decomposition. Each task should produce self-con
 - "Run the tests and make sure they pass" - step
 - "Commit" - step
 
-Execution may group several tasks into one phase when the tasks share files, are tightly coupled, or are cheaper to review together. Preserve bite-sized task detail in the plan, but add phase suggestions when grouping is obvious.
+Execution should complete all tasks in the current branch in one run, then perform one overall code review. You may group tasks into phases for readability, but phases are not review checkpoints by default.
 
 ## Plan Document Header
 
@@ -53,7 +55,7 @@ Execution may group several tasks into one phase when the tasks share files, are
 ```markdown
 # [Feature Name] Implementation Plan
 
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers-lite:subagent-driven-development (recommended) or superpowers-lite:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking, and tasks may be grouped into phases for execution and review.
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers-lite:executing-plans by default, or superpowers-lite:subagent-driven-development only when explicitly requested. Steps use checkbox (`- [ ]`) syntax for tracking, and tasks may be grouped into phases for execution readability. Complete all tasks first, then run one overall code review.
 
 **Goal:** [One sentence describing what this builds]
 
@@ -61,7 +63,7 @@ Execution may group several tasks into one phase when the tasks share files, are
 
 **Tech Stack:** [Key technologies/libraries]
 
-**Suggested Phases:** [Group related tasks for execution/review, or "One task per phase" if no grouping is useful]
+**Suggested Phases:** [Optional grouping for execution readability, or "Single run" if no grouping is useful]
 
 ---
 ```
@@ -141,18 +143,18 @@ If you find issues, fix them inline. No need to re-review — just fix and move
 
 After saving the plan, offer execution choice:
 
-**"Plan complete and saved to `.superpowers-lite/plans/<filename>.md` as a local, untracked artifact. Two execution options:**
+**"Plan complete and saved to `.superpowers-lite/plans/<filename>.md`. Default execution is a single current-branch run followed by one overall code review."**
 
-**1. Subagent-Driven (recommended)** - I dispatch a fresh subagent per phase, then run one review loop for that phase
+**1. Execute Now (recommended)** - Complete all tasks in the current branch, then run one final code review
 
-**2. Inline Execution** - Execute tasks in this session using executing-plans, batch tasks into phases with review checkpoints
+**2. Subagent-Driven** - Use subagents for implementation/review only if you explicitly want that workflow
 
 **Which approach?"**
 
+**If Execute Now chosen:**
+- **REQUIRED SUB-SKILL:** Use superpowers-lite:executing-plans
+- Complete all tasks, then one code review
+
 **If Subagent-Driven chosen:**
 - **REQUIRED SUB-SKILL:** Use superpowers-lite:subagent-driven-development
-- Fresh subagent per phase + two-stage review
-
-**If Inline Execution chosen:**
-- **REQUIRED SUB-SKILL:** Use superpowers-lite:executing-plans
-- Batch execution with checkpoints for review
+- Complete all phases, then one overall review unless the user asks for phase reviews