SuperAPI AI Directory

product-plan

General & other

View repository

Updated 10-16 08:10

About this skill

Product Plan

Step 1: Read the project

Before asking anything, gather all available context:

Ideation output — read .harness/product/idea.md if it exists:

  • Extract: concept, problem, market landscape, competitor list, viability verdict
  • These questions are already answered — do not re-ask them in the interview

Existing product docs — read .harness/product/ for prior decisions to update rather than re-litigate

Codebase — if code already exists:

  • Read README.md for stated goals and audience
  • Scan the feature surface: routes, screens, commands, or API endpoints
  • Check the roadmap or issue tracker if present (gh issue list)
  • Note what's implemented, what's stubbed, and what's conspicuously absent

Starting mid-flow on an existing project: if code exists but .harness/ is absent, treat this as step 2 — /ideate was skipped. Read the codebase and README to reconstruct what idea.md would have said, then proceed.

Synthesize into a one-paragraph internal picture. Do not share this — use it to skip already-answered questions and form sharper hypotheses.

Step 2: Interview

Interview the user relentlessly — one question at a time. For every question, state a concrete recommendation or hypothesis first. Never ask a bare question. Lead with your position — "My read is X. Do you agree?" — so the user reacts to a specific claim.

Be a realist, not a cheerleader. Surface the truth, not validation: name failure modes, push back on optimistic answers, make vague audiences concrete, call out weak moats.

Work through these dimensions in order; skip any already answered. See REFERENCE.md for detailed questions per dimension:

  1. The idea
  2. Target audience
  3. Market and competition (skip if idea.md covers it)
  4. Value and differentiation
  5. Validation
  6. Features
  7. UX and design

Step 3: Report

After the interview, produce a report with these sections:

  • Audience — who it's for, who the early adopter is, why they care
  • Market Positioning — category, differentiation, competitive gap
  • Competitive Analysis — top 3–5 competitors, strengths, weaknesses
  • Direction Assessment — go / conditional go / no-go with 2–3 reasons
  • Prioritized Feature Backlog — must-have / should-have / nice-to-have
  • UX and Design Direction — core workflow, interaction model, design register
  • Key Risks — 2–3 assumptions most likely to be wrong and how to test them

Step 4: Write docs

Spawn a subagent to write all product docs. Pass the full report as context — it cannot read the conversation.

Rules: all files go under .harness/product/; update existing rather than overwrite; omit sections with no source; never link to .harness/ from public docs.

The subagent writes: product.md, roadmap.md, competitors.md, ux.md (if UI discussed), and CONTEXT.md (domain glossary). See REFERENCE.md for templates.

After the subagent finishes, confirm every file written. Recommend: "Run /dev-plan to define the architecture and generate feature specs."