propose turns “I have an idea” or “what next” into evidence before any build. The agent reads what you shared and the product’s existing record, researches alternatives, segments and what people say, and checks feasibility before drawing screens.
The result is one self-contained HTML proposal. Each claim is marked as observed fact, owner preference, agent inference or unsupported assumption, and it carries its source and the date it was read. It is not for agreed changes or bugs.
What You Get
- One HTML page holding research, alternatives, segment, value proposition and curve, recommendation, jobs map, key screens, open decisions and hypotheses
- Every claim marked by kind with its source and read date
- One recommended direction with rough builder-hour size and what it adds to run
- The weakest consequential assumption and the customer experiment that would test it
Common Use Cases
- Judging whether an idea is worth building
- Deciding the next step for a product that already has users
- Running standalone market research on competitors, segments and value proposition
- Reviewing key screens before a plan is written
What Makes It Unique
The skill treats every output as a hypothesis until people use and pay, separates the owner’s preference (a decision) from the owner’s assertion (a hypothesis), and asks questions last. The owner sees high-fidelity key screens before any plan. Quotes from vendors, staff or paid posts are left out. It orchestrates the competitor-analysis, market-segments, beachhead-segment, value-proposition and value-curve skills and the ui-design skill for screens.
Under The Hood
The skill is a SKILL.md of instructions with one reference file, references/proposal.md, which describes the page sections, and a receipts.md of rule origins. It tells the agent to search the web and fetch pages, reviews, forums, Reddit and X, to read the repository’s notes, briefs and decision log, and to check APIs and platform rules for feasibility. It writes the proposal as an HTML file in the repository (docs/product/proposal.html by default), removes an older Markdown proposal, updates the brief and decision log, and publishes the page as an artifact where the host supports it. It also asks for a fresh session to read page screenshots. It ships no scripts.