Brainstorming skill ignores CLAUDE.md Output Paths, always writes to docs/superpowers/specs/

[shalinhudda]

Summary

The brainstorming skill hardcodes docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md as the output path for design specs. Even when CLAUDE.md defines an Output Paths table with a different location (e.g., docs/design-docs/), the skill's concrete path wins every time.

The skill has a parenthetical hint on line 112:

(User preferences for spec location override this default)

But in practice, Claude never checks for or applies this override.

Reproduction

1. Create a project with a CLAUDE.md containing:

   ## Output Paths
   | Artifact | Location |
   |---|---|
   | Design specs | `docs/design-docs/` |

2. Start a fresh Claude Code session (so CLAUDE.md is loaded)

3. Brainstorm anything — e.g., "Let's brainstorm a simple CLI tool that converts CSV files to JSON"

4. Approve the design

Expected: Spec written to docs/design-docs/2026-03-25-csv2json-design.md
Actual: Spec written to docs/superpowers/specs/2026-03-25-csv2json-design.md

Root Cause (from Claude's own analysis)

When asked why it missed the CLAUDE.md override, Claude explained:

The skill gives a concrete, copy-pasteable path right in the instruction. CLAUDE.md's output paths are in a table that I'd already processed earlier in context. When I got to the "write the doc" step, I followed the specific path right in front of me rather than cross-referencing back to CLAUDE.md's table.

The parenthetical "(User preferences for spec location override this default)" is easy to gloss over because:

1. It's a parenthetical — visually subordinate to the concrete path above it
2. It says "user preferences" which is vague — I didn't connect it to CLAUDE.md's output paths table
3. The concrete path was immediately actionable; the override required me to recall and cross-reference

Suggested Fix

Reverse the priority in the instruction — check first, default second. Something like:

**Write the validated design spec:**
1. Check CLAUDE.md for an "Output Paths" table. If "Design specs" has a configured location, use that path.
2. If no output path is configured, use the default: `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`

This likely affects writing-plans as well (execution plans have the same pattern).

Environment

• superpowers v5.0.6
• Claude Code with Opus 4.6

[shalinhudda]

Workaround Found

Adding an explicit imperative instruction directly below the Output Paths table in CLAUDE.md fixes the behavior:

## Output Paths

| Artifact | Location |
|---|---|
| Design specs | `docs/design-docs/` |
| Execution plans (active) | `docs/exec-plans/active/` |

**IMPORTANT: Design specs MUST be saved to `docs/design-docs/`, NOT `docs/superpowers/specs/`. Execution plans MUST be saved to `docs/exec-plans/active/`, NOT `docs/superpowers/plans/`.**

The table alone is not enough — Claude processes the skill's concrete hardcoded path before cross-referencing the table. The bold imperative instruction competes at the same priority level as the skill instruction and wins.

Tested: fresh session with this instruction in CLAUDE.md → brainstorming skill correctly writes to docs/design-docs/ on the first attempt without any user intervention.

[obra]

I think the right fix here is an example of how to override the default in the readme