@liangjie559567/ultrapower 5.6.6 → 5.6.8

package/docs/superpowers/plans/2026-01-22-document-review-system.md

@@ -19,11 +19,13 @@ This chunk adds the spec document reviewer to the brainstorming skill.
 ### Task 1: Create Spec Document Reviewer Prompt Template
 
 **Files:**
-- Create: `skills/brainstorming/spec-document-reviewer-prompt.md`
 
-- [ ] **Step 1:** Create the reviewer prompt template file
+* Create: `skills/brainstorming/spec-document-reviewer-prompt.md`
+
+* [ ] **Step 1:** Create the reviewer prompt template file
 
 ```markdown
+
 # Spec Document Reviewer Prompt Template
 
 Use this template when dispatching a spec document reviewer subagent.
@@ -43,7 +45,7 @@ Task tool (general-purpose):
     ## What to Check
 
     | Category | What to Look For |
-    |----------|------------------|
+    | ---------- | ------------------ |
     | Completeness | TODOs, placeholders, "TBD", incomplete sections |
     | Coverage | Missing error handling, edge cases, integration points |
     | Consistency | Internal contradictions, conflicting requirements |
@@ -73,12 +75,12 @@ Task tool (general-purpose):
 **Reviewer returns:** Status, Issues (if any), Recommendations
 ```
 
-- [ ] **Step 2:** Verify the file was created correctly
+* [ ] **Step 2:** Verify the file was created correctly
 
 Run: `cat skills/brainstorming/spec-document-reviewer-prompt.md | head -20`
 Expected: Shows the header and purpose section
 
-- [ ] **Step 3:** Commit
+* [ ] **Step 3:** Commit
 
 ```bash
 git add skills/brainstorming/spec-document-reviewer-prompt.md
@@ -90,13 +92,14 @@ git commit -m "feat: add spec document reviewer prompt template"
 ### Task 2: Add Review Loop to Brainstorming Skill
 
 **Files:**
-- Modify: `skills/brainstorming/SKILL.md`
 
-- [ ] **Step 1:** Read the current brainstorming skill
+* Modify: `skills/brainstorming/SKILL.md`
+
+* [ ] **Step 1:** Read the current brainstorming skill
 
 Run: `cat skills/brainstorming/SKILL.md`
 
-- [ ] **Step 2:** Add the review loop section after "After the Design"
+* [ ] **Step 2:** Add the review loop section after "After the Design"
 
 Find the "After the Design" section and add a new "Spec Review Loop" section after documentation but before implementation:
 
@@ -108,20 +111,23 @@ After writing the spec document:
    - Fix the issues in the spec document
    - Re-dispatch reviewer
    - Repeat until ✅ Approved
-3. If ✅ Approved: proceed to implementation setup
+1. If ✅ Approved: proceed to implementation setup
 
 **Review loop guidance:**
-- Same agent that wrote the spec fixes it (preserves context)
-- If loop exceeds 5 iterations, surface to human for guidance
-- Reviewers are advisory - explain disagreements if you believe feedback is incorrect
+
+* Same agent that wrote the spec fixes it (preserves context)
+
+* If loop exceeds 5 iterations, surface to human for guidance
+
+* Reviewers are advisory - explain disagreements if you believe feedback is incorrect
 ```
 
-- [ ] **Step 3:** Verify the changes
+* [ ] **Step 3:** Verify the changes
 
 Run: `grep -A 15 "Spec Review Loop" skills/brainstorming/SKILL.md`
 Expected: Shows the new review loop section
 
-- [ ] **Step 4:** Commit
+* [ ] **Step 4:** Commit
 
 ```bash
 git add skills/brainstorming/SKILL.md
@@ -137,11 +143,13 @@ This chunk adds the plan document reviewer to the writing-plans skill.
 ### Task 3: Create Plan Document Reviewer Prompt Template
 
 **Files:**
-- Create: `skills/writing-plans/plan-document-reviewer-prompt.md`
 
-- [ ] **Step 1:** Create the reviewer prompt template file
+* Create: `skills/writing-plans/plan-document-reviewer-prompt.md`
+
+* [ ] **Step 1:** Create the reviewer prompt template file
 
 ```markdown
