Instead of just executing known tasks, use AI to explore the feasibility of complex features. By asking "what's the best way to do this?", the AI provides a ranked list of technical approaches, complete with pros and cons, which helps to de-risk development.

Stakeholders must first interact with an AI agent about their feature ideas. The agent asks clarifying questions to assess impact and alignment. If the idea is weak, the agent politely rejects it, protecting PMs from distractions and poorly framed requests.

You don't need technical skills to build custom AI tools. Frame your needs as problem statements to a capable AI agent. The AI then acts as a product manager, asking clarifying questions to understand the requirements before generating the necessary scripts and workflows to solve your problem automatically.

Ask an AI to write the product spec for a feature. If it feels wrong, re-prompt instead of editing. Then, have the AI generate a prompt for an image generator to create a visual mockup, allowing you to see the feature before committing to code.

Don't ask an AI agent to build an entire product at once. Structure your plan as a series of features. For each step, have the AI build the feature, then immediately write a test for it. The AI should only proceed to the next feature once the current one passes its test.

Use a dedicated AI chat as a dynamic feature backlog. Continuously feed it new ideas and user feedback, prompting the AI to maintain a ranked table of features based on estimated build time and potential impact. This creates a low-friction system for choosing what to build next during focused work sprints.

Most PMs work on existing products, not new ones. Use a specialized LLM skill, like 'Vet a Feature,' to rigorously analyze new feature ideas against anti-patterns and opportunity costs before committing development resources, ensuring you work on the highest-impact items.

Avoid the trap of building features for a single customer, which grinds products to a halt. When a high-stakes customer makes a specific request, the goal is to reframe and build it in a way that benefits the entire customer base, turning a one-off demand into a strategic win-win.

When users request a specific feature, like an API, don't take it at face value. Ask 'why' to uncover the underlying job-to-be-done. The user's goal might be a centralized view of comments, which can be solved with a dedicated feed—a much simpler solution than building a full API.