Claude Code for Product Managers with Sachin Rekhi

Use Claude Code to decode any legacy feature you inherit
Point it at the relevant folders and ask:
“Explain this feature’s flow like I’m a PM, from user action to database, including main edge cases.”

Co‑design data models and specs before you brief engineering
Paste your user story and ask:
“Propose a data model, APIs, and validation rules for this feature. Highlight 5 risks or trade‑offs I should discuss with engineering.”

Ask Claude where your change will ripple through the system
Give it the function you want to change plus related files and ask:
“If we change this logic, where else in the system will be affected, and what rollout plan + tests do you recommend?”

Turn PR diffs into a PM‑friendly test checklist
Paste the diff and ask:
“Summarize what changed in user‑visible behavior, and list 5 scenarios a PM/QA should manually test before launch.”

Use Claude as a growth‑experiment ideation partner
Share your current metrics or a dashboard export and ask:
“What patterns do you see, and what 3 experiment ideas would you run next to move metric X?”

Compare spec vs implementation any time they feel out of sync
Paste both the spec and key implementation files, then ask:
“Where does the code diverge from this spec, and what should we update: the spec, the code, or both?”

Compress long modules into 1‑page PM briefs
For big files, ask:
“Summarize this module as a diagram + bullets for a PM. What questions should I ask the team about this design?”

Generate a concrete test case list for each feature
Give Claude Code your feature description and ask:
“List 10 concrete test cases (inputs + expected behavior) that cover happy path, edge cases, and failure states.”

Add guardrails so Claude admits when context is missing
Include something like:
“If you’re not sure, say ‘not enough context’ and tell me which files or logs you need instead of guessing.”

Save your best prompts and turn them into a reusable PM toolkit
Tomorrow, pick one real feature, run steps 1–4 above with Claude Code, then save the 2–3 prompts that work best into your personal template library and reuse them for every future project.