collect

/collect

Capture a complete problem state through guided conversation. Probes all three layers: optimization, market-making, and experience. Outputs problem-state.yaml.

Pipeline Position

• Requires: nothing (entry point)
• Produces: $PROBLEMS_ROOT/$ARGUMENTS/problem-state.yaml
• Advances: collect → complete

Instructions

1. Load ${CLAUDE_PLUGIN_ROOT}/templates/PROBLEM_TEMPLATE.md for the structure to fill.
2. If $ARGUMENTS is provided, use it as the problem name. Otherwise ask.
3. Walk the user through each section of the problem-state schema:
   • Core: problem, domain, actors, archetype
   • Layer 2 (optimization): objective, measurables, constraints, paradigms, uncertainty
   • Layer 1 (market-making): cold start, density, growth, network effects, economics
   • Layer 3 (experience): social model, communication, trust/safety, habits, onboarding
   • Behavioral: incentive risks, loss aversion, social preferences, temporal patterns
   • Environmental: weather, seasonality, venue dynamics
   • Infrastructure: scale, hosting, requirements, compliance
4. For each section: ask focused questions, detect gaps, suggest defaults where reasonable.
5. Set maturity markers based on what the user can specify vs. what's unknown.
6. Write the completed problem-state.yaml.
7. Update pipeline-state.json: set collect status to complete, current_stage to formalize.