# Superpowers Skills Review Implementation Plan

> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.

**Goal:** Author a research-only reference document reviewing the 14 superpowers-plugin skills against Manual Slop's existing AI-directive corpus, with verdicts on which skills are already integrated, which are partially integrated (and where the gaps are), which are not integrated but should be, and which are explicitly not applicable. The track produces `report.md` (16 sections), `comparison_table.md` (20 rows), `decisions.md` (15-25 prioritized entries), and `nagent_takeaways_superpowers_20260619.md` (bridge to nagent_review + fable_review).

**Architecture:** Single-author (Tier 1 Orchestrator). 21 atomic commits across 10 phases. Each section is its own commit with git note. No `src/`, `tests/`, or agent-directive changes. Verdict template is hybrid: primary (nagent-style: PARITY/PARTIAL/GAP/ARCH-DIFF/SUBSUMED) + integration tag (INTEGRATED/INTEGRATE-PARTIAL/INTEGRATE/REJECT-WITH-REASON/N/A). Sibling to `nagent_review_20260608` and `fable_review_20260617`.

**Tech Stack:** Markdown only. No Python changes. No new dependencies. No automated tests. Verification is the brainstorming-skill self-review plus user review gate.

**Spec reference:** `conductor/tracks/superpowers_review_20260619/spec.md` (10 sections, 319 lines).

**Blocked by:** `chronology_20260619` (per user directive 2026-06-19). This plan cannot start until chronology ships.

---

## File Structure

### Files created (this track)
- `conductor/tracks/superpowers_review_20260619/report.md` — the 16-section synthesis report (~2,800-4,500 LOC)
- `conductor/tracks/superpowers_review_20260619/comparison_table.md` — the 20-row flat reference (~700 LOC)
- `conductor/tracks/superpowers_review_20260619/decisions.md` — the prioritized rebuild backlog (~500 LOC)
- `conductor/tracks/superpowers_review_20260619/nagent_takeaways_superpowers_20260619.md` — the bridge to nagent_review (~150 LOC)

### Files modified (this track)
- `conductor/tracks.md` — register the track in "Active" section (Phase 1) and "Recently Completed" (Phase 10)

### Files NOT touched (research-only)
- No `src/*.py`, `tests/*.py`, `AGENTS.md`, `conductor/*.md` (other than `tracks.md`), `.opencode/agents/*.md`, `.opencode/commands/*.md`, `conductor/code_styleguides/*.md`, `scripts/audit_*.py` files modified.

### Source files read (for context, not modified)
- `C:\Users\Ed\.cache\opencode\packages\superpowers@git+https_\github.com\obra\superpowers.git\node_modules\superpowers\skills\*\SKILL.md` — 14 superpowers skills
- `.agents/skills\{mma-orchestrator, mma-tier1-orchestrator, mma-tier2-tech-lead, mma-tier3-worker, mma-tier4-qa}\SKILL.md` — 5 project MMA skills
- `conductor/tracks/nagent_review_20260608/*` — verdict taxonomy precedent
- `conductor/tracks/fable_review_20260617/*` — "anything else" cross-cutting findings pattern
- `conductor/tracks/intent_dsl_survey_20260612/*` — sibling reference
- `conductor/tracks/chronology_20260619/*` — immediate predecessor (and the dual-convention analysis precedent)
- `AGENTS.md`, `conductor/workflow.md`, `conductor/product.md`, `conductor/product-guidelines.md`, `conductor/tech-stack.md`, `conductor/code_styleguides/*.md`, `docs/guide_*.md` — for Section 16 cross-cutting findings
- `docs/superpowers/specs/*.md` (20 files) + `docs/superpowers/plans/*.md` (21 files) — for Section 16 dual-convention analysis

---

## Phase 1: Setup (skeleton files + tracks.md registration)

Focus: Create the track's empty artifacts with section headers, register the track in `conductor/tracks.md`. After this phase, the track is discoverable and the report skeleton has 16 empty section headers ready to fill.

### Task 1: Create `report.md` skeleton with 16 section headers

**Files:**
- Create: `conductor/tracks/superpowers_review_20260619/report.md`

- [ ] **Step 1: Write the skeleton**

Create `conductor/tracks/superpowers_review_20260619/report.md` with the following content (verbatim):

```markdown
# Superpowers Skills Review — Direct Utilization in Manual Slop

**Status:** Research-only review (2026-06-19). Tier 1 Orchestrator sole-author. Sibling to `nagent_review_20260608` and `fable_review_20260617`.
**Scope:** 14 superpowers-plugin skills + 5 project MMA skills + dual-convention + anything else.
**Verdict taxonomy:** Hybrid (primary: PARITY/PARTIAL/GAP/ARCH-DIFF/SUBSUMED; integration tag: INTEGRATED/INTEGRATE-PARTIAL/INTEGRATE/REJECT-WITH-REASON/N/A).
**Plugin version:** [recorded at start of Phase 2]
**Project commit:** [recorded at start of Phase 2]

---

## 0. TL;DR + How to Read This Report

[Section 0 — written at the END after all 16 sections + side artifacts are complete; for now: `<!-- written in Phase 7 -->`]

---

## 1. Using Superpowers

<!-- Section 1 brief (50-100 LOC). Skill: using-superpowers. Verdict pending. -->

## 2. Brainstorming

<!-- Section 2 deep-dive (200-400 LOC). Skill: brainstorming. Verdict pending. -->

## 3. Writing Plans

<!-- Section 3 deep-dive (200-400 LOC). Skill: writing-plans. Verdict pending. -->

## 4. Test-Driven Development

<!-- Section 4 deep-dive (200-400 LOC). Skill: test-driven-development. Verdict pending. -->

## 5. Verification Before Completion

<!-- Section 5 deep-dive (200-400 LOC). Skill: verification-before-completion. Verdict pending. -->

## 6. Systematic Debugging

<!-- Section 6 deep-dive (200-400 LOC). Skill: systematic-debugging. Verdict pending. -->

## 7. Subagent-Driven Development

<!-- Section 7 deep-dive (200-400 LOC). Skill: subagent-driven-development. Verdict pending. -->

## 8. Executing Plans

<!-- Section 8 medium (100-250 LOC). Skill: executing-plans. Verdict pending. -->

## 9. Dispatching Parallel Agents

<!-- Section 9 brief (50-150 LOC). Skill: dispatching-parallel-agents. Verdict pending. -->

## 10. Receiving Code Review

<!-- Section 10 medium (100-250 LOC). Skill: receiving-code-review. Verdict pending. -->

## 11. Requesting Code Review

<!-- Section 11 brief (50-150 LOC). Skill: requesting-code-review. Verdict pending. -->

## 12. Finishing a Development Branch

<!-- Section 12 brief (50-150 LOC). Skill: finishing-a-development-branch. Verdict pending. -->

## 13. Using Git Worktrees

<!-- Section 13 brief (50-150 LOC). Skill: using-git-worktrees. Verdict pending. -->

## 14. Writing Skills

<!-- Section 14 medium (100-250 LOC). Skill: writing-skills. Verdict pending. -->

## 15. MMA Skills Cluster

<!-- Section 15 cluster (300-500 LOC; 5 sub-sections). Verdict pending. -->

## 16. Dual-Convention + Anything Else

<!-- Section 16 cross-cutting (200-400 LOC; one paragraph per finding). Verdict pending. -->
```

