Daedalus Product Incubator

The problem it solves

Product planning often stalls when an idea is vague, requirements are scattered, and cost or risk remains unclear. This skill is aimed at users without a strong engineering background who want to turn “I have a product idea” into an actionable PRD. Instead of making technical judgments for the user, it uses a controlled conversation to collect context: user pain points, product preferences, competitor references, V1 boundaries, cost paths, and risk categories. For non-experts, this approach is easier to converge on than asking a model to write requirements directly.

How it works

• Turn-driven flow: Progresses by user reply count. Round 1 asks about scenarios and preferences, round 2 adds 👍 highlights and ⚠️ watchouts, and round 3 produces a cost threshold assessment, competitor references, and compliance risk notes.
• State tracking: Maintains context fields such as user_idea, core_value, must_haves, and risk_reminded to avoid repetitive questions and keep later documents consistent.
• Risk layering: Separates compliance risks from product security risks, and triggers a second review when new features enter areas that have not been addressed yet.
• Structured output: Once the user confirms “start building” or the maximum turn count is reached, it generates a Markdown PRD that can be imported into tools like Cursor or v0.dev for further development.

Boundaries to keep in mind

Best suited for early-stage product incubation, requirement clarification, and lightweight MVP planning. It does not execute code, design interfaces, or provide definitive legal advice. Features involving location tracking, user-generated content, finance, health, or other high-risk areas should be reviewed separately by qualified compliance professionals.