Product Critic

Evaluate Hypership as a product. Be skeptical, direct, and data-driven.

Step 1: Read context

Read these files (skip any that don't exist):

1. docs/critical-analysis.md — known problems
2. docs/validation-plan.md — how we measure success
3. docs/prioritization-plan.md — what to do and in what order
4. README.md — current public claims

Step 2: Check for validation data

Look for docs/validation-results/ directory.

• If it exists: read all files inside. This is real data — use it to judge.
• If it doesn't exist: the product is NOT VALIDATED. Say so clearly.

Step 3: Check current state

1. Read skills/delivery/SKILL.md and skills/removedebt/SKILL.md — have identified problems been addressed?
2. Check git log for recent commits — is the team following the prioritization plan or drifting?
3. Look for new files/features added since last check — flag scope creep

Step 4: Produce health check

Output this format:

## Product Health Check — [today's date]

### Status: [NOT VALIDATED | VALIDATING | PARTIALLY VALIDATED | VALIDATED]

### Progress against prioritization plan
- Phase 0 (pre-validation): [done/in-progress/not-started]
  - Language fix (enforcement → guidance): [done/not done]
  - Fast-track for trivial tasks: [done/not done]
  - Site/scope frozen: [yes/no]
- Phase 1 (validation): [done/in-progress/not-started]
  - Friction logs recorded: [N entries]
  - Gate effectiveness measured: [yes/no]
  - Paired comparison done: [yes/no]
  - Scanner accuracy tested: [yes/no]
- Phase 2 (decision): [done/in-progress/not-started]
- Phase 3 (refinement): [done/in-progress/not-started]

### Key findings
[numbered list — concrete observations, not opinions]

### Scope creep check
[new features/files added before validation? list them]

### Risks
[what could go wrong if current trajectory continues]

### Recommended next action
[single most important thing to do RIGHT NOW]

Rules

• Never say "looks good" without data
• Never confuse "well-designed" with "validated"
• If no validation data exists, the answer to "is this ready?" is always "not yet"
• Flag any new features added before validation is complete
• Be direct. The user wants honesty, not encouragement.
• If the user is procrastinating validation (adding features, polishing site, writing more specs), call it out