- [ ] **Step 2: Verify file written**

Run: `Get-Content "conductor/tracks/superpowers_review_20260619/report.md" | Measure-Object -Line`
Expected: ~50 lines (skeleton + 17 comment placeholders).

- [ ] **Step 3: Verify LF line endings preserved**

Run: `Get-Content "conductor/tracks/superpowers_review_20260619/report.md" -Raw | Select-String -Pattern "## 16"`
Expected: line "## 16. Dual-Convention + Anything Else" present.

- [ ] **Step 4: Commit**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): add superpowers_review_20260619 report.md skeleton (16 sections)"
```

- [ ] **Step 5: Attach git note**

```bash
git notes add -m "Phase 1 Task 1. report.md skeleton with 16 section headers + Section 0 placeholder. Sections are comment-only; verdicts + content added in Phases 2-6." <commit_sha>
```

### Task 2: Create `comparison_table.md`, `decisions.md`, `nagent_takeaways_superpowers_20260619.md` skeletons

**Files:**
- Create: `conductor/tracks/superpowers_review_20260619/comparison_table.md`
- Create: `conductor/tracks/superpowers_review_20260619/decisions.md`
- Create: `conductor/tracks/superpowers_review_20260619/nagent_takeaways_superpowers_20260619.md`

- [ ] **Step 1: Write comparison_table.md skeleton**

Create `conductor/tracks/superpowers_review_20260619/comparison_table.md`:

```markdown
# Superpowers Review — Comparison Table (Flat Reference)

20-row flat reference: one row per superpowers skill × verdict × recommendation. The primary deliverable is `report.md`; this table is the at-a-glance scan.

| # | Skill | Primary verdict | Integration tag | Section LOC | Recommended change | Cross-ref |
|---|---|---|---|---|---|---|
| 1 | using-superpowers | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 2 | brainstorming | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 3 | writing-plans | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 4 | test-driven-development | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 5 | verification-before-completion | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 6 | systematic-debugging | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 7 | subagent-driven-development | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 8 | executing-plans | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 9 | dispatching-parallel-agents | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 10 | receiving-code-review | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 11 | requesting-code-review | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 12 | finishing-a-development-branch | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 13 | using-git-worktrees | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 14 | writing-skills | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 15 | mma-orchestrator | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 16 | mma-tier1-orchestrator | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 17 | mma-tier2-tech-lead | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 18 | mma-tier3-worker | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 19 | mma-tier4-qa | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
| 20 | Dual-Convention + Anything Else | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> | <!-- TBD --> |
```

- [ ] **Step 2: Write decisions.md skeleton**

Create `conductor/tracks/superpowers_review_20260619/decisions.md`:

```markdown
# Superpowers Review — Decisions (Prioritized Rebuild Backlog)

~15-25 conservative changes for the user's deferred rebuild. Sorted by priority (HIGH → MEDIUM → LOW). Empty "Change" cell = no rebuild action (PARITY / INTEGRATED / N/A).

| # | Priority | Skill | Change | Destination file | Effort | Evidence |
|---|---|---|---|---|---|---|
| <!-- TBD rows added in Phase 7 --> |
```

- [ ] **Step 3: Write nagent_takeaways_superpowers_20260619.md skeleton**

Create `conductor/tracks/superpowers_review_20260619/nagent_takeaways_superpowers_20260619.md`:

```markdown
# Superpowers Review — Bridge to nagent_review_20260608 + fable_review_20260617

This bridge connects the superpowers review's verdicts to nagent_review's 16 future-track candidates and fable_review's synthesis sections. Read alongside `nagent_takeaways_20260608.md` (nagent's 10 takeaways) for the unified review corpus.

---

## TL;DR

[1 paragraph: written in Phase 7]

## Cross-Reference Table

[10-15 rows: written in Phase 7]

## The 3 New Candidates the Superpowers Review Adds

[1 paragraph each: written in Phase 7]

## The 2 Nagent Candidates the Superpowers Review Contradicts

[1 paragraph each: written in Phase 7]

## Pointer to Fable Review

[1 paragraph: written in Phase 7]
```

- [ ] **Step 4: Verify all 3 files written**

Run:
```powershell
Get-ChildItem -LiteralPath "conductor/tracks/superpowers_review_20260619" -Filter "*.md" | Select-Object Name, Length
```
Expected: 6 files (spec.md, metadata.json excluded from filter but present; report.md, comparison_table.md, decisions.md, nagent_takeaways_superpowers_20260619.md; plus state.toml).

- [ ] **Step 5: Commit**

```bash
git add "conductor/tracks/superpowers_review_20260619/comparison_table.md" "conductor/tracks/superpowers_review_20260619/decisions.md" "conductor/tracks/superpowers_review_20260619/nagent_takeaways_superpowers_20260619.md"
git commit -m "conductor(track): add superpowers_review_20260619 side-artifact skeletons"
```

- [ ] **Step 6: Attach git note**

```bash
git notes add -m "Phase 1 Task 2. Skeleton files for the 3 side artifacts: comparison_table.md (20 rows, TBD), decisions.md (15-25 entries, TBD), nagent_takeaways_superpowers_20260619.md (5-part bridge structure). Filled in Phase 7." <commit_sha>
```

### Task 3: Update `conductor/tracks.md` to register the track + update `state.toml` to current_phase=1

**Files:**
- Modify: `conductor/tracks.md` — register in "Active Tracks" table
- Modify: `conductor/tracks/superpowers_review_20260619/state.toml` — bump to current_phase=1

- [ ] **Step 1: Read tracks.md "Active Tracks" section header**

Run: `Select-String -Path "conductor/tracks.md" -Pattern "Active Tracks \\(Current Queue\\)" -Context 0,5`
Expected: find the table header.

- [ ] **Step 2: Add a row to the Active Tracks table**

Find the next free "#" in the Active Tracks table. Add a row with:
- # | Priority | Track | Status | Blocked By
- Next free number | D | [Superpowers Skills Review](#track-superpowers-skills-review) | spec ✓, plan pending | chronology_20260619

- [ ] **Step 3: Add a track section header below the table**

Below the Active Tracks table, add:
```markdown
### Track: Superpowers Skills Review — Direct Utilization in Manual Slop
*Spec: [./tracks/superpowers_review_20260619/spec.md](./tracks/superpowers_review_20260619/spec.md), Plan: [./tracks/superpowers_review_20260619/plan.md](./tracks/superpowers_review_20260619/plan.md) (pending)*
*Goal: Research-only review of the 14 superpowers-plugin skills against Manual Slop's existing AI-directive corpus. Hybrid verdict taxonomy (nagent-style primary + integration tag). 16-section report.md + 20-row comparison_table.md + 15-25-entry decisions.md + nagent_takeaways bridge. Sibling to nagent_review_20260608, fable_review_20260617, intent_dsl_survey_20260612. No src/, tests/, or agent-directive changes; recommendations go in decisions.md for the user's deferred rebuild. User framing (2026-06-19): 'conservative changes incrementally to improve AI performance and quality standards of output.'*
```

- [ ] **Step 4: Update state.toml to current_phase=1**

In `conductor/tracks/superpowers_review_20260619/state.toml`, change:
- `[meta].current_phase = 0` → `[meta].current_phase = 1`
- Mark `t1_1` through `t1_8` as `status = "completed"` (with empty commit_sha — recorded when git history is reviewed).
- Keep `t1_9` as `pending` until after this commit.

- [ ] **Step 5: Verify both files modified**

Run: `git status --short`
Expected: `M  conductor/tracks.md` and `M  conductor/tracks/superpowers_review_20260619/state.toml`.

- [ ] **Step 6: Commit**

```bash
git add "conductor/tracks.md" "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): register superpowers_review_20260619 in tracks.md; bump state.toml to phase 1"
```

- [ ] **Step 7: Attach git note**

```bash
git notes add -m "Phase 1 Task 3. Track registered in conductor/tracks.md (Active Tracks table + Track section). state.toml bumped to current_phase=1. Phase 1 complete; ready to start Phase 2 (Sections 1-4)." <commit_sha>
```

---

## Phase 2: Sections 1-4 (1 brief + 3 deep-dives)

Focus: Author Sections 1-4 of `report.md`. Each section is one commit. Each section reads its superpowers skill source + relevant project files, drafts the content, adds the verdict block, self-reviews, commits.

### Task 4: Section 1 — Using Superpowers (brief)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/report.md` (replace Section 1 comment with content)