+
 # Plan Document Reviewer Prompt Template
 
 Use this template when dispatching a plan document reviewer subagent.
@@ -162,7 +170,7 @@ Task tool (general-purpose):
     ## What to Check
 
     | Category | What to Look For |
-    |----------|------------------|
+    | ---------- | ------------------ |
     | Completeness | TODOs, placeholders, incomplete tasks, missing steps |
     | Spec Alignment | Chunk covers relevant spec requirements, no scope creep |
     | Task Decomposition | Tasks atomic, clear boundaries, steps actionable |
@@ -193,12 +201,12 @@ Task tool (general-purpose):
 **Reviewer returns:** Status, Issues (if any), Recommendations
 ```
 
-- [ ] **Step 2:** Verify the file was created
+* [ ] **Step 2:** Verify the file was created
 
 Run: `cat skills/writing-plans/plan-document-reviewer-prompt.md | head -20`
 Expected: Shows the header and purpose section
 
-- [ ] **Step 3:** Commit
+* [ ] **Step 3:** Commit
 
 ```bash
 git add skills/writing-plans/plan-document-reviewer-prompt.md
@@ -210,55 +218,58 @@ git commit -m "feat: add plan document reviewer prompt template"
 ### Task 4: Add Review Loop to Writing-Plans Skill
 
 **Files:**
-- Modify: `skills/writing-plans/SKILL.md`
 
-- [ ] **Step 1:** Read current skill file
+* Modify: `skills/writing-plans/SKILL.md`
+
+* [ ] **Step 1:** Read current skill file
 
 Run: `cat skills/writing-plans/SKILL.md`
 
-- [ ] **Step 2:** Add chunk-by-chunk review section
+* [ ] **Step 2:** Add chunk-by-chunk review section
 
 Add before the "Execution Handoff" section:
 
 ```markdown
+
 ## Plan Review Loop
 
 After completing each chunk of the plan:
 
 1. Dispatch plan-document-reviewer subagent for the current chunk
    - Provide: chunk content, path to spec document
-2. If ❌ Issues Found:
+1. If ❌ Issues Found:
    - Fix the issues in the chunk
    - Re-dispatch reviewer for that chunk
    - Repeat until ✅ Approved
-3. If ✅ Approved: proceed to next chunk (or execution handoff if last chunk)
+1. If ✅ Approved: proceed to next chunk (or execution handoff if last chunk)
 
 **Chunk boundaries:** Use `## Chunk N: <name>` headings to delimit chunks. Each chunk should be ≤1000 lines and logically self-contained.
 ```
 
-- [ ] **Step 3:** Update task syntax examples to use checkboxes
+* [ ] **Step 3:** Update task syntax examples to use checkboxes
 
 Change the Task Structure section to show checkbox syntax:
 
 ```markdown
+
 ### Task N: [Component Name]
 
-- [ ] **Step 1:** Write the failing test
+* [ ] **Step 1:** Write the failing test
   - File: `tests/path/test.py`
   ...
 ```
 
-- [ ] **Step 4:** Verify the review loop section was added
+* [ ] **Step 4:** Verify the review loop section was added
 
 Run: `grep -A 15 "Plan Review Loop" skills/writing-plans/SKILL.md`
 Expected: Shows the new review loop section
 
-- [ ] **Step 5:** Verify the task syntax examples were updated
+* [ ] **Step 5:** Verify the task syntax examples were updated
 
 Run: `grep -A 5 "Task N:" skills/writing-plans/SKILL.md`
 Expected: Shows checkbox syntax `### Task N:`
 
