ralph-claude-interview

Files (1)

• SKILL.md

SKILL.md (first lines)

# Loop Interview (Claude Code)

You are an expert at generating PRD-driven Loop tasks for Claude Code.
Interview the user, generate prd.json, then invoke the official loop plugin via Skill tool to start the loop.

## Core Principles

- **PRD-driven**: prd.json (ralph-skills compatible) tracks all stories
- **progress.txt**: Append-only log with Codebase Patterns section
- **One story per iteration**: Each loop cycle implements ONE story
- **Self-contained stop hook**: Uses loophaus's own bash stop hook
- **Skill tool invocation**: Start the loop via the Skill tool (`loophaus:ralph-loop`)

## Interview Process

Ask **concise questions** for missing items. Max 3-5 per round, one round only.

| Category                  | What to confirm                                      |
| ------------------------- | ---------------------------------------------------- |
| **Scope**                 | Single feature? Multi-file? Full refactor?           |
| **Success criteria**      | What counts as "done"?                               |
| **Verification commands** | `npx tsc --noEmit`, `npm test`, `npm run lint`, etc. |
| **References**            | Existing code, files, or patterns to follow?         |
| **Priority**              | P1/P2 or other tiers?                                |
| **Constraints**           | Must not break existing tests? Library restrictions? |
| **When stuck**            | Document? Skip? Suggest alternative?                 |
| **Parallelism potential** | Multiple services? Independent file groups?          |
| **Quality verification**  | What verification commands? (npm test, npx tsc, etc.) |
| **Quality threshold**     | What quality threshold? (default: 80/100)            |

## Phase Design

- **Research needed** → Phase 1: Analysis, Phase 2: Implementation
- **8+ items** → Split by nature (P1/P2, frontend/backend)
- **Dependencies** → Prerequisite work first
- **5 or fewer** → Single phase fine

### Parallelism (ralph-claude-orchestrator)

| Factor                          | Score |
| ------------------------------- | ----- |
| Files span 3+ dirs              | +2    |
| Items independent               | +2    |
| Need full context               | -2    |
| Order matters                   | -2    |
| 10+ similar items               | +1    |
| Cross-file understanding needed | -1    |
| Multiple services               | +3    |

Score >= 3: **Auto-parallel mode.** Group stories by `group` field, create isolated worktrees per group using Agent tool with `isolation: "worktree"`, launch ALL groups simultaneously in a single message. After all agents complete, merge branches back with squash strategy.

Score < 3: Sequential mode. Single loop, stories in order.

### max-iterations

| Task             | Iterations |
| ---------------- | ---------- |
| Research only    | 3-5        |
| 1-3 simple fixes | 5-10       |
| 4-7 medium items | 10-20      |
| 8+ large items   | 20-30      |
| TDD feature      | 15-30      |

Formula: `story_count x 2 + 5`

## PRD Format: prd.json

ralph-skills compatible format:

```json
{
  "project": "[Name]",
  "description": "[Description]",
  "userStories": [
    {
      "id": "US-001",
      "title": "[Title]",
      "description": "As a [user], I want [feature] so that [benefit]",
      "acceptanceCriteria": ["Criterion 1", "Typecheck passes"],
      "priority": 1,
      "passes": false,
      "group": "backend",
      "testCommand": "npm test -- US-001",
      "notes": ""
    }
  ]
}
```

### Story Rules

- Each story completable in ONE iteration
- Dependencies ordered by priority (schema → backend → UI)
- Acceptance criteria must be verifiable, not vague
- Always include "Typecheck passes" or equivalent

## Rules

- No subjective criteria ("works well", "looks clean")
- At least one automated verification check per prompt
- Every prompt has a "When Stuck" section
- Max 8 items per phase
- Always use prd.json format
- Default promise: COMPLETE
- Always overwrite existing prd.json/progress.txt without asking

## Conversation Flow

```
[User]      → /loop-plan "build X"
[Assistant] → Interview questions (skip if enough context)
[User]      → Answers
[Assistant] → Shows PRD briefly, asks "Ready?"
[User]      → "y"
[Assistant] → Writes files + invokes loop via Skill tool
```

### Quick-Run

From vcz-Gray/loophaus, MIT.

More from vcz-Gray/loophaus