Orc Discover

---
description: Codebase discovery for orc planning workflow. Analyzes patterns without user interaction.
argument-hint: [slug]
allowed-tools:
  - Read
  - Write
  - Glob
  - Grep
  - Bash(ls:*)
  - Bash(find:*)
  - Bash(rg:*)
  - Bash(wc:*)
  - Bash(git:*)
model: inherit
context: fork
hooks: {}
user-invocable: false
---

# Orc Discover

Codebase exploration that runs forked (non-interactive).

## Input

- **$ARGUMENTS** — Plan slug

## Template

See [templates/STATE.md](templates/STATE.md) for output format.

## Process

### Step 0: Validate Slug

Tree the plans directory at depth 1 to see existing plan directories:
```bash
tree .claude/plans -L 1 -d
```

Compare the tree output against the provided `$ARGUMENTS` slug. If the slug matches a directory exactly, proceed with that directory. If it doesn't match exactly but a visible directory is clearly the right one (typo, case variation, truncation), use that directory instead. Use the matched directory path for all subsequent steps.

### Step 1: Load Vision
```
Read .claude/plans/$ARGUMENTS/PROJECT.md
```
Extract search targets from vision.

### Step 2: Pattern Discovery

Use Glob and Grep. **Find 2-3 examples of each** (emphasized: depth matters):
- Similar existing functionality
- File/test naming conventions
- API/route patterns
- Error handling patterns

### Step 3: Convention Analysis

For discovered files, document with file:line references:
- Code style (naming, organization)
- Error handling approach
- Testing patterns

### Step 4: Integration Mapping

For each file to modify:
- Current purpose
- What will change
- Dependencies (via `rg "import.*filename"`)
- Risk level (H/M/L)

### Step 5: Write STATE.md

Write `.claude/plans/$ARGUMENTS/STATE.md` using template.

Include these required sections:
- **Current Phase** — Track progress state
- **Decisions Made** — Audit trail for architectural choices
- **Blockers** — Surface impediments early

## Constraint

Cannot use AskUserQuestion — forked context is non-interactive.

## Completion Criteria

- [ ] Found 2-3 examples of similar patterns
- [ ] Documented all files to modify with risk levels
- [ ] Identified integration points
- [ ] Surfaced risks with mitigations