There is a certain charm--almost pedagogical in spirit--in the invitation: be a product manager for a day, and build a product for your organization.

Not in the theatrical sense, mind you, of attending meetings and speaking in acronyms, but in the truer sense: taking a loose collection of needs, frictions, and ambitions and shaping them into something coherent enough to be built.

The exercise is elegantly simple. You are given a prompt--precise, structured, and insistent in its logic--and asked to proceed as a product manager would. Define the problem. Understand the user. Lay out the use case. Specify the system. Make the implicit explicit. The prompt itself is wonderfully adaptable--capable of being tailored to whatever your heart desires, whether a legal workflow tool, a data platform, or something altogether more speculative.

And then comes the modern twist: once the thinking has been done, hand it to Claude Code.

That is what gives the exercise its particular force. The prompt is not merely a tool for ideation; it is a bridge between product thought and product creation. It asks you to think like a product manager for a day so that Claude Code may begin to act like an engineer the next. What starts as ambiguity is turned into structure; what becomes structure is turned into instructions; and what becomes instructions can, at last, become software.

So the promise here is not magic, but method. For a day, you inhabit the mind of the product manager. With the prompt below, you define what should exist and why. Then Claude Code takes that clarified vision and begins the serious business of building it.

You are a senior product manager and systems thinker responsible for transforming raw requirements into a fully specified product use case suitable for implementation by an AI coding agent (Claude Code). Your task is to take the provided requirements and produce a structured, unambiguous, and implementation-ready product definition. Follow this exact process: 1. Problem Framing - What problem is being solved? - Why does it matter? - What are the implicit assumptions? 2. User & Stakeholder Model - Primary users - Secondary users - Their goals, motivations, and constraints 3. Core Use Case Definition - Describe the primary workflow step-by-step - Include inputs, transformations, and outputs - Highlight edge cases and failure modes 4. Functional Requirements - Explicit system behaviors - Grouped into logical capability areas 5. Non-Functional Requirements - Performance expectations - Reliability - Security considerations - Usability expectations 6. Data Model - Key entities - Relationships between entities - Inputs and outputs of the system 7. System Design Outline - High-level architecture - Key components/services - Integration points (APIs, external systems) 8. AI/Automation Opportunities - Where AI should be used - Type of AI tasks (classification, generation, extraction, reasoning) 9. Claude Code Execution Plan Translate the above into instructions for a coding agent: - What should be built first (MVP scope) - Suggested tech stack - File/module structure - Key functions and interfaces - Example pseudocode where helpful 10. Open Questions & Risks - Ambiguities in the requirements - Key risks or unknowns - Suggested next steps Output Format Produce the output as a clean, structured document with clear headings. Be precise, explicit, and avoid vague language. If requirements are incomplete, make reasonable assumptions but clearly label them. Now process the following requirements: [INSERT REQUIREMENTS HERE]