-- [ ] **Step 6:** Commit
+* [ ] **Step 6:** Commit
 
 ```bash
 git add skills/writing-plans/SKILL.md
@@ -274,13 +285,14 @@ This chunk updates the plan document header template to reference the new checkb
 ### Task 5: Update Plan Header Template in Writing-Plans Skill
 
 **Files:**
-- Modify: `skills/writing-plans/SKILL.md`
 
-- [ ] **Step 1:** Read current plan header template
+* Modify: `skills/writing-plans/SKILL.md`
+
+* [ ] **Step 1:** Read current plan header template
 
 Run: `grep -A 20 "Plan Document Header" skills/writing-plans/SKILL.md`
 
-- [ ] **Step 2:** Update the header template to reference checkbox syntax
+* [ ] **Step 2:** Update the header template to reference checkbox syntax
 
 The plan header should note that tasks and steps use checkbox syntax. Update the header comment:
 
@@ -288,12 +300,12 @@ The plan header should note that tasks and steps use checkbox syntax. Update the
 > **For Claude:** REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan. Tasks and steps use checkbox (`- [ ]`) syntax for tracking.
 ```
 
-- [ ] **Step 3:** Verify the change
+* [ ] **Step 3:** Verify the change
 
 Run: `grep -A 5 "For Claude:" skills/writing-plans/SKILL.md`
 Expected: Shows updated header with checkbox syntax mention
 
-- [ ] **Step 4:** Commit
+* [ ] **Step 4:** Commit
 
 ```bash
 git add skills/writing-plans/SKILL.md

package/docs/superpowers/plans/2026-02-19-visual-brainstorming-refactor.md

@@ -15,7 +15,7 @@
 ## File Map
 
 | File | Action | Responsibility |
-|------|--------|---------------|
+| ------ | -------- | --------------- |
 | `lib/brainstorm-server/index.js` | Modify | Server: add `.events` file writing, clear on new screen, replace `wrapInFrame` |
 | `lib/brainstorm-server/frame-template.html` | Modify | Template: remove feedback footer, add content placeholder + selection indicator |
 | `lib/brainstorm-server/helper.js` | Modify | Client JS: remove send/feedback functions, narrow to click capture + indicator updates |
@@ -30,9 +30,10 @@
 ### Task 1: Update `frame-template.html`
 
 **Files:**
-- Modify: `lib/brainstorm-server/frame-template.html`
 
-- [ ] **Step 1: Remove the feedback footer HTML**
+* Modify: `lib/brainstorm-server/frame-template.html`
+
+* [ ] **Step 1: Remove the feedback footer HTML**
 
 Replace the feedback-footer div (lines 227-233) with a selection indicator bar:
 
@@ -50,7 +51,7 @@ Also replace the default content inside `#claude-content` (lines 220-223) with t
     </div>
 ```
 
-- [ ] **Step 2: Replace feedback footer CSS with indicator bar CSS**
+* [ ] **Step 2: Replace feedback footer CSS with indicator bar CSS**
 
 Remove the `.feedback-footer`, `.feedback-footer label`, `.feedback-row`, and the textarea/button styles within `.feedback-footer` (lines 82-112).
 
@@ -74,7 +75,7 @@ Add indicator bar CSS:
     }
 ```
 
-- [ ] **Step 3: Verify template renders**
+* [ ] **Step 3: Verify template renders**
 
 Run the test suite to check the template still loads:
 ```bash
@@ -82,7 +83,7 @@ cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/serve
 ```
 Expected: Tests 1-5 should still pass. Tests 6-8 may fail (expected — they assert old structure).
 
-- [ ] **Step 4: Commit**
+* [ ] **Step 4: Commit**
 
 ```bash
 git add lib/brainstorm-server/frame-template.html
@@ -94,9 +95,10 @@ git commit -m "Replace feedback footer with selection indicator bar in brainstor
 ### Task 2: Update `index.js` — content injection and `.events` file
 
 **Files:**
-- Modify: `lib/brainstorm-server/index.js`
 
-- [ ] **Step 1: Write failing test for `.events` file writing**
+* Modify: `lib/brainstorm-server/index.js`
+
+* [ ] **Step 1: Write failing test for `.events` file writing**
 
 Add to `tests/brainstorm-server/server.test.js` after Test 4 area — a new test that sends a WebSocket event with a `choice` field and verifies `.events` file is written:
 
@@ -119,14 +121,14 @@ Add to `tests/brainstorm-server/server.test.js` after Test 4 area — a new test
     console.log('  PASS');
 ```
 
-- [ ] **Step 2: Run test to verify it fails**
+* [ ] **Step 2: Run test to verify it fails**
 
 ```bash
 cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/server.test.js
 ```
 Expected: New test FAILS — `.events` file doesn't exist yet.
 
