Skip to content

README: clarify the superpowers relationship (TDD disambiguation + brainstorming); bump v3.2.5#20

Open
cahenesy wants to merge 1 commit into
masterfrom
docs/readme-superpowers-clarity
Open

README: clarify the superpowers relationship (TDD disambiguation + brainstorming); bump v3.2.5#20
cahenesy wants to merge 1 commit into
masterfrom
docs/readme-superpowers-clarity

Conversation

@cahenesy
Copy link
Copy Markdown
Owner

Fixes two confusing/conflicting statements in Relationship to superpowers & the official plugins.

1. "TDD" was ambiguous. The section listed TDD under superpowers' ownership, but throughline owns creating TDDs — because the acronym means two different things:

  • in superpowers, TDD = test-driven development (the failing-test-first build discipline);
  • in throughline, a TDD = a Technical Design Document (docs/tdd/).

Added a callout making this explicit (throughline owns the documents; superpowers owns the discipline), and disambiguated the same wording in the file tree and the dependencies list.

2. The brainstorming "contradiction." The section said superpowers owns brainstorming/discovery, then said throughline won't fire superpowers:brainstorming — which read as a conflict. Reframed:

  • throughline owns governance including the design phase: /prd-author + /tdd-author are the governance-producing equivalents of brainstorming/writing-plans (they run the interview and emit a governed artifact);
  • superpowers owns the engineering mechanics + open-ended brainstorming;
  • a dedicated bullet explains throughline skips brainstorming only because its design commands are the design step (double-work otherwise) — and plain brainstorming still stands when no throughline command is driving.

Docs-only + plugin.json 3.2.4 → 3.2.5.

🤖 Generated with Claude Code

test-driven-development) and resolve the brainstorming ownership confusion; bump v3.2.5

- Add a callout: "TDD" = Technical Design Document in throughline vs test-driven
  development in superpowers; throughline owns the documents, superpowers the discipline.
- Reframe ownership: throughline owns governance + the design phase (its /prd-author,
  /tdd-author are the governance-producing equivalents of brainstorming/writing-plans);
  superpowers owns the engineering mechanics + open-ended brainstorming.
- Explain why throughline doesn't double-fire brainstorming (its design commands ARE
  the design step), without contradicting "superpowers owns discovery".
- Disambiguate the same "superpowers:TDD" wording in the file tree + dependencies list.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant