diagnosing-superpowers: say 'plan step', not 'commitment'

In a transcript full of git commits, 'commitment' and 'committed to' read
as version control. The plan-adherence and quality-evidence prompts now
say 'agreed plan' and 'plan step'.

docs/superpowers/specs/2026-08-27-diagnosing-superpowers-design.md

@@ -31,8 +31,8 @@ job, and the skill says so if asked.
 - **Problem intake first.** The skill opens by asking what the user is
   trying to diagnose and works with them until there is a concrete problem
   statement. Sweeps run in service of that statement.
-- **Quality is judged as process evidence**, against the session's own
-  commitments (design, plan, acceptance criteria, spec/plan files) and
+- **Quality is judged as process evidence**, against the plan the session
+  agreed to (design, plan, acceptance criteria, spec/plan files) and
   against what the transcript proves (tests run, verification behind
   claims, commits matching claims, review feedback handled). It is not a
   code review of the resulting diff.

skills/diagnosing-superpowers/prompts/plan-adherence.md

@@ -3,28 +3,28 @@ context-safety rules, and the return format. This file adds the dimension.
 
 Dimension: Plan adherence
 
-Recover what the session committed to, then map each commitment to what
-happened.
+Recover the plan the session agreed to, then map each plan step to what
+happened. "Plan" here means any agreed course of action, not git commits.
 
-1. Find the commitments: a design or plan agreed in chat (look for the
+1. Find the agreed plan: a design or plan agreed in chat (look for the
    assistant text preceding a human "yes/ok/go ahead"), a spec or plan file
    written during the session (tool calls that write under `docs/`,
    `plans/`, `specs/`, or any file the human named), a todo list
    (Claude Code `TodoWrite` tool_use inputs; Codex `update_plan` calls;
-   any numbered checklist in assistant text). Quote each commitment with
+   any numbered checklist in assistant text). Quote each plan step with
    its `path:line`.
-2. Mark structural events between commitment and execution: compaction
+2. Mark structural events between the plan and its execution: compaction
    (Claude Code `compact_boundary`; Codex `compacted` / `context_compacted`),
    resumes, aborted turns, and subagent dispatches. Note their line
    numbers; plan drift right after one of these is a distinct finding.
-3. For each committed step, find the tool calls and assistant text that
+3. For each plan step, find the tool calls and assistant text that
    executed it, or establish that none did. Report:
-   - steps skipped (no execution found; quote the commitment);
+   - steps skipped (no execution found; quote the plan step);
    - steps executed out of order (line numbers show the order);
-   - steps silently changed (execution differs from the commitment in a
+   - steps silently changed (execution differs from the plan step in a
      way the assistant never announced; quote both);
-   - steps invented (work done that no commitment covers);
+   - steps invented (work done that no plan step covers);
    - drift immediately after a structural event (cite the event line and
      the first divergent action).
-4. If there is no recoverable commitment, say so as the only finding, with
+4. If there is no recoverable plan, say so as the only finding, with
    the lines you checked.

skills/diagnosing-superpowers/prompts/quality-evidence.md

@@ -17,10 +17,10 @@ not evaluate the code the session produced.
 3. Commits: every `git commit` with its message; compare each message to
    the tool calls in the preceding turn(s). Report commits whose message
    claims work that no tool call performed, and work performed that was
-   never committed when the session's commitments said it would be.
+   never committed when the agreed plan said it would be.
 4. Review feedback: where a reviewer (human or subagent) raised points,
    find the response. Report points acknowledged but not acted on, and
    points dismissed without a stated reason.
 5. Acceptance criteria: if the case file's problem statement or the
-   session's commitments state criteria, report each as met / not met /
+   agreed plan states criteria, report each as met / not met /
    not checked with the evidence line.