ai-native-product-building
AI-native product building shifts the Product Manager’s role from writing requirements for others to directly directing an AI agent to build the software. This approach reduces development time from months to weeks and costs by up to 99%.
The "JIRA-Prompt" Framework
Treat every interaction with an AI agent (like Bolt) as if you are writing a high-quality ticket for a senior developer.
1. Define the Technical Scope
Instead of general descriptions, provide the specific parameters the AI needs to spin up the environment:
- Identify the Core Functionality: "Make a Spotify clone with streaming, playlists, and MP3 file support."
- Specify the Stack: State the desired integrations (e.g., "Use Supabase for the database and Netlify for hosting").
- Provide Data Context: Paste raw data (e.g., LinkedIn bio, CSV rows, or brand guidelines) directly into the prompt to give the AI context.
2. Balance Specification with "Vibes"
AI agents perform best when given a mix of rigid requirements and creative freedom.
- High Specificity: Use this for business logic, data schemas, and user flows.
- The "Vibe" Prompt: For UI/UX, use descriptive language rather than specific CSS.
- Example: "Make it look like a high-end medical donation site—clean, professional, and trustworthy."
- Example: "Make it prettier and more modern."
3. Implement Iterative Debugging
More from samarv/shanon
agentic-workflow-automation
Transition from static LLM chats to autonomous agents that execute multi-step tasks. Use this when you need to automate cross-platform reports (e.g., Snowflake to Google Docs), build self-service tools for non-technical teams, or create "anticipatory" engineering workflows that draft PRs based on Slack discussions.
63b2b-value-negotiation
A framework for defending price and extracting maximum value in B2B sales. Use this skill when a prospect asks for a discount, when transitioning a POC to a commercial deal, or when presenting high-ticket pricing to budget-conscious stakeholders.
18niche-market-opportunity-mapping
A framework for identifying high-margin, low-competition business ideas ("fishing holes") by leveraging personal unfair advantages and avoiding overcrowded markets. Use this when vetting a new startup idea, choosing a niche for a service business, or seeking to pivot an existing product into a more profitable segment.
17b2b-saas-workflow-strategy
A framework to evaluate the market potential and strategic direction of B2B products based on workflow frequency and organizational breadth. Use it when validating a new startup idea, evaluating a product's "ceiling," or planning a pivot to increase market share.
14agentic-engineering-workflow
Transition from a hands-on "bricklayer" to a high-level "architect" by managing a fleet of autonomous AI agents. Use this when you need to scale engineering output with a small team, handle repetitive migrations/bug fixes, or onboard engineers to complex legacy codebases.
10b2b-category-creation-strategy
A framework for determining when to create a new software category versus winning an existing one, and the tactical steps to define and validate that category. Use this when your product is too disruptive for current labels, when existing categories have negative associations, or when you need to expand your TAM.
9