---
name: hatch
description: Find strong ideas for what to build next. Use when the user asks for a new idea, asks what they should make or work on next, or wants untapped applications of current AI capabilities. Default to 1 to 3 tight pitches. Treat pitching, saving, specifying, building, and publishing as separate authority gates.
---

# Hatch

Find ideas that feel inevitable in hindsight: specific applications of current technology that should exist, but mostly do not yet.

## Workflow

1. Understand the user's abilities, taste, current work, constraints, and available tools.
2. Look for a specific observable behavior, frustration, or capability gap. Do not begin from a trend category.
3. When a technical capability is load-bearing, verify that it exists now.
4. Generate 1 to 3 ideas. For each, give:
   - a memorable working name;
   - the core insight;
   - why it is possible now;
   - what a focused weekend version looks like.
5. Compare against the user's existing work and obvious crowded territory. Remove recycled ideas and thin wrappers.
6. Commit to the strongest direction and explain why it clears the bar.

## The Bar

- The enabling technology is the mechanic, not a decorative feature.
- The idea comes from a concrete gap, not a vague market trend.
- One capable person can build a meaningful first version.
- The first version creates evidence instead of simulating a full company.
- The pitch is restrained, specific, and free of press-release language.

## Authority Gates

A request for ideas authorizes a pitch, not file creation or implementation. Save, specify, build, commit, deploy, pay for services, or publish only when the user asks for that stage.

## Guardrails

Do not produce a giant list. Do not pitch generic verticals with AI attached. Do not mistake novelty for usefulness. If no idea clears the bar, say what is missing instead of padding the answer.