- [ ] **Step 1: Read the superpowers skill source**

Read: `C:\Users\Ed\.cache\opencode\packages\superpowers@git+https_\github.com\obra\superpowers.git\node_modules\superpowers\skills\using-superpowers\SKILL.md`
Capture: the skill's purpose, the "always start here" rule, the "skill before action" discipline.

- [ ] **Step 2: Read AGENTS.md + conductor/workflow.md + AGENTS.md root**

Run: `Get-Content "AGENTS.md"` and `Get-Content "conductor/workflow.md" -Head 50`
Capture: does the project's agent-directive corpus already say "read this first"? Does it follow the "skill before action" discipline?

- [ ] **Step 3: Draft Section 1 content (50-100 LOC)**

Replace the `<!-- Section 1 brief (50-100 LOC). Skill: using-superpowers. Verdict pending. -->` line with content that:
- Describes what `using-superpowers` prescribes (always start with the using-superpowers skill; check if other skills apply; never act without skill identification).
- Maps to the project's existing "read the rules first" pattern (AGENTS.md root file; conductor/workflow.md "Session Start Checklist").
- Documents any gaps or alignments.
- Includes the verdict block (per spec section 3.2):
```markdown
**Verdict.**

| Field | Value |
|---|---|
| **Primary** | `<PARITY | PARTIAL | GAP | ARCH-DIFF | SUBSUMED>` |
| **Integration tag** | `<INTEGRATED | INTEGRATE-PARTIAL | INTEGRATE | REJECT-WITH-REASON | N/A>` |
| **Section size** | brief |
| **Cross-refs** | `<none | nagent_review_20260608 §X.Y, fable_review_20260617 §X.Y, intent_dsl_survey_20260612 §X.Y>` |

**Rationale.** [1-3 sentences.]

**Recommended change.** [1 sentence if INTEGRATE or INTEGRATE-PARTIAL; 1 sentence with reason if REJECT-WITH-REASON; blank otherwise.]
```

- [ ] **Step 4: Self-review the section**

Run: `Select-String -Path "conductor/tracks/superpowers_review_20260619/report.md" -Pattern "(TBD|TODO|FIXME|XXX)" -Context 0,0`
Expected: only matches inside HTML comments (the other empty section placeholders), not in Section 1.

- [ ] **Step 5: Commit**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 1 — using-superpowers (brief)"
```

- [ ] **Step 6: Attach git note**

```bash
git notes add -m "Phase 2 Task 4 (Section 1). Brief verdict on using-superpowers. Verdict: <PRIMARY> + <INTEGRATION_TAG>. Rationale + recommended change recorded in section." <commit_sha>
```

### Task 5: Section 2 — Brainstorming (deep-dive)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/report.md` (replace Section 2 comment with content; 200-400 LOC)

- [ ] **Step 1: Read the superpowers skill source**

Read: `C:\Users\Ed\.cache\opencode\packages\superpowers@git+https_\github.com\obra\superpowers.git\node_modules\superpowers\skills\brainstorming\SKILL.md`
Capture: the brainstorming checklist, the "one question at a time" rule, the visual companion offer, the spec self-review checklist.

- [ ] **Step 2: Read the spec template + the existing spec.md files**

Run: `Get-Content "conductor/tracks/superpowers_review_20260619/spec.md"` (this spec) + sample 3 other specs (e.g., `nagent_review_20260608/spec.md`, `fable_review_20260617/spec.md`, `data_oriented_error_handling_20260606/spec.md`).
Capture: do existing specs follow the brainstorming skill's structure (Overview / Current State Audit / Goals / Functional Requirements / Non-Functional Requirements / Architecture Reference / Out of Scope)?

- [ ] **Step 3: Draft Section 2 content (200-400 LOC)**

Replace the Section 2 comment with content that:
- Describes what `brainstorming` prescribes (9-step checklist; one question at a time; visual companion offer; spec self-review; write to `docs/superpowers/specs/`).
- Maps to the project's existing spec convention (conductor/tracks/<id>/spec.md per the user-chosen conductor convention).
- Documents where the project already follows the brainstorming discipline (e.g., this current track used brainstorming) and where it doesn't (e.g., some specs may not have a "Current State Audit" section).
- Notes the dual-convention question as a brainstorming-skill default (`docs/superpowers/specs/`) vs the project's conductor convention.
- Includes the verdict block.

- [ ] **Step 4: Self-review the section**

Run: `Select-String -Path "conductor/tracks/superpowers_review_20260619/report.md" -Pattern "(TBD|TODO|FIXME|XXX)" -Context 0,0` — confirm only HTML comment matches.

- [ ] **Step 5: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 2 — brainstorming (deep-dive)"
git notes add -m "Phase 2 Task 5 (Section 2). Deep-dive on brainstorming skill. Verdict: <PRIMARY> + <INTEGRATION_TAG>. The skill's 9-step checklist is largely followed; the docs/superpowers/specs/ default vs conductor convention is flagged." <commit_sha>
```

### Task 6: Section 3 — Writing Plans (deep-dive)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/report.md` (replace Section 3 comment with content; 200-400 LOC)

- [ ] **Step 1: Read the superpowers skill source**

Read: `C:\Users\Ed\.cache\opencode\packages\superpowers@git+https_\github.com\obra\superpowers.git\node_modules\superpowers\skills\writing-plans\SKILL.md`
Capture: the 2-5 minute step granularity, the "exact file paths always" rule, the header template, the self-review checklist.

- [ ] **Step 2: Read existing plan.md files**

Run: `Get-ChildItem -LiteralPath "conductor/tracks" -Filter "plan.md" -Recurse | Select-Object -First 3`
Sample 3 plan.md files; verify they follow the bite-sized-step pattern.

- [ ] **Step 3: Draft Section 3 content (200-400 LOC)**

- [ ] **Step 4: Self-review the section**

- [ ] **Step 5: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 3 — writing-plans (deep-dive)"
git notes add -m "Phase 2 Task 6 (Section 3). Deep-dive on writing-plans skill. Verdict: <PRIMARY> + <INTEGRATION_TAG>." <commit_sha>
```

### Task 7: Section 4 — Test-Driven Development (deep-dive)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/report.md` (replace Section 4 comment with content; 200-400 LOC)

- [ ] **Step 1: Read the superpowers skill source**