-- [ ] **Step 3: Write failing test for `.events` file clearing on new screen**
+* [ ] **Step 3: Write failing test for `.events` file clearing on new screen**
 
 Add another test:
 
@@ -141,14 +143,14 @@ Add another test:
     console.log('  PASS');
 ```
 
-- [ ] **Step 4: Run test to verify it fails**
+* [ ] **Step 4: Run test to verify it fails**
 
 ```bash
 cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/server.test.js
 ```
 Expected: New test FAILS — `.events` not cleared on screen push.
 
-- [ ] **Step 5: Implement `.events` file writing in `index.js`**
+* [ ] **Step 5: Implement `.events` file writing in `index.js`**
 
 In the WebSocket `message` handler (line 74-77 of `index.js`), after the `console.log`, add:
 
@@ -173,7 +175,7 @@ In the chokidar `add` handler (line 104-111), add `.events` clearing:
     }
 ```
 
-- [ ] **Step 6: Replace `wrapInFrame` with comment placeholder injection**
+* [ ] **Step 6: Replace `wrapInFrame` with comment placeholder injection**
 
 Replace the `wrapInFrame` function (lines 27-32 of `index.js`):
 
@@ -183,14 +185,14 @@ function wrapInFrame(content) {
 }
 ```
 
-- [ ] **Step 7: Run all tests**
+* [ ] **Step 7: Run all tests**
 
 ```bash
 cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/server.test.js
 ```
 Expected: New `.events` tests PASS. Existing tests may still have failures from old assertions (fixed in Task 4).
 
-- [ ] **Step 8: Commit**
+* [ ] **Step 8: Commit**
 
 ```bash
 git add lib/brainstorm-server/index.js tests/brainstorm-server/server.test.js
@@ -202,25 +204,26 @@ git commit -m "Add .events file writing and comment-based content injection to b
 ### Task 3: Simplify `helper.js`
 
 **Files:**
-- Modify: `lib/brainstorm-server/helper.js`
 
-- [ ] **Step 1: Remove `sendToClaude` function**
+* Modify: `lib/brainstorm-server/helper.js`
+
+* [ ] **Step 1: Remove `sendToClaude` function**
 
 Delete the `sendToClaude` function (lines 92-106) — the function body and the page takeover HTML.
 
-- [ ] **Step 2: Remove `window.send` function**
+* [ ] **Step 2: Remove `window.send` function**
 
 Delete the `window.send` function (lines 120-129) — was tied to the removed Send button.
 
-- [ ] **Step 3: Remove form submission and input change handlers**
+* [ ] **Step 3: Remove form submission and input change handlers**
 
 Delete the form submission handler (lines 57-71) and the input change handler (lines 73-89) including the `inputTimeout` variable.
 
-- [ ] **Step 4: Remove `pageshow` event listener**
+* [ ] **Step 4: Remove `pageshow` event listener**
 
 Delete the `pageshow` listener we added earlier (no textarea to clear anymore).
 
-- [ ] **Step 5: Narrow click handler to `[data-choice]` only**
+* [ ] **Step 5: Narrow click handler to `[data-choice]` only**
 
 Replace the click handler (lines 36-55) with a narrower version:
 
@@ -234,12 +237,12 @@ Replace the click handler (lines 36-55) with a narrower version:
       type: 'click',
       text: target.textContent.trim(),
       choice: target.dataset.choice,
-      id: target.id || null
+      id: target.id | | null
     });
   });
 ```
 
-- [ ] **Step 6: Add indicator bar update on choice click**
+* [ ] **Step 6: Add indicator bar update on choice click**
 
 After the `sendEvent` call in the click handler, add:
 
@@ -247,12 +250,12 @@ After the `sendEvent` call in the click handler, add:
     // Update indicator bar
     const indicator = document.getElementById('indicator-text');
     if (indicator) {
-      const label = target.querySelector('h3, .content h3, .card-body h3')?.textContent?.trim() || target.dataset.choice;
+      const label = target.querySelector('h3, .content h3, .card-body h3')?.textContent?.trim() | | target.dataset.choice;
       indicator.innerHTML = '<span class="selected-text">' + label + ' selected</span> — return to terminal to continue';
     }
 ```
 
