Pocket Pitching

Pre-grinding problem exploration. Scans project context before making project-specific claims, picks 3-5 brainstorming methods based on problem type, runs them with independent advisor curation, investigates technical unknowns that could change the approach, then produces a pitch exploration doc with a problem statement and 2-3 approach directions.

Core principle: Diverge first, converge second. Never propose solutions until the problem is fully explored.

Start from the user's request. Use clear instructions, corrections, and approvals already given; do not ask the user to repeat them or select a numbered option. Ask only when an unanswered product decision or fact would materially change the exploration. Otherwise, inspect available context, proceed, and label any assumption that affects the result.

When to Use

Trigger when:

• Problem is vague, unformed, or needs exploration before spec-writing
• User says "pitch", "explore", "I have a rough idea", "help me think through this"
• Starting a new feature with no clear direction

Do NOT use:

• When problem is already clearly defined (use pocket-grinding)
• When a spec already exists (use pocket-grinding or pocket-planning)
• For "brainstorm" keyword — pocket-grinding owns that trigger