Product Manager Role Prompt
A complete 'act as a product manager' role prompt — the perspective, responsibilities, and decision criteria a real PM brings, not just the job title.
Make AI act as a software architect — system design, scalability, service boundaries, and trade-offs — instead of jumping straight to code.
Ask an AI to design a system and it tends to start typing code; ask it to act as a software architect and you get the decisions that come first — the boundaries, the non-functional requirements, and the trade-off behind each call. This generates a role prompt that fixes the AI as a principal software architect: expensive-to-reverse decisions get the judgment, every quality attribute is weighed against another, and each design states its assumptions and the failure mode it guards against. Open it in the Role Prompt Generator to adjust the seniority level, industry, and focus areas.
Open the example in the tool
It loads with realistic inputs already filled in.
Swap in your own details
Adjust the inputs and options to match your case.
Generate and copy
Produce the output and paste it where you need it.
It makes the AI answer like a principal software architect, presenting each design as the forces at play, the options, the chosen structure, and the trade-off that choice accepts. It states its assumptions about scale and team and names the failure mode each decision guards against, weighting attention toward system design and explicit trade-off analysis rather than jumping straight to code.
Give it the actual system or decision you are weighing, plus the real load and growth curve, the team that will run it, and the constraints that bind you. It judges fitness for your actual load, reversibility, and whether your team can build and operate the design — vague inputs get vague trade-offs. Open it in the Role Prompt Generator to set seniority, industry, and focus areas first.
No — it gives you an architect's critique and the trade-offs behind each option, but you make the call and you build it. Run the role prompt in your own AI tool to pressure-test a design; it names the forces, the alternatives, and the accepted trade-off, and it won't write the implementation itself. The final architecture decision, and the code, stay yours.
A complete 'act as a product manager' role prompt — the perspective, responsibilities, and decision criteria a real PM brings, not just the job title.
An expert startup advisor role prompt — stage-aware, capital-efficiency-minded, and built to name the riskiest assumption in any plan instead of cheering it on.
Choose how users prove who they are — sessions vs tokens, passwords vs passwordless, SSO and MFA — decided on your real constraints, not the default tutorial.
Convert scattered bug notes, Slack messages, or user complaints into structured engineering tasks with reproduction steps, severity, and root cause hypothesis.
'Make it good', 'be detailed', 'keep it interesting' — vague prompts get vague output. The fix is mechanical: replace every fuzzy word with a checkable instruction.
A reusable AI agent task template with variables for objective, context, available tools, constraints, success criteria, failure handling, and output format.
Generate expert role prompts — perspective, responsibilities, and decision criteria, not just "act as".
The full path from idea to a shipped SaaS MVP — define and scope the requirements, design the architecture, API, and data model, then build it reviewed, tested, secured, cost-controlled, and deployed.
The full path to a backend you can put clients on — define the requirements, design the architecture, API contract, data model, and access control, then build it reviewed, tested, secured, and shipped.
Design a system's architecture on its real trade-offs instead of a confident diagram — put the model in an architect's seat, work the decisions one at a time, and write down the why.
Design an API on its contract instead of discovering it endpoint by endpoint — model the resources, design the endpoints and payloads, pin the contract, then review it before code locks it in.
Design a schema on its data, not a hunch — model the entities and relationships, set the constraints that protect integrity, plan indexes around real queries, then document the schema and migration.
Connect systems so they don't break each other — map the integration boundaries, design the event and webhook contracts, plan retries and failure handling, then document the integration.
Organize a site so people and crawlers find things — inventory the content, group it into a real hierarchy, design the sitemap and navigation, then document the information architecture for the build.
AI hands you a clean recommendation that reads as ready to use — and never shows you which assumption breaks it, which edge case sinks it, or what needs a human's eyes. Here's how to run a separate risk pass on an answer before you accept it.
Four sentences of requirements go in, a confident schema comes out — and it quietly decided three things nobody decided. Here's how to turn real domain rules and access patterns into a reviewable database schema, with the modeling gaps named as open questions instead of guessed.
Code you can refactor on a quiet afternoon. A field you shipped is somebody else's dependency — you don't fix it, you version it. What an hour of contract review buys: method semantics, a truthful error model, retries, authorization, and compatibility you didn't mean to promise.
In year three someone finds the queue and asks why it's there. Nobody left knows. An ADR is the note that answers them — the constraint that eliminated the alternative, the consequences you accepted on purpose, and what would have to change for the decision to be wrong.