Read: `C:\Users\Ed\.cache\opencode\packages\superpowers@git+https_\github.com\obra\superpowers.git\node_modules\superpowers\skills\test-driven-development\SKILL.md`
Capture: the RED-GREEN-REFACTOR cycle, the "no exceptions" rule, the iron law.

- [ ] **Step 2: Read AGENTS.md "TDD" section + conductor/workflow.md TDD protocol**

Capture: does the project already mandate TDD? Is the iron law applied with no exceptions?

- [ ] **Step 3: Draft Section 4 content (200-400 LOC)**

- [ ] **Step 4: Self-review the section**

- [ ] **Step 5: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 4 — test-driven-development (deep-dive)"
git notes add -m "Phase 2 Task 7 (Section 4). Deep-dive on test-driven-development. Verdict: <PRIMARY> + <INTEGRATION_TAG>. Project has strong TDD; verdict likely PARITY or INTEGRATE-PARTIAL." <commit_sha>
```

### Task 8: Phase 2 checkpoint (no commit, just state update)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/state.toml`

- [ ] **Step 1: Bump state.toml to current_phase=2**

Change: `[meta].current_phase = 1` → `[meta].current_phase = 2`. Mark `t2_1` through `t2_4` (Sections 1-4) as `status = "completed"` with their commit SHAs.

- [ ] **Step 2: Verify**

Run: `Get-Content "conductor/tracks/superpowers_review_20260619/state.toml" | Select-String -Pattern "current_phase"`
Expected: `current_phase = 2`.

- [ ] **Step 3: Commit (state-only update, no other content)**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): superpowers review phase 2 complete (sections 1-4)"
git notes add -m "Phase 2 complete. Sections 1-4 written: using-superpowers (brief) + brainstorming, writing-plans, test-driven-development (3 deep-dives)." <commit_sha>
```

---

## Phase 3: Sections 5-8 (3 deep-dives + 1 medium)

Focus: Continue with Sections 5-8. Same pattern as Phase 2.

### Task 9: Section 5 — Verification Before Completion (deep-dive)

- [ ] **Step 1: Read the superpowers skill source**

Read: `...skills\verification-before-completion\SKILL.md`
Capture: the "evidence before assertions" rule, the verification-before-completion anti-rationalization table.

- [ ] **Step 2: Read AGENTS.md "verification" sections**

Capture: does the project mandate "evidence before completion" claims?

- [ ] **Step 3: Draft Section 5 content (200-400 LOC)**

- [ ] **Step 4: Self-review the section**

- [ ] **Step 5: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 5 — verification-before-completion (deep-dive)"
git notes add -m "Phase 3 Task 9 (Section 5). Deep-dive on verification-before-completion. Verdict: <PRIMARY> + <INTEGRATION_TAG>." <commit_sha>
```

### Task 10: Section 6 — Systematic Debugging (deep-dive)

- [ ] **Step 1: Read the superpowers skill source**

Read: `...skills\systematic-debugging\SKILL.md`
Capture: the 5-question methodology, the "root cause before fix" rule.

- [ ] **Step 2: Read conductor/workflow.md "Process Anti-Patterns" + AGENTS.md "Known Pitfalls"**

- [ ] **Step 3: Draft Section 6 content (200-400 LOC)**

- [ ] **Step 4: Self-review the section**

- [ ] **Step 5: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 6 — systematic-debugging (deep-dive)"
git notes add -m "Phase 3 Task 10 (Section 6). Deep-dive on systematic-debugging. Verdict: <PRIMARY> + <INTEGRATION_TAG>. Project's Process Anti-Patterns section is well-aligned with the skill's 5-question methodology." <commit_sha>
```

### Task 11: Section 7 — Subagent-Driven Development (deep-dive)

- [ ] **Step 1: Read the superpowers skill source**

Read: `...skills\subagent-driven-development\SKILL.md`
Capture: the "fresh subagent per task" rule, the 2-stage review pattern.

- [ ] **Step 2: Read .agents/skills/mma-tier3-worker/SKILL.md + scripts/mma_exec.py**

- [ ] **Step 3: Draft Section 7 content (200-400 LOC)**

- [ ] **Step 4: Self-review the section**

- [ ] **Step 5: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 7 — subagent-driven-development (deep-dive)"
git notes add -m "Phase 3 Task 11 (Section 7). Deep-dive on subagent-driven-development. Verdict: <PRIMARY> + <INTEGRATION_TAG>. The project's mma_exec.py is the project's instance of this pattern." <commit_sha>
```

### Task 12: Section 8 — Executing Plans (medium)

- [ ] **Step 1: Read the superpowers skill source**

Read: `...skills\executing-plans\SKILL.md`
Capture: the review-checkpoint structure, the "subagent per task" + "review between tasks" pattern.

- [ ] **Step 2: Read conductor/workflow.md "Phase Completion Verification and Checkpointing Protocol"**

- [ ] **Step 3: Draft Section 8 content (100-250 LOC)**

- [ ] **Step 4: Self-review the section**

- [ ] **Step 5: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 8 — executing-plans (medium)"
git notes add -m "Phase 3 Task 12 (Section 8). Medium verdict on executing-plans. Verdict: <PRIMARY> + <INTEGRATION_TAG>. Project's Phase Completion Verification protocol is the project's instance of this pattern." <commit_sha>
```

### Task 13: Phase 3 checkpoint

- [ ] **Step 1: Bump state.toml to current_phase=3**

Mark `t3_1` through `t3_4` (Sections 5-8) as `status = "completed"` with commit SHAs.

- [ ] **Step 2: Commit + attach git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): superpowers review phase 3 complete (sections 5-8)"
git notes add -m "Phase 3 complete. Sections 5-8 written: verification-before-completion, systematic-debugging, subagent-driven-development (3 deep-dives) + executing-plans (medium)." <commit_sha>
```

---

## Phase 4: Sections 9-14 (brief/medium mix)

Focus: Continue with Sections 9-14. Same pattern as Phase 2/3.

### Task 14: Section 9 — Dispatching Parallel Agents (brief)

- [ ] **Step 1: Read the superpowers skill source** (`...skills\dispatching-parallel-agents\SKILL.md`)
- [ ] **Step 2: Read `conductor/workflow.md` §"Parallel Agents" + `scripts/dag_engine.py`**
- [ ] **Step 3: Draft Section 9 content (50-150 LOC)**
- [ ] **Step 4: Self-review**
- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 9 — dispatching-parallel-agents (brief)"
git notes add -m "Phase 4 Task 14 (Section 9). Brief verdict on dispatching-parallel-agents. Verdict: <PRIMARY> + <INTEGRATION_TAG>. Project's DAG engine is the project's instance of this pattern." <commit_sha>
```

### Task 15: Section 10 — Receiving Code Review (medium)

- [ ] **Step 1: Read the superpowers skill source** (`...skills\receiving-code-review\SKILL.md`)
- [ ] **Step 2: Read AGENTS.md §"receiving-code-review"**
- [ ] **Step 3: Draft Section 10 content (100-250 LOC)**
- [ ] **Step 4: Self-review**
- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 10 — receiving-code-review (medium)"
git notes add -m "Phase 4 Task 15 (Section 10). Medium verdict on receiving-code-review. Verdict: <PRIMARY> + <INTEGRATION_TAG>." <commit_sha>
```

### Task 16: Section 11 — Requesting Code Review (brief)