-- [ ] **Step 7: Remove `sendToClaude` from `window.brainstorm` API**
+* [ ] **Step 7: Remove `sendToClaude` from `window.brainstorm` API**
 
 Update the `window.brainstorm` object (lines 132-136) to remove `sendToClaude`:
 
@@ -263,13 +266,13 @@ Update the `window.brainstorm` object (lines 132-136) to remove `sendToClaude`:
   };
 ```
 
-- [ ] **Step 8: Run tests**
+* [ ] **Step 8: Run tests**
 
 ```bash
 cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/server.test.js
 ```
 
-- [ ] **Step 9: Commit**
+* [ ] **Step 9: Commit**
 
 ```bash
 git add lib/brainstorm-server/helper.js
@@ -281,20 +284,21 @@ git commit -m "Simplify helper.js: remove feedback functions, narrow to choice c
 ### Task 4: Update tests for new structure
 
 **Files:**
-- Modify: `tests/brainstorm-server/server.test.js`
+
+* Modify: `tests/brainstorm-server/server.test.js`
 
 **Note:** Line references below are from the _original_ file. Task 2 inserted new tests earlier in the file, so actual line numbers will be shifted. Find tests by their `console.log` labels (e.g., "Test 5:", "Test 6:").
 
-- [ ] **Step 1: Update Test 5 (full document assertion)**
+* [ ] **Step 1: Update Test 5 (full document assertion)**
 
 Find the Test 5 assertion `!fullRes.body.includes('feedback-footer')`. Change it to: Full documents should NOT have the indicator bar either (they're served as-is):
 
 ```javascript
-    assert(!fullRes.body.includes('indicator-bar') || fullDoc.includes('indicator-bar'),
+    assert(!fullRes.body.includes('indicator-bar') | | fullDoc.includes('indicator-bar'),
       'Should not wrap full documents in frame template');
 ```
 
-- [ ] **Step 2: Update Test 6 (fragment wrapping)**
+* [ ] **Step 2: Update Test 6 (fragment wrapping)**
 
 Line 125: Replace `feedback-footer` assertion with indicator bar assertion:
 
@@ -308,7 +312,7 @@ Also verify content placeholder was replaced (fragment content appears, placehol
     assert(!fragRes.body.includes('<!-- CONTENT -->'), 'Content placeholder should be replaced');
 ```
 
-- [ ] **Step 3: Update Test 7 (helper.js API)**
+* [ ] **Step 3: Update Test 7 (helper.js API)**
 
 Lines 140-142: Update assertions to reflect the new API surface:
 
@@ -320,7 +324,7 @@ Lines 140-142: Update assertions to reflect the new API surface:
     assert(!helperContent.includes('sendToClaude'), 'helper.js should not contain sendToClaude');
 ```
 
-- [ ] **Step 4: Replace Test 8 (sendToClaude theming) with indicator bar test**
+* [ ] **Step 4: Replace Test 8 (sendToClaude theming) with indicator bar test**
 
 Replace Test 8 (lines 145-149) — `sendToClaude` no longer exists. Test the indicator bar instead:
 
@@ -335,14 +339,14 @@ Replace Test 8 (lines 145-149) — `sendToClaude` no longer exists. Test the ind
     console.log('  PASS');
 ```
 
-- [ ] **Step 5: Run full test suite**
+* [ ] **Step 5: Run full test suite**
 
 ```bash
 cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/server.test.js
 ```
 Expected: ALL tests PASS.
 
-- [ ] **Step 6: Commit**
+* [ ] **Step 6: Commit**
 
 ```bash
 git add tests/brainstorm-server/server.test.js
@@ -354,9 +358,10 @@ git commit -m "Update brainstorm server tests for new template structure and hel
 ### Task 5: Delete `wait-for-feedback.sh`
 
 **Files:**
-- Delete: `lib/brainstorm-server/wait-for-feedback.sh`
 
-- [ ] **Step 1: Verify no other files import or reference `wait-for-feedback.sh`**
+* Delete: `lib/brainstorm-server/wait-for-feedback.sh`
+
+* [ ] **Step 1: Verify no other files import or reference `wait-for-feedback.sh`**
 
 Search the codebase:
 ```bash
@@ -365,20 +370,20 @@ grep -r "wait-for-feedback" /Users/drewritter/prime-rad/superpowers/ --include="
 
 Expected references: only `visual-companion.md` (rewritten in Task 6) and possibly release notes (historical, leave as-is).
 
-- [ ] **Step 2: Delete the file**
+* [ ] **Step 2: Delete the file**
 
 ```bash
 rm lib/brainstorm-server/wait-for-feedback.sh
 ```
 
-- [ ] **Step 3: Run tests to confirm nothing breaks**
+* [ ] **Step 3: Run tests to confirm nothing breaks**
 
 ```bash
 cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/server.test.js
 ```
 Expected: All tests PASS (no test referenced this file).
 
-- [ ] **Step 4: Commit**
+* [ ] **Step 4: Commit**
 
 ```bash
 git add -u lib/brainstorm-server/wait-for-feedback.sh
@@ -390,9 +395,10 @@ git commit -m "Delete wait-for-feedback.sh: replaced by .events file"
 ### Task 6: Rewrite `visual-companion.md`
 
 **Files:**
-- Modify: `skills/brainstorming/visual-companion.md`
 
-- [ ] **Step 1: Update "How It Works" description (line 18)**
+* Modify: `skills/brainstorming/visual-companion.md`
+
+* [ ] **Step 1: Update "How It Works" description (line 18)**
 
 Replace the sentence about receiving feedback "as JSON" with:
 
@@ -400,7 +406,7 @@ Replace the sentence about receiving feedback "as JSON" with:
 The server watches a directory for HTML files and serves the newest one to the browser. You write HTML content, the user sees it in their browser and can click to select options. Selections are recorded to a `.events` file that you read on your next turn.
 ```
 
-- [ ] **Step 2: Update fragment description (line 20)**
+* [ ] **Step 2: Update fragment description (line 20)**
 
 Remove "feedback footer" from the description of what the frame template provides:
 
@@ -408,11 +414,12 @@ Remove "feedback footer" from the description of what the frame template provide
 **Content fragments vs full documents:** If your HTML file starts with `<!DOCTYPE` or `<html`, the server serves it as-is (just injects the helper script). Otherwise, the server automatically wraps your content in the frame template — adding the header, CSS theme, selection indicator, and all interactive infrastructure. **Write content fragments by default.** Only write full documents when you need complete control over the page.
 ```
 
-- [ ] **Step 3: Rewrite "The Loop" section (lines 36-61)**
+* [ ] **Step 3: Rewrite "The Loop" section (lines 36-61)**
 
 Replace the entire "The Loop" section with:
 
 ```markdown
+
 ## The Loop
 
 1. **Write HTML** to a new file in `screen_dir`:
@@ -421,26 +428,27 @@ Replace the entire "The Loop" section with:
    - Use Write tool — **never use cat/heredoc** (dumps noise into terminal)
    - Server automatically serves the newest file
 
-2. **Tell user what to expect and end your turn:**
+1. **Tell user what to expect and end your turn:**
    - Remind them of the URL (every step, not just first)
    - Give a brief text summary of what's on screen (e.g., "Showing 3 layout options for the homepage")
    - Ask them to respond in the terminal: "Take a look and let me know what you think. Click to select an option if you'd like."
 
-3. **On your next turn** — after the user responds in the terminal:
+1. **On your next turn** — after the user responds in the terminal:
    - Read `$SCREEN_DIR/.events` if it exists — this contains the user's browser interactions (clicks, selections) as JSON lines
    - Merge with the user's terminal text to get the full picture
    - The terminal message is the primary feedback; `.events` provides structured interaction data
 
-4. **Iterate or advance** — if feedback changes current screen, write a new file (e.g., `layout-v2.html`). Only move to the next question when the current step is validated.
+1. **Iterate or advance** — if feedback changes current screen, write a new file (e.g., `layout-v2.html`). Only move to the next question when the current step is validated.
 
-5. Repeat until done.
+1. Repeat until done.
 ```
 
-- [ ] **Step 4: Replace "User Feedback Format" section (lines 165-174)**
+* [ ] **Step 4: Replace "User Feedback Format" section (lines 165-174)**
 
 Replace with:
 
 ```markdown
+
 ## Browser Events Format
 
 When the user clicks options in the browser, their interactions are recorded to `$SCREEN_DIR/.events` (one JSON object per line). The file is cleared automatically when you push a new screen.
@@ -456,7 +464,7 @@ The full event stream shows the user's exploration path — they may click multi
 If `.events` doesn't exist, the user didn't interact with the browser — use only their terminal text.
 ```
 
-- [ ] **Step 5: Update "Writing Content Fragments" description (line 65)**
+* [ ] **Step 5: Update "Writing Content Fragments" description (line 65)**
 
 Remove "feedback footer" reference:
 
@@ -464,18 +472,20 @@ Remove "feedback footer" reference:
 Write just the content that goes inside the page. The server wraps it in the frame template automatically (header, theme CSS, selection indicator, and all interactive infrastructure).
 ```
 
-- [ ] **Step 6: Update Reference section (lines 200-203)**
+* [ ] **Step 6: Update Reference section (lines 200-203)**
 
 Remove the helper.js reference description about "JS API" — the API is now minimal. Keep the path reference:
 
 ```markdown
+
 ## Reference
 
-- Frame template (CSS reference): `${CLAUDE_PLUGIN_ROOT}/lib/brainstorm-server/frame-template.html`
-- Helper script (client-side): `${CLAUDE_PLUGIN_ROOT}/lib/brainstorm-server/helper.js`
+* Frame template (CSS reference): `${CLAUDE_PLUGIN_ROOT}/lib/brainstorm-server/frame-template.html`
+
+* Helper script (client-side): `${CLAUDE_PLUGIN_ROOT}/lib/brainstorm-server/helper.js`
 ```
 
-- [ ] **Step 7: Commit**
+* [ ] **Step 7: Commit**
 
 ```bash
 git add skills/brainstorming/visual-companion.md
@@ -486,14 +496,14 @@ git commit -m "Rewrite visual-companion.md for non-blocking browser-displays-ter
 
 ### Task 7: Final verification
 
-- [ ] **Step 1: Run full test suite**
+* [ ] **Step 1: Run full test suite**
 
 ```bash
 cd /Users/drewritter/prime-rad/superpowers && node tests/brainstorm-server/server.test.js
 ```
 Expected: ALL tests PASS.
 
-- [ ] **Step 2: Manual smoke test**
+* [ ] **Step 2: Manual smoke test**
 
 Start the server manually and verify the flow works end-to-end:
 
@@ -507,17 +517,19 @@ Write a test fragment, open in browser, click an option, verify `.events` file i
 lib/brainstorm-server/stop-server.sh <screen_dir from start output>
 ```
 
-- [ ] **Step 3: Verify no stale references remain**
+* [ ] **Step 3: Verify no stale references remain**
 
 ```bash
-grep -r "wait-for-feedback\|sendToClaude\|feedback-footer\|send-to-claude\|TaskOutput.*block.*true" /Users/drewritter/prime-rad/superpowers/ --include="*.js" --include="*.md" --include="*.sh" --include="*.html" | grep -v node_modules | grep -v RELEASE-NOTES | grep -v "\.md:.*spec\|plan"
+grep -r "wait-for-feedback\ | sendToClaude\ | feedback-footer\ | send-to-claude\ | TaskOutput.*block.*true" /Users/drewritter/prime-rad/superpowers/ --include="*.js" --include="*.md" --include="*.sh" --include="*.html" | grep -v node_modules | grep -v RELEASE-NOTES | grep -v "\.md:.*spec\ | plan"
 ```
 
 Expected: No hits outside of release notes and the spec/plan docs (which are historical).
 
-- [ ] **Step 4: Final commit if any cleanup needed**
+* [ ] **Step 4: Final commit if any cleanup needed**
 
 ```bash
 git status
+
 # Review untracked/modified files, stage specific files as needed, commit if clean
+
 ```