W Compound

# /w-compound

Compound This - Captures current context as reusable knowledge AND auto-generates diagnostic/fix Ralph candidates for overnight verification.

## Usage

/w-compound [category] /w-compound feature /w-compound bug

---

## ⚠️ MANDATORY EXECUTION

This command MUST complete ALL phases including auto-QA generation.

---

## Categories
- `feature` - Feature implementations
- `bug` - Bug fixes
- `security` - Security improvements
- `performance` - Performance optimizations
- `architecture` - Architecture decisions

## What Gets Stored
1. **Memory Key** - Searchable pattern reference
2. **Solution Doc** - Markdown documentation
3. **Diagnostic Candidates** - RC-D### to verify patterns exist
4. **Fix Candidates** - RC-F### to restore patterns if diagnostics fail

---

## Execution Protocol

### ⛔ CHECKPOINT 0: Category Selection
**REQUIRED OUTPUT:**
- Category selected: _____
- Context to capture: _____

**USER GATE:** Use AskUserQuestion
- Question: "Storing as [category]. Confirm?"
- Options: ["Continue", "Change category"]

STOP and wait for user response.

---

### ⛔ CHECKPOINT 1: Storage Complete (MANDATORY - NEVER SKIP)
**REQUIRED OUTPUT:**
- Memory key: project/[category]/_____
- Doc path: docs/solutions/[category]/_____.md
- Pattern stored: yes/no

**AUTO-PROCEED:** Continue to Analyze Changes phase.

---

### ⛔ CHECKPOINT 2: Analyze Changes (AUTO-PROCEED)
**Parse git diff to identify what was built:**

Run: `git diff --name-only HEAD~1` and `git diff HEAD~1`

**Categorize changes:**
| Change Type | Detection Method |
|-------------|------------------|
| New function | `+ export function` or `+ function` |
| New interface | `+ export interface` or `+ interface` |
| Pattern change | Significant line changes in existing files |
| Test added | Changes in `*.test.*` or `*.spec.*` files |
| Config change | Changes in config/settings files |

**REQUIRED OUTPUT:**
- Files changed: _____
- Functions added: _____
- Interfaces added: _____
- Patterns modified: _____
- Tests added: _____

**AUTO-PROCEED:** Continue to Generate Diagnostics phase.

---

### ⛔ CHECKPOINT 3: Generate Diagnostics (AUTO-PROCEED)
**For each significant change, create RC-D### diagnostic:**

**Diagnostic Template:**
| Change Type | Diagnostic Command | Pass Criteria |
|-------------|-------------------|---------------|
| Function added | `grep -n "export function NAME" FILE` | Match found |
| Interface added | `grep -n "export interface NAME" FILE` | Match found |
| Pattern exists | `grep -rn "PATTERN" PATH` | N matches found |
| Test passes | `npm test -- --grep "NAME"` | Exit code 0 |
| Pattern removed | `grep -rn "OLD_PATTERN" PATH` | 0 matches |

**For each diagnostic, generate:**
```markdown
### RC-D###: [Name] Exists

**Auto-Generated From**: /w-compound on [DATE]
**Type**: Diagnostic
**Verifies**: [description]

**Test Command**:
\`\`\`bash
grep -n "[pattern]" [file]
\`\`\`

**AI-Verifiable Output**:
DIAGNOSTIC: [NAME]
PATTERN_FOUND: YES|NO
LOCATION: [file:line] or NONE
STATUS: PASS|FAIL

**Triggers**: RC-F### if STATUS: FAIL
**Priority**: P2
**Status**: ready

REQUIRED OUTPUT:

• Diagnostics generated: _____ (list RC-D### IDs)

AUTO-PROCEED: Continue to Generate Fix Candidates phase.

---

⛔ CHECKPOINT 4: Generate Fix Candidates (AUTO-PROCEED)

For each diagnostic, create paired RC-F### fix candidate:

For each fix, generate:

### RC-F###: Restore [Name]

**Auto-Generated From**: /w-compound on [DATE]
**Type**: Conditional Fix
**Triggered By**: RC-D### failure
**Priority**: P1 (critical - restores functionality)

**Pattern to Restore**:
\`\`\`[language]
[actual code that was just written]
\`\`\`

**File**: [path/to/file]

**Completion Tests**:
1. Pattern: `[pattern]` exists in `[file]`
2. Test: RC-D### returns STATUS: PASS

**Status**: ready (only runs if RC-D### fails)

REQUIRED OUTPUT:

• Fix candidates generated: _____ (list RC-F### IDs)
• Diagnostic → Fix pairs: RC-D001→RC-F001, etc.

AUTO-PROCEED: Continue to Append phase.

---

⛔ CHECKPOINT 5: Append to Ralph Candidates (AUTO-PROCEED)

Add all generated candidates to .claude/ralph-candidates.md:

1. Read current file to find highest RC-D### and RC-F### IDs
2. Assign sequential IDs to new candidates
3. Append to Active Diagnostics table
4. Append to Active Fixes table
5. Append full details to Diagnostic Details and Fix Details sections

REQUIRED OUTPUT:

• Candidates appended: _____
• New highest RC-D ID: RC-D___
• New highest RC-F ID: RC-F___
• File updated: .claude/ralph-candidates.md

AUTO-PROCEED: Continue to Ralph Candidate Check phase.

---

⛔ CHECKPOINT 6: Ralph Candidate Check (MANDATORY)

Evaluate if this pattern could become a GENERAL Ralph loop (RC-###):

• Is this a repeating dev pattern beyond just this session?
• Could it be templated for future similar work?

If YES - Create General Ralph Candidate (RC-###):

1. Read .claude/ralph-candidates.md for next available RC-### ID
2. Assign priority: P1/P2/P3
3. Define completion tests
4. Add to Active Candidates table

REQUIRED OUTPUT:

• General Ralph candidate identified: yes/no
• If yes: ID, priority, tests, status

NEVER skip this phase. Command is INCOMPLETE without all checks.

---

Completion Checklist

• Category confirmed
• Memory key stored: _____
• Solution doc created: _____
• Changes analyzed
• Diagnostics generated: RC-D___ to RC-D___
• Fixes generated: RC-F___ to RC-F___
• Candidates appended to .claude/ralph-candidates.md
• General Ralph candidate check completed

⚠️ Command INCOMPLETE until all boxes checked

Output Summary

At completion, report:

Compounded: [category] - [name]
Memory: project/[category]/[name]
Doc: docs/solutions/[category]/[name].md
Auto-generated: N diagnostic/fix pairs for overnight Ralph
  - RC-D001 → RC-F001: [description]
  - RC-D002 → RC-F002: [description]
Run /w-ralph-batch to process overnight.

Example

/w-compound