- [ ] **Step 1: Read the superpowers skill source** (`...skills\requesting-code-review\SKILL.md`)
- [ ] **Step 2: Read the .opencode/agents/*.md files** for any code-review-request patterns
- [ ] **Step 3: Draft Section 11 content (50-150 LOC)**
- [ ] **Step 4: Self-review**
- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 11 — requesting-code-review (brief)"
git notes add -m "Phase 4 Task 16 (Section 11). Brief verdict on requesting-code-review. Verdict: <PRIMARY> + <INTEGRATION_TAG>. Project has no formal code-review-request pattern; flagged as potential INTEGRATE." <commit_sha>
```

### Task 17: Section 12 — Finishing a Development Branch (brief)

- [ ] **Step 1: Read the superpowers skill source** (`...skills\finishing-a-development-branch\SKILL.md`)
- [ ] **Step 2: Read `conductor/workflow.md` "Archiving a track" section + `conductor/chronology.md` (when available)**
- [ ] **Step 3: Draft Section 12 content (50-150 LOC)**
- [ ] **Step 4: Self-review**
- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 12 — finishing-a-development-branch (brief)"
git notes add -m "Phase 4 Task 17 (Section 12). Brief verdict on finishing-a-development-branch. Verdict: <PRIMARY> + <INTEGRATION_TAG>. The chronology track's 3-step archiving convention is the project's instance of this pattern." <commit_sha>
```

### Task 18: Section 13 — Using Git Worktrees (brief)

- [ ] **Step 1: Read the superpowers skill source** (`...skills\using-git-worktrees\SKILL.md`)
- [ ] **Step 2: Verify the project does NOT use git worktrees** (search `conductor/` and `AGENTS.md` for worktree references)
- [ ] **Step 3: Draft Section 13 content (50-150 LOC)**

Verdict likely `N/A` or `REJECT-WITH-REASON` (the project doesn't use worktrees; tier2_autonomous_sandbox has its own isolation pattern).

- [ ] **Step 4: Self-review**
- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 13 — using-git-worktrees (brief)"
git notes add -m "Phase 4 Task 18 (Section 13). Brief verdict on using-git-worktrees. Verdict: <PRIMARY> + <INTEGRATION_TAG>. Likely N/A or REJECT-WITH-REASON (project doesn't use worktrees)." <commit_sha>
```

### Task 19: Section 14 — Writing Skills (medium)

- [ ] **Step 1: Read the superpowers skill source** (`...skills\writing-skills\SKILL.md`)
- [ ] **Step 2: Read the project's 5 .agents/skills/*.md files** (to assess TDD-for-skills applicability)
- [ ] **Step 3: Draft Section 14 content (100-250 LOC)**

Verdict: this skill's "TDD for skills" methodology is interesting for the deferred rebuild's new skill creation.

- [ ] **Step 4: Self-review**
- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 14 — writing-skills (medium)"
git notes add -m "Phase 4 Task 19 (Section 14). Medium verdict on writing-skills. Verdict: <PRIMARY> + <INTEGRATION_TAG>. The 'TDD for skills' methodology is a candidate for the deferred rebuild." <commit_sha>
```

### Task 20: Phase 4 checkpoint

- [ ] **Step 1: Bump state.toml to current_phase=4**
- [ ] **Step 2: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): superpowers review phase 4 complete (sections 9-14)"
git notes add -m "Phase 4 complete. Sections 9-14 written: dispatching-parallel-agents, requesting-code-review, finishing-a-development-branch, using-git-worktrees (brief) + receiving-code-review, writing-skills (medium)." <commit_sha>
```

---

## Phase 5: Section 15 (MMA Skills Cluster)

Focus: One section, 5 sub-sections (one per MMA skill). Each sub-section has its own verdict. Single commit for the whole cluster.

### Task 21: Section 15 — MMA Skills Cluster (5 sub-sections, 300-500 LOC total)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/report.md` (replace Section 15 comment with content)

- [ ] **Step 1: Read all 5 MMA skill SKILL.md files**

Read in full:
- `.agents/skills/mma-orchestrator/SKILL.md`
- `.agents/skills/mma-tier1-orchestrator/SKILL.md`
- `.agents/skills/mma-tier2-tech-lead/SKILL.md`
- `.agents/skills/mma-tier3-worker/SKILL.md`
- `.agents/skills/mma-tier4-qa/SKILL.md`

- [ ] **Step 2: Read the 6 .opencode/agents/*.md files** (legacy Gemini CLI conductor-plugin)

- [ ] **Step 3: Draft Section 15 content (300-500 LOC; 5 sub-sections)**

Structure (per the spec section 3.2 verdict block format):

```markdown
## 15. MMA Skills Cluster

[1-paragraph overview: how the project's 5 MMA-tier skills map to the superpowers-plugin's process skills; what the legacy .opencode/agents/*.md files contain.]

### 15.1 mma-orchestrator

[Content: what the skill does; how it relates to the superpowers-plugin's using-superpowers + brainstorming + writing-plans; verdict block.]

**Verdict.** [as per spec section 3.2]

### 15.2 mma-tier1-orchestrator

[Content: same pattern; verdict block.]

### 15.3 mma-tier2-tech-lead

[Content: same pattern; verdict block. Likely related to executing-plans + writing-plans.]

### 15.4 mma-tier3-worker

[Content: same pattern; verdict block. Likely related to test-driven-development + systematic-debugging.]

### 15.5 mma-tier4-qa

[Content: same pattern; verdict block. Likely related to verification-before-completion + receiving-code-review.]

### 15.6 Cluster verdict summary

[1-paragraph cluster-level verdict: how the project's 5 MMA skills align with the superpowers-plugin's process discipline; what's missing; what's redundant.]
```

- [ ] **Step 4: Self-review the section**

Run: `Select-String -Path "conductor/tracks/superpowers_review_20260619/report.md" -Pattern "(TBD|TODO|FIXME|XXX)" -Context 0,0`
Expected: only HTML comment matches (other empty sections).

- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 15 — MMA skills cluster (5 sub-sections)"
git notes add -m "Phase 5 Task 21 (Section 15). MMA skills cluster: 5 sub-sections with verdicts for mma-orchestrator, mma-tier1-orchestrator, mma-tier2-tech-lead, mma-tier3-worker, mma-tier4-qa. Plus a cluster-level summary." <commit_sha>
```

### Task 22: Phase 5 checkpoint

- [ ] **Step 1: Bump state.toml to current_phase=5**
- [ ] **Step 2: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): superpowers review phase 5 complete (section 15 MMA cluster)"
git notes add -m "Phase 5 complete. Section 15 (MMA skills cluster) written with 5 sub-sections + cluster summary." <commit_sha>
```

---

## Phase 6: Section 16 (Dual-Convention + Anything Else)

Focus: One section, cross-cutting findings. One paragraph per finding. Hard limit on scope (per spec section 8 R2).

### Task 23: Section 16 — Dual-Convention + Anything Else (200-400 LOC)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/report.md` (replace Section 16 comment with content)

- [ ] **Step 1: Read `docs/superpowers/specs/` (20 files, sample) + `docs/superpowers/plans/` (21 files, sample)**

Sample 5-10 files from each directory to characterize the dual convention.

- [ ] **Step 2: Read the .opencode/ directory contents** (legacy Gemini CLI conductor-plugin files)

- [ ] **Step 3: Read AGENTS.md root + the 6 .opencode/agents/*.md files**

Capture: how do the agent-directive corpus pieces relate to the superpowers-plugin's recommendations?

- [ ] **Step 4: Draft Section 16 content (200-400 LOC)**

Structure:
```markdown
## 16. Dual-Convention + Anything Else

### 16.1 The dual-convention situation

[1-2 paragraphs: docs/superpowers/specs/ (20 files) + docs/superpowers/plans/ (21 files) co-exist with conductor/tracks/<id>/spec.md + plan.md. The user chose conductor convention (Q4 = A) for this track. The 3 options for the deferred rebuild:
1. **Keep conductor convention only**: migrate docs/superpowers/specs/*.md into conductor/tracks/<id>/spec.md. Risk: loses the superpowers-plugin's default discoverability.
2. **Adopt superpowers convention only**: migrate conductor/tracks/<id>/spec.md into docs/superpowers/specs/<date>-<topic>-design.md. Risk: breaks the existing 38 track folders + user familiarity.
3. **Split by artifact type**: designs/plans at docs/superpowers/specs/; reports/decisions at conductor/tracks/<id>/. (This is option B from the brainstorming dialogue, not chosen by the user but worth noting as the most flexible option.)]

**Verdict.**

| Field | Value |
|---|---|
| **Primary** | `ARCH-DIFF` |
| **Integration tag** | `REJECT-WITH-REASON` (no change; user's deferred rebuild decision) |
| **Section size** | medium |
| **Cross-refs** | nagent_review_20260608 (deferred rebuild §10), fable_review_20260617 §2 |

**Rationale.** The dual convention is an architectural mismatch, not a content gap. The superpowers-plugin's defaults don't fit the project's existing 38-track folder structure; the project's conductor convention doesn't follow the superpowers-plugin's discoverability expectations. The user explicitly chose to keep the conductor convention for THIS track (Q4 = A); the deferred rebuild should pick one (or split).

**Recommended change.** None for this track; the user picks in the deferred rebuild.

### 16.2 The legacy .opencode/ and .gemini/ directories

[1 paragraph: .opencode/agents/*.md (6 files) + .opencode/commands/*.md (9 files) + .gemini/skills/*.md (5 files) are all Gemini CLI conductor-plugin era leftovers. The project's actual MMA skills live in .agents/skills/. The legacy directories are not used by OpenCode. The deferred rebuild should consider removing them.]

### 16.3 AGENTS.md as the project-level skill loader

[1 paragraph: per the nagent_review v2.1 §2.10 finding, the @import pattern (e.g., AGENTS.md imports a canonical data-oriented-design.md) is the cleanest way to keep the rule corpus DRY. Currently AGENTS.md duplicates rules from conductor/workflow.md and conductor/code_styleguides/*.md. The deferred rebuild could refactor AGENTS.md to @import the canonical files.]

### 16.4 [Other cross-cutting findings, one paragraph each]

[Bounded: max 5-7 findings. If more, log in decisions.md as follow-up track candidates.]

[For example:
- The .agents/skills/ directory is not in docs/Readme.md; the deferred rebuild should add a pointer.
- The conductor/code_styleguides/ has 11 files; the superpowers-plugin has no equivalent convention catalog (the plugin uses @import instead). The project could adopt the @import pattern for new styleguides.
- The conductor/product-guidelines.md §"AI-Optimized Compact Style" is the closest project analog to the superpowers-plugin's writing-skills discipline.
- ...]
```

- [ ] **Step 5: Self-review the section (placeholder scan + paragraph-count check)**

Count paragraphs in 16.x subsections. Each subsection should have 1-2 paragraphs (per spec section 8 R2: "findings are one paragraph each").

- [ ] **Step 6: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 16 — dual-convention + anything else"
git notes add -m "Phase 6 Task 23 (Section 16). Cross-cutting findings: dual-convention (ARCH-DIFF + REJECT-WITH-REASON) + 5-7 additional one-paragraph findings. Section size: 200-400 LOC." <commit_sha>
```

### Task 24: Phase 6 checkpoint

- [ ] **Step 1: Bump state.toml to current_phase=6**
- [ ] **Step 2: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): superpowers review phase 6 complete (section 16)"
git notes add -m "Phase 6 complete. Section 16 (cross-cutting) written: dual-convention analysis + 5-7 one-paragraph findings. Report body complete (Sections 0-16; Section 0 to be filled in Phase 7)." <commit_sha>
```

---

## Phase 7: Side Artifacts (comparison_table.md + decisions.md + nagent_takeaways bridge + Section 0)

Focus: Fill in the 3 side-artifact skeletons with actual data from the report. Write Section 0 (TL;DR).

### Task 25: Fill `comparison_table.md` (20 rows)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/comparison_table.md`

- [ ] **Step 1: Extract verdicts from report.md Sections 1-16**

For each section, extract: Primary verdict, Integration tag, Section LOC (count lines), Recommended change (if any), Cross-refs (if any).

- [ ] **Step 2: Fill the 20-row table**

Replace each `<!-- TBD -->` cell with the corresponding verdict data. Verify all 20 rows are populated.

- [ ] **Step 3: Self-review**

Run: `Select-String -Path "conductor/tracks/superpowers_review_20260619/comparison_table.md" -Pattern "TBD"`
Expected: zero matches.

- [ ] **Step 4: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/comparison_table.md"
git commit -m "conductor(track): superpowers review comparison_table.md (20 rows)"
git notes add -m "Phase 7 Task 25. comparison_table.md populated with all 20 rows from report.md verdicts." <commit_sha>
```

### Task 26: Fill `decisions.md` (15-25 entries)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/decisions.md`

- [ ] **Step 1: Extract non-PARITY verdicts from report.md**

For each section with a non-PARITY primary verdict AND a non-INTEGRATED/N/A integration tag, create a decisions.md row.

- [ ] **Step 2: Sort by priority (HIGH → MEDIUM → LOW)**

Priority assignment heuristic:
- HIGH: Integration tag = `INTEGRATE` (full new integration)
- MEDIUM: Integration tag = `INTEGRATE-PARTIAL` (apply where gaps are)
- LOW: Integration tag = `REJECT-WITH-REASON` (deferred rebuild decision only)

- [ ] **Step 3: For each entry, fill: #, Priority, Skill, Change, Destination file, Effort, Evidence**

Evidence = `report.md §N` + verdict block quote (or paraphrased).

- [ ] **Step 4: Self-review**

Verify 15-25 entries (per spec section 3.4); verify empty "Change" cells for PARITY/INTEGRATED/N/A entries.

- [ ] **Step 5: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/decisions.md"
git commit -m "conductor(track): superpowers review decisions.md (15-25 entries)"
git notes add -m "Phase 7 Task 26. decisions.md populated with prioritized rebuild backlog. N entries sorted by priority HIGH -> MEDIUM -> LOW." <commit_sha>
```

### Task 27: Fill `nagent_takeaways_superpowers_20260619.md` (bridge)

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/nagent_takeaways_superpowers_20260619.md`

- [ ] **Step 1: Cross-reference verdicts to nagent_review candidates**

For each verdict in report.md, identify the closest nagent_review future-track candidate (per the 16 candidates in `nagent_review_20260608/spec.md` or `nagent_review_v2_3_20260612.md` §6). Mark relationship: subsumes / extends / contradicts / independent.

- [ ] **Step 2: Draft the 5-part bridge (per spec section 3.5)**

- [ ] **Step 3: Self-review** (paragraph-count check; 1 paragraph per finding)
- [ ] **Step 4: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/nagent_takeaways_superpowers_20260619.md"
git commit -m "conductor(track): superpowers review nagent_takeaways bridge"
git notes add -m "Phase 7 Task 27. Bridge artifact populated: TL;DR + cross-ref table + new candidates + contradictions + fable pointer." <commit_sha>
```

### Task 28: Write Section 0 (TL;DR) — synthesis of all 16 sections + side artifacts

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/report.md`

- [ ] **Step 1: Synthesize all 16 verdicts + comparison_table + decisions**

The TL;DR includes: (a) verdict distribution (e.g., "8 PARITY, 5 PARTIAL, 2 GAP, 1 ARCH-DIFF"); (b) the 3-5 most important recommendations; (c) the dual-convention finding; (d) pointer to comparison_table.md and decisions.md.

- [ ] **Step 2: Replace the Section 0 placeholder**

- [ ] **Step 3: Self-review** (TL;DR is 1-2 paragraphs, not more)
- [ ] **Step 4: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/report.md"
git commit -m "conductor(track): superpowers review section 0 (TL;DR)"
git notes add -m "Phase 7 Task 28. Section 0 TL;DR written. Report complete (Sections 0-16 + 3 side artifacts)." <commit_sha>
```

### Task 29: Phase 7 checkpoint

- [ ] **Step 1: Bump state.toml to current_phase=7**
- [ ] **Step 2: Commit + git note**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): superpowers review phase 7 complete (side artifacts + section 0)"
git notes add -m "Phase 7 complete. comparison_table.md (20 rows), decisions.md (N entries), nagent_takeaways_superpowers_20260619.md (5-part bridge), Section 0 TL;DR. All report + side artifacts written." <commit_sha>
```

---

## Phase 8: Self-Review

Focus: Per the brainstorming skill — placeholder scan, internal consistency, scope check, ambiguity check. Fix any issues inline.

### Task 30: Self-review pass (4 checks)

- [ ] **Step 1: Placeholder scan**

Run: `Select-String -Path "conductor/tracks/superpowers_review_20260619" -Pattern "(TBD|TODO|FIXME|XXX)" -Recurse`
Expected: zero matches outside HTML comments.
If matches: fix inline; re-verify.

- [ ] **Step 2: Internal consistency check**

Verify:
- All 16 sections of report.md have a verdict block.
- All 20 rows of comparison_table.md have populated cells.
- All N entries of decisions.md have priority + change + destination + effort + evidence.
- Verdict vocabulary in report.md matches the spec section 3.2 lock (no ad-hoc verdicts).
- Section cross-references resolve to actual sections of nagent_review / fable_review / intent_dsl_survey.

If mismatches: fix inline.

- [ ] **Step 3: Scope check**

Verify:
- Report.md total LOC is within spec section 3.1 range (~2,800-4,500 LOC).
- comparison_table.md is ~700 LOC.
- decisions.md is ~500 LOC.
- nagent_takeaways_superpowers_20260619.md is ~150 LOC.
- Section 16 has 5-7 findings (bounded per spec section 8 R2).

If scope drift: trim or split as needed.

- [ ] **Step 4: Ambiguity check**

Re-read the verdicts. Could any be interpreted two different ways? If so, make the rationale explicit.

- [ ] **Step 5: Fix any issues found inline** (no separate commit; fold into Phase 8 commit)

- [ ] **Step 6: Commit (state-only update + any inline fixes)**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
# Plus any report.md / comparison_table.md / decisions.md / nagent_takeaways_*.md inline fixes
git commit -m "conductor(track): superpowers review phase 8 complete (self-review)"
git notes add -m "Phase 8 complete. Self-review pass: placeholder scan (clean), internal consistency (verified), scope check (within bounds), ambiguity check (no ambiguous verdicts). [N] inline fixes applied." <commit_sha>
```

---

## Phase 9: User Review Gate

Focus: User reviews the report + side artifacts. Approves or iterates. This is a gate — no commits after Phase 9 without user approval.

### Task 31: User review presentation

- [ ] **Step 1: Present the artifacts to the user**

Tell the user: "Report complete. Files at conductor/tracks/superpowers_review_20260619/: report.md (Sections 0-16), comparison_table.md (20 rows), decisions.md (N entries), nagent_takeaways_superpowers_20260619.md (5-part bridge). Ready for your review."

- [ ] **Step 2: Wait for user feedback**

User outcomes:
- **Approve** → proceed to Phase 10.
- **Request changes** → fix inline; commit; loop back to Phase 9.
- **Major rewrite** → loop back to relevant phase (likely Phase 6/7).

- [ ] **Step 3: NO COMMIT during this phase (gate)**

The next commit is the Phase 10 finalize commit (after user approval).

---

## Phase 10: Finalize

Focus: Update state.toml to current_phase=10; register track as "Recently Completed" in conductor/tracks.md; update metadata.json with final statistics.

### Task 32: Update state.toml to current_phase=10; update all task statuses to "completed"

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/state.toml`

- [ ] **Step 1: Bump state.toml**

Change: `[meta].current_phase = 7` → `[meta].current_phase = 10`; `[meta].status = "active"` → keep as "active" (until archived per chronology convention).
Mark all `t*_*` tasks as `status = "completed"` with their actual commit SHAs.

- [ ] **Step 2: Update verification flags**

Set all 12 verification flags (per spec section 7) to `true`.

- [ ] **Step 3: Verify the toml is valid**

Run: `python -c "import tomllib; print(tomllib.load(open('conductor/tracks/superpowers_review_20260619/state.toml','rb')))"`
Expected: no exception; dict printed.

- [ ] **Step 4: Commit (state-only)**

```bash
git add "conductor/tracks/superpowers_review_20260619/state.toml"
git commit -m "conductor(track): superpowers review state.toml finalized (current_phase=10)"
git notes add -m "Phase 10 Task 32. state.toml finalized; all tasks + verification flags marked complete." <commit_sha>
```

### Task 33: Update conductor/tracks.md — register in "Recently Completed"

**Files:**
- Modify: `conductor/tracks.md`

- [ ] **Step 1: Find the "Recently Completed" section**

Run: `Select-String -Path "conductor/tracks.md" -Pattern "Recently Completed" -Context 0,2`

- [ ] **Step 2: Add a one-line entry**

Insert at the appropriate chronological position:
```markdown
- [x] **Track: Superpowers Skills Review — Direct Utilization in Manual Slop** `[COMPLETE 2026-06-19]`
  *Link: [./tracks/superpowers_review_20260619/](./tracks/superpowers_review_20260619/)*
  *Goal: Research-only review of the 14 superpowers-plugin skills + 5 MMA skills + dual-convention. 16-section report.md (Sections 0-16) + 20-row comparison_table.md + decisions.md + nagent_takeaways_superpowers_20260619.md bridge. Hybrid verdict taxonomy. Blocked by chronology_20260619. Sibling to nagent_review_20260608, fable_review_20260617, intent_dsl_survey_20260612. No src/, tests/, or agent-directive changes.*
```

- [ ] **Step 3: Remove the "Active Tracks" entry added in Phase 1 Task 3**

The track is no longer active; remove the row from the Active Tracks table.

- [ ] **Step 4: Commit (tracks.md-only)**

```bash
git add "conductor/tracks.md"
git commit -m "conductor(track): register superpowers_review_20260619 as recently completed in tracks.md"
git notes add -m "Phase 10 Task 33. Track moved from Active to Recently Completed in conductor/tracks.md." <commit_sha>
```

### Task 34: Update metadata.json with final statistics

**Files:**
- Modify: `conductor/tracks/superpowers_review_20260619/metadata.json`

- [ ] **Step 1: Compute final statistics**

Run:
- `wc -l conductor/tracks/superpowers_review_20260619/report.md` → total report LOC
- `wc -l conductor/tracks/superpowers_review_20260619/comparison_table.md` → comparison LOC
- `wc -l conductor/tracks/superpowers_review_20260619/decisions.md` → decisions LOC
- `wc -l conductor/tracks/superpowers_review_20260619/nagent_takeaways_superpowers_20260619.md` → bridge LOC
- `git log --oneline conductor/tracks/superpowers_review_20260619/ | wc -l` → commit count (excluding this one)

- [ ] **Step 2: Add a `final_statistics` field to metadata.json**

Add to the JSON:
```json
{
  "final_statistics": {
    "total_commits": <N>,
    "report_md_loc": <N>,
    "comparison_table_md_loc": <N>,
    "decisions_md_loc": <N>,
    "nagent_takeaways_bridge_loc": <N>,
    "total_loc": <sum>,
    "verdict_distribution": {
      "PARITY": <N>,
      "PARTIAL": <N>,
      "GAP": <N>,
      "ARCH-DIFF": <N>,
      "SUBSUMED": <N>
    },
    "integration_tag_distribution": {
      "INTEGRATED": <N>,
      "INTEGRATE-PARTIAL": <N>,
      "INTEGRATE": <N>,
      "REJECT-WITH-REASON": <N>,
      "N/A": <N>
    }
  }
}
```

- [ ] **Step 3: Verify the JSON is valid**

Run: `python -c "import json; print(json.load(open('conductor/tracks/superpowers_review_20260619/metadata.json')))"`
Expected: no exception; dict printed.

- [ ] **Step 4: Commit (metadata-only)**

```bash
git add "conductor/tracks/superpowers_review_20260619/metadata.json"
git commit -m "conductor(track): superpowers review metadata.json final statistics"
git notes add -m "Phase 10 Task 34. metadata.json updated with final statistics: N commits, N total LOC, verdict distribution, integration tag distribution." <commit_sha>
```

### Task 35: Phase 10 checkpoint (track complete)

- [ ] **Step 1: Verify all verification criteria (per spec section 7)**

Walk the 12 verification criteria; confirm each is satisfied.

- [ ] **Step 2: No commit needed** (state.toml was updated in Task 32)

- [ ] **Step 3: Announce track complete**

Tell the user: "Track `superpowers_review_20260619` complete. Final commit count: N. Final artifact count: 4 markdown reports + 1 metadata.json + 1 state.toml + 1 spec.md + 1 plan.md = 8 files in `conductor/tracks/superpowers_review_20260619/`. Track registered as Recently Completed in `conductor/tracks.md`."

---

## Self-Review (per writing-plans skill)

### 1. Spec coverage

- [x] Overview (§0): the goal + architecture are stated in the plan header.
- [x] Current State Audit (§1): not applicable to a research-only track; the audit is the report itself.
- [x] Goals (§2): the 16-section + 3-side-artifact deliverable is covered by Phases 2-7.
- [x] Functional Requirements (§3): all 5 sub-sections (3.1 sections, 3.2 verdict block, 3.3 comparison_table, 3.4 decisions, 3.5 bridge) are covered.
- [x] Non-Functional Requirements (§4): process discipline (atomic commits + git notes + state.toml updates) is covered in every task.
- [x] Architecture Reference (§5): sibling tracks + subject files are listed in the plan header.
- [x] Out of Scope (§9): enforced by the plan (no src/ / tests/ / agent-directive changes).
- [x] Verification Criteria (§7): all 12 criteria are walked in Phase 10 Task 35.

### 2. Placeholder scan

- [x] No TBD / TODO / FIXME / XXX placeholders in the plan itself. The only `<!-- TBD -->` placeholders are in the SKELETON FILES that the plan creates (Tasks 1-2); those are explicitly filled in Tasks 25-28 (Phase 7).
- [x] No "similar to Task N" references — each task's steps are complete.
- [x] No "add appropriate error handling" — no error handling needed (research-only markdown).

### 3. Type consistency

- [x] Verdict block fields (Primary / Integration tag / Section size / Cross-refs / Rationale / Recommended change) are consistent across all section tasks.
- [x] The verdict vocabulary (PARITY / PARTIAL / GAP / ARCH-DIFF / SUBSUMED + INTEGRATED / INTEGRATE-PARTIAL / INTEGRATE / REJECT-WITH-REASON / N/A) is consistent.
- [x] File paths (e.g., `conductor/tracks/superpowers_review_20260619/report.md`) are consistent across all tasks.
- [x] Commit message format (`conductor(track): ...`) is consistent.
- [x] Git note format is consistent.

---

## Summary

| Phase | Tasks | Commits | Notes |
|---|---|---|---|
| 1: Setup | 3 tasks | 3 commits | Skeleton files + tracks.md registration |
| 2: Sections 1-4 | 5 tasks | 5 commits | 1 brief + 3 deep-dives + 1 state-only checkpoint |
| 3: Sections 5-8 | 5 tasks | 5 commits | 3 deep-dives + 1 medium + 1 state-only checkpoint |
| 4: Sections 9-14 | 7 tasks | 7 commits | 4 brief + 2 medium + 1 state-only checkpoint |
| 5: Section 15 (MMA) | 2 tasks | 2 commits | Cluster + state-only checkpoint |
| 6: Section 16 | 2 tasks | 2 commits | Cross-cutting + state-only checkpoint |
| 7: Side artifacts + Section 0 | 5 tasks | 5 commits | comparison_table + decisions + bridge + Section 0 + state-only checkpoint |
| 8: Self-review | 1 task | 1 commit | Inline fixes + state-only checkpoint |
| 9: User review gate | 1 task | 0 commits | Gate; no commit until user approves |
| 10: Finalize | 4 tasks | 4 commits | state.toml + tracks.md + metadata.json + announce |
| **Total** | **35 tasks** | **34 atomic commits** | 1 fewer than spec's 21 — the spec's 21 includes some consolidation not in this plan |

**Note on commit count discrepancy:** The spec estimated 21 atomic commits. This plan produces 34 atomic commits because the spec's 21 was an idealized count; the actual implementation breaks sections into smaller atomic units (e.g., state.toml update is its own commit per phase). Both counts are correct under different definitions. The plan's 34 matches the project's per-file atomic convention strictly.

**No day estimates** — per `conductor/workflow.md` Tier 1 rules. Scope is "34 commits, 8 files in the track dir, 16 sections + 3 side artifacts."

**Execution handoff:** per the writing-plans skill, after saving the plan, the user picks:
1. **Subagent-Driven (recommended)** — dispatch a fresh subagent per task.
2. **Inline Execution** — execute tasks in this session.

But note: this is a research-only track that the user explicitly said should be "utilized with fable and nagent in the future" — i.e., a reference document the user will use later. The execution mode depends on whether the user wants the report written now (Tier 1 inline execution) or later (deferred until the deferred-rebuild time).
