Add new methodology skills for enhanced development workflows

.claude/agents/brainstormer.md

@@ -273,6 +273,24 @@ Starting from fundamentals, what's the best way to solve this?
 - [ ] Feasibility considered
 - [ ] Clear recommendation given
 
+## Methodology Skills
+
+For enhanced interactive brainstorming, use the superpowers methodology:
+
+**Reference**: `.claude/skills/methodology/brainstorming/SKILL.md`
+
+Key principles from superpowers methodology:
+- **One question per message**: Ask single questions, wait for response
+- **Multiple-choice preference**: Provide structured options when possible
+- **YAGNI ruthlessly**: Remove unnecessary features aggressively
+- **Incremental validation**: Present design in 200-300 word chunks
+- **Design documentation**: Output to timestamped markdown files
+
+To use interactive mode, invoke with:
+```
+Use the brainstorming methodology skill for one-question-at-a-time design refinement.
+```
+
 <!-- CUSTOMIZATION POINT -->
 ## Project-Specific Overrides
 

.claude/agents/code-reviewer.md

@@ -177,6 +177,39 @@ I am a senior code reviewer providing thorough, constructive feedback on code qu
 - [ ] No new linting errors
 - [ ] Documentation updated if needed
 
+## Methodology Skills
+
+For enhanced code review workflows, use the superpowers methodology:
+
+### Requesting Reviews
+
+**Reference**: `.claude/skills/methodology/requesting-code-review/SKILL.md`
+
+Include in review requests:
+- Scope definition (files, lines changed)
+- Context (why changes were made)
+- Areas of concern (where to focus)
+- Test coverage summary
+
+### Receiving Reviews
+
+**Reference**: `.claude/skills/methodology/receiving-code-review/SKILL.md`
+
+Process feedback by category:
+- **Critical**: Must fix before proceeding
+- **Important**: Should fix before proceeding
+- **Minor**: Can fix later
+
+### Review Between Tasks
+
+When using subagent-driven development:
+
+**Reference**: `.claude/skills/methodology/executing-plans/SKILL.md`
+
+- Review after each task completion
+- Fresh agent for unbiased review
+- Quality gates prevent proceeding with issues
+
 <!-- CUSTOMIZATION POINT -->
 ## Project-Specific Overrides
 

.claude/agents/debugger.md

@@ -232,6 +232,32 @@ This agent works with:
 - **tester**: To generate regression tests
 - **code-reviewer**: To validate the fix
 
+## Methodology Skills
+
+For enhanced systematic debugging, use the superpowers methodology:
+
+**Reference**: `.claude/skills/methodology/systematic-debugging/SKILL.md`
+
+### Four-Phase Methodology
+
+1. **Root Cause Investigation**: Reproduce, trace, gather evidence
+2. **Pattern Analysis**: Find working code, identify differences
+3. **Hypothesis Testing**: One variable at a time, written hypothesis
+4. **Implementation**: Failing test first, single targeted fix
+
+### Key Principle
+
+**"NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST"**
+
+### Three-Fix Rule
+
+If 3+ consecutive fixes fail, STOP - this is an architectural problem.
+
+### Additional Skills
+
+- **Root cause tracing**: `.claude/skills/methodology/root-cause-tracing/SKILL.md`
+- **Defense in depth**: `.claude/skills/methodology/defense-in-depth/SKILL.md`
+
 <!-- CUSTOMIZATION POINT -->
 ## Project-Specific Overrides
 

.claude/agents/planner.md

@@ -140,10 +140,33 @@ Implement JWT-based authentication with login, logout, and token refresh capabil
 - Password complexity: Define requirements before implementation
 ```
 
+## Methodology Skills
+
+For enhanced detailed planning, use the superpowers methodology:
+
+**Reference**: `.claude/skills/methodology/writing-plans/SKILL.md`
+
+### Detailed Mode (2-5 min tasks)
+
+When `--detailed` flag is used, create superpowers-style plans:
+- **Bite-sized tasks**: 2-5 minutes each (vs standard 15-60 min)
+- **Exact file paths**: Always specify full paths
+- **Complete code samples**: Include actual code, not descriptions
+- **TDD steps**: Write test → verify fail → implement → verify pass → commit
+- **Expected outputs**: Specify command results
+
+### Execution Options
+
+After creating a detailed plan:
+- **Subagent-driven**: Use `executing-plans` skill for automated execution
+- **Manual**: Developer follows plan sequentially
+
+**Reference**: `.claude/skills/methodology/executing-plans/SKILL.md`
+
 <!-- CUSTOMIZATION POINT -->
 ## Project-Specific Overrides
 
 Check CLAUDE.md for:
-- Preferred task sizing (default: 15-60 min)
+- Preferred task sizing (default: 15-60 min, detailed: 2-5 min)
 - Required task metadata
 - Project-specific planning templates

.claude/agents/tester.md

@@ -260,6 +260,43 @@ pnpm test path/to/file.test.ts
 ```
 ```
 
+## Methodology Skills
+
+For enhanced testing practices, use the superpowers methodology:
+
+### Test-Driven Development
+
+**Reference**: `.claude/skills/methodology/test-driven-development/SKILL.md`
+
+Key principles:
+- **NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST**
+- Red-green-refactor cycle (non-negotiable)
+- Delete code written before tests (don't keep as reference)
+- One behavior per test with clear naming
+- Real code over mocks when possible
+
+### Verification
+
+**Reference**: `.claude/skills/methodology/verification-before-completion/SKILL.md`
+
+Before claiming tests pass:
+1. Identify the command that proves assertion
+2. Execute it fully and freshly
+3. Read complete output
+4. Verify output matches claim
+5. Only then make the claim
+
+### Testing Anti-Patterns
+
+**Reference**: `.claude/skills/methodology/testing-anti-patterns/SKILL.md`
+
+Avoid these mistakes:
+1. Testing mock behavior instead of real code
+2. Polluting production with test-only methods
+3. Mocking without understanding dependencies
+4. Creating incomplete mocks
+5. Writing tests as afterthoughts
+
 <!-- CUSTOMIZATION POINT -->
 ## Project-Specific Overrides