Skip to content
SkillModel-led3,188 tokens in use

propose

Research an idea, then propose what to build in one HTML page with sourced claims, key screens, open decisions and a recommendation.

680 stars on the repository MIT Licensephuryn/product-engineering · product/skills/propose
claude plugin install product@product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing propose costs

41tokens idle
3,188tokens in use
5,311tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure25/25
  • Examples3/15
  • Output10/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers