// Read iteration state
const state = JSON.parse(fs.readFileSync('.ralph_state.json', 'utf8'));
console.log(`Executing iteration ${state.currentIteration}`);

// Read PRD
const prd = JSON.parse(fs.readFileSync('prd.json', 'utf8'));
const stories = prd.userStories.filter(s => !s.passes);
console.log(`${stories.length} stories remaining`);

// Read patterns
const rootPatterns = fs.readFileSync('CLAUDE.md', 'utf8');
// Parse and internalize patterns before starting work

BRANCH=$(jq -r '.branchName' prd.json)
CURRENT=$(git branch --show-current)

if [ "$CURRENT" != "$BRANCH" ]; then
  # Check if branch exists
  if git show-ref --verify --quiet refs/heads/$BRANCH; then
    git checkout $BRANCH
  else
    git checkout -b $BRANCH
  fi
fi

## Codebase Patterns

- Use sql<number> template for aggregations
- Always use IF NOT EXISTS for migrations  
- Export types from actions.ts for UI components
- Tests require dev server on port 3000

const nextStory = prd.userStories
  .filter(s => !s.passes)
  .sort((a, b) => a.priority - b.priority)[0];

if (!nextStory) {
  // All stories complete!
  createCompletionSignal();
  return;
}

console.log(`Implementing: ${nextStory.id} - ${nextStory.title}`);

CREATE TABLE IF NOT EXISTS tasks (
  id INTEGER PRIMARY KEY,
  status TEXT DEFAULT 'pending'
);

# Typecheck
npm run typecheck  # or tsc --noEmit, or your project's command

# Lint
npm run lint  # or eslint ., or your project's command

npm test  # or your project's test command

I need to verify the UI changes in the browser.

Load dev-browser skill and:
1. Navigate to [page URL]
2. Check that [specific UI element] is visible
3. Verify [specific behavior] works
4. Take screenshot if helpful

## Database Patterns

- Always use IF NOT EXISTS for table creation
- Use transactions for multi-step operations
- Column names: snake_case, table names: plural

## API Patterns

- All server actions return { success, data?, error? }
- Use sql<number> template literal for parameterized queries
- Validate input with Zod schemas before queries

## UI Patterns

- Import types from @/lib/actions (never duplicate)
- Use <Badge variant="..."> for status indicators
- Form submissions use useTransition for loading states

git add .
git commit -m "feat: ${STORY_ID} - ${STORY_TITLE}"

git commit -m "feat: US-002 - Display priority indicator on task cards"

const prd = JSON.parse(fs.readFileSync('prd.json', 'utf8'));

// Find and update the story
const storyIndex = prd.userStories.findIndex(s => s.id === completedStoryId);
prd.userStories[storyIndex].passes = true;

// Write back
fs.writeFileSync('prd.json', JSON.stringify(prd, null, 2));

## 2026-01-13 14:30 - US-002

Iteration: 3

**Implemented:**
- Added priority badge component to task cards
- Color coding: red=high, yellow=medium, gray=low
- Badge visible without hover/click

**Files Changed:**
- components/TaskCard.tsx - Added <Badge> with priority colors
- lib/types.ts - Exported Priority type

**Learnings for future iterations:**
- Badge component already exists at components/ui/badge.tsx, reused it
- Priority colors defined in tailwind.config.ts, matched existing palette
- Card layout uses CSS Grid, added badge to header slot

**Quality Checks:**
- ✅ Typecheck passed
- ✅ Lint passed  
- ✅ Verified in browser - badges display correctly

---

echo "All user stories completed at iteration $(jq -r '.currentIteration' .ralph_state.json)" > .ralph_complete

🎉 All Ralph stories completed! All user stories have passes=true.

rm -f .ralph_trigger

✅ Story US-002 completed. 3 stories remaining.

# [Module/Directory Name] - Claude Patterns

## Overview
Brief description of what this directory/module does.

## Patterns

- Pattern 1: When doing X, always do Y
- Pattern 2: Use Z pattern for all A operations
- Pattern 3: Component B expects data in format C

## Gotchas

- Gotcha 1: Don't forget to update D when changing E
- Gotcha 2: Field names must match template exactly
- Gotcha 3: This module runs before F, so G isn't available yet

## Dependencies

- Depends on: ../other-module for shared types
- Exports: Used by UI components in /app
- External: Requires API_KEY environment variable

## Examples

[Optional - helpful code snippets]

## Last Updated

YYYY-MM-DD - [Brief context of what was learned]

# Database Layer - Claude Patterns

## Overview
Database schema, migrations, and query utilities using better-sqlite3.

## Patterns

- Use sql<number> template literal for parameterized queries (prevents SQL injection)
- Always include IF NOT EXISTS in CREATE TABLE statements
- Migrations in db/migrations/, numbered sequentially
- Use transactions for multi-step operations

## Gotchas

- Run migrations before starting dev server (npm run db:migrate)
- Schema changes require new migration file, don't edit existing ones
- INTEGER PRIMARY KEY gives auto-increment behavior in SQLite
- TEXT columns need explicit DEFAULT if required

## Dependencies

- Depends on: better-sqlite3 package
- Exports: Used by lib/db.ts (connection pool)
- Schema: Defined in db/schema.sql

## Examples

```typescript
// Good: Parameterized query
const tasks = db.prepare(
  sql`SELECT * FROM tasks WHERE status = ?`
).all(status);

// Bad: String concatenation
const tasks = db.prepare(
  `SELECT * FROM tasks WHERE status = '${status}'` // SQL injection risk!
).all();

---

## Common Mistakes to Avoid

### ❌ Don't Skip Pattern Reading

Reading CLAUDE.md and progress.txt patterns is NOT optional. Skipping this leads to:
- Repeating mistakes from previous iterations
- Breaking existing patterns
- Wasting time rediscovering solutions

### ❌ Don't Make Stories Too Big

If a story can't be completed in one iteration, it's too big. But you can't split it mid-iteration. If you realize this:
1. Complete what you can
2. Note in progress.txt that story needs splitting
3. User can manually split it for next run

### ❌ Don't Skip Quality Checks

NEVER commit without running:
- Typecheck
- Lint
- Tests (if story has testable logic)
- Browser verification (if UI changes)

Broken commits break the autonomous loop.

### ❌ Don't Forget to Update All Files

After completing a story, you MUST update:
- [ ] prd.json (set passes: true)
- [ ] progress.txt (append entry with learnings)
- [ ] CLAUDE.md (if patterns discovered)
- [ ] .ralph_trigger or .ralph_complete (signal status)

Missing any of these breaks the loop.

---

## Debugging

If something goes wrong:

### Check State Files

```bash
# Current iteration
cat .ralph_state.json

# Stories remaining  
jq '.userStories[] | select(.passes == false) | .id' prd.json

# Recent progress
tail -n 50 progress.txt

# Uncommitted changes?
git status

# Recent commits
git log --oneline -5

# On correct branch?
git branch --show-current