product-os: Command for Claude Code

Create New Project

Create a new experiment/project document using the standard template, complete it through guided conversation, and ensure quality through review criteria and Socratic questioning.

Instructions

Phase 1: Gather Project Information

1. Start the conversation by asking the user for the project/experiment name and a brief description of what they want to achieve.

2. Use Socratic questioning to help the user think through the project. Ask 3-5 questions from the categories below (pick the most relevant):

   Problem Clarity:

   • "What specific user pain point does this solve?"
   • "How do we know this is a real problem? What evidence do we have?"
   • "Who experiences this problem most acutely?"
   • "What's the cost of NOT solving this?"

   Solution Validation:

   • "Why is this the right solution for that problem?"
   • "What alternatives did you consider? Why did you reject them?"
   • "What's the simplest version that solves the core problem?"
   • "How will users discover this feature?"

   Success Criteria:

   • "How will we know if this feature is successful?"
   • "What would make you consider this a failure?"
   • "What metric are we trying to move? By how much?"
   • "What's the adoption target?"

   Constraints & Trade-offs:

   • "What are the technical constraints or risks?"
   • "What are we NOT going to do as part of this?"
   • "What existing features or workflows does this affect?"
   • "If we had half the time/resources, what would we cut?"

   Strategic Fit:

   • "Why is this the right feature to build RIGHT NOW?"
   • "How does this fit into our broader product strategy?"
   • "What happens if we wait 6 months to build this?"
   • "How does this affect our competitive position?"

3. Gather specific template fields through conversation:

   • Objective (clear, measurable goal)
   • Hypothesis (if we do X, then Y will happen because Z)
   • Evidence (user research, data, competitive analysis)
   • Success metric (primary KPI)
   • Secondary metrics
   • Guardrail metrics (what we don't want to negatively impact)
   • ROTI score estimate (Expected impact / dev days)
   • Evaluation plan: what to evaluate, criteria, method (Logfire/manual/hybrid), baseline, frequency, owner
   • Experiment details (if applicable): test type, audience, run time, MDE/ROPE
   • Launch and end dates
   • Solution details: link, scope, build time, out of scope, key assumptions
   • Risks and mitigations: impact, technical, internal, monitoring plans
   • Cross-functional stakeholders
   • Next steps