rogee/superpowers
1
0
Fork 0
mirror of https://github.com/obra/superpowers.git synced 2026-08-07 22:59:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(brainstorming): tooling question in the design presentation for new projects

Browse Source 
For a project with no configured tooling, the design presentation now
includes a tooling question — linting/auto-formatting, unit-test
infrastructure, e2e test infrastructure, fuzz/mutation testing — whose
answers land in the spec's Global Constraints. Without this, sessions
never ask and ship plans with zero tooling constraints (0/3 in the
quorum control cell); with it, the ask fires before any code in 3/3
and the user's answer is honored verbatim, including exclusions.

Claude-Session: https://claude.ai/code/session_0185AJr98gHx5EmwqNeft4Sy
This commit is contained in:
Jesse Vincent
2026-08-06 17:28:47 -07:00
parent 5f8f500b1d
commit 537d649ab3
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
skills/brainstorming/SKILL.md
View File

@@ -85,6 +85,7 @@ digraph brainstorming {
- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced - Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced
- Ask after each section whether it looks right so far - Ask after each section whether it looks right so far
- Cover: architecture, components, data flow, error handling, testing - Cover: architecture, components, data flow, error handling, testing
- For a new project (or one with no configured tooling), the design presentation includes a short tooling question alongside the architecture: which of these to set up from the start — cheapest before any code exists: aggressive linting + auto-formatting (the stack's standard, e.g. ruff+format / eslint+prettier / clippy+rustfmt); unit-test infrastructure (runner, layout, a first passing fixture); end-to-end test infrastructure; fuzz or mutation testing where the stack supports it. The user's selections land in the spec's Global Constraints so every later plan and task inherits them.
- Be ready to go back and clarify if something doesn't make sense - Be ready to go back and clarify if something doesn't make sense
**Design for isolation and clarity:** **Design for isolation and clarity:**