Agent skill

Prd V02 Product Type Classification

by mattgierhart in mattgierhart/PRD-driven-context-engineering

Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape.

MITAuto-check passedProduct & Project Management

Install Prd V02 Product Type Classification

skills CLI
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-product-type-classification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v02-product-type-classification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-v02-product-type-classification .claude/skills/prd-v02-product-type-classification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prd-v02-product-type-classification
GitHub stars
180
Token cost
~1.8k tokens
SKILL.md length
457 words
Files
5 (incl. references, assets)
Skills in repo
45
Repo updated
First seen
Licence
MIT

At a glance

Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape.

  • Works in 5 steps: Claiming Innovation when it's really… → Undercut without price evidence: Must… → Slice without ecosystem validation:… → …
  • PRD v0.2 work after competitive analysis
  • SKILL.md covers Consumes, Produces, Six Product Types and Classification Decision Flow, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prd V02 Product Type Classification is an agent skill from mattgierhart/PRD-driven-context-engineering. Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Triggers on PRD v0.2 work after competitive analysis, or when user asks "what type of product should we build?", "should we clone or innovate?", "is this a fast-follow opportunity?", "how should we position against competitors?", "clone vs undercut", "unbundle vs slice", or requests help choosing product strategy. Outputs BR- entries for product type classification and inherited…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `assets/classification.md`, `references/decision-framework.md` and `references/examples.md`).

It sits in Product & Project Management, covering PRD writing, Competitor analysis and Go-to-market strategy. The repository describes itself as: PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD… The licence is MIT.

When your agent uses it

  • PRD v0.2 work after competitive analysis
  • User asks what type of product should we build?
  • Should we clone
  • Is this a fast-follow opportunity?

Example prompts

  • “what type of product should we build?”
  • “should we clone or innovate?”
  • “is this a fast-follow opportunity?”
  • “/prd-v02-product-type-classification”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, WebSearch, WebFetch

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Claiming Innovation when it's really Clone: If competitor exists with revenue, you're not innovating
  2. Undercut without price evidence: Must show 60%+ reduction is possible AND sustainable
  3. Slice without ecosystem validation: Platform must actually want third-party apps
  4. Wrapper without API access confirmed: Technical feasibility must precede classification
  5. Unbundle from small platform: Only works against large horizontal players

What it can do on your machine

Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • WebSearch
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd V02 Product Type Classification loads about 1.8k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 457 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 457 words, ~1,817 tokens.

Download SKILL.mdSave it as .claude/skills/prd-v02-product-type-classification/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
prd-v02-product-type-classification
description
Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Triggers on PRD v0.2 work after competitive analysis, or when user asks "what type of product should we build?", "should we clone or innovate?", "is this a fast-follow opportunity?", "how should we position against competitors?", "clone vs undercut", "unbundle vs slice", or requests help choosing product strategy. Outputs BR- entries for product type classification and inherited GTM constraints.
allowed-tools
Read, Write, Edit, Glob, Grep, WebSearch, WebFetch
context
fork

Product Type Classification

Position in HORIZON workflow: v0.2 Competitive Landscape → v0.2 Product Type Classification → v0.3 Outcome Definition

Consumes

This skill requires prior work from v0.2:

  • Landscape map artifact (from Competitive Landscape Mapping) — Current behavior documentation, feature matrix, competitor analysis
  • CFD-* entries (competitive intelligence, from Competitive Landscape Mapping) — Evidence from 3+ direct competitors + adjacent solutions
  • BR-* positioning rules (from Competitive Landscape Mapping) — Constraints derived from competitive analysis

This skill assumes v0.2 Competitive Landscape is complete with documented landscape analysis.

Produces

This skill creates/updates:

  • BR-* entries (product type classification) — Decision record showing which of the six types this product is
  • BR-* entries (GTM constraints inherited from type) — Pricing, channel, scope, and timeline implications of the chosen type
  • Product type artifact — Named decision: "We are building a [Type] product because [specific evidence from landscape]"

Example product type classification entry:

markdown
BR-042: Product Type Classification

Type: Classification Decision
Date: 2026-02-01
Confidence: 70% (source: competitive-landscape-analysis + 3-customer-interviews)

Classification: UNDERCUT
Rationale: All 3 direct competitors (Notion, Linear, Figma) serve enterprise/mid-market first; SMB segment underserved. We can deliver 80% of feature set at 40% price for SMB-specific workflows.

Evidence:
  - CFD-015 (landscape): "All competitors start at $50/user/month enterprise pricing"
  - CFD-018 (landscape): "3 SMB teams using workarounds because pricing doesn't fit budget"
  - CFD-001 (value hypothesis): "$12,500/year value for 5 core features only"

GTM Constraints (inherited):
  - Pricing: Must be <$200/user/month to justify switching
  - Channel: Direct sales to SMB, not marketplace/enterprise
  - Scope: Ruthlessly cut features; 5 core + 3 differentiators max
  - Timeline: Fast iteration with SMB feedback; can't outspend enterprise marketing

Six Product Types

TypeDefinitionWhen Evidence Shows
CloneCopy proven product, execute betterLeader validated market; weak moat; execution gap
UnbundleExtract one category from horizontal platformMulti-category platform does your thing poorly
UndercutSame product, simpler + cheaper for nicheTool overserves broad market; 60%+ price gap possible
SlicePlugin/extension in existing ecosystemPlatform has marketplace; users already there
WrapperAI/API layer on existing data/toolsMiddleware gap between tools; data accessible
InnovationNew solution to known problemExisting approaches fundamentally broken; high pain

Classification Decision Flow

START: What does v0.2 Competitive Landscape show?

Q1: Is there a dominant horizontal platform doing many things?
    YES → Does it do YOUR thing poorly? 
          YES → UNBUNDLE (extract the vertical)
          NO → Continue to Q2
    NO → Continue to Q2

Q2: Is there a single-purpose leader with validated market?
    YES → Can you price 60%+ lower for a niche?
          YES → UNDERCUT
          NO → Can you execute better (speed/UX)?
                YES → CLONE
                NO → Continue to Q3
    NO → Continue to Q3

Q3: Does target customer live in a platform ecosystem?
    YES → Does platform have marketplace/app store?
          YES → SLICE (build extension)
          NO → Continue to Q4
    NO → Continue to Q4

Q4: Is there a data/API integration gap between tools?
    YES → Is the data accessible (API/scraping)?
          YES → WRAPPER
          NO → Continue to Q5
    NO → Continue to Q5

Q5: Are existing solutions fundamentally broken?
    YES → Is pain severe enough for education investment?
          YES → INNOVATION
          NO → Reconsider market
    NO → Reconsider market or revisit Q1-Q4

Evidence Requirements Per Type

TypeRequired Evidence (from v0.2 Landscape)Confidence Threshold
CloneRevenue proof + feature gap + weak moatMedium (50%+)
UnbundlePlatform size + category neglect + user complaintsMedium (50%+)
UndercutPrice benchmarks + niche pain + simplification pathHigh (70%+)
SlicePlatform MAU + marketplace presence + integration docsHigh (70%+)
WrapperAPI availability + use case validation + cost modelHigh (70%+)
InnovationFailed alternatives + severe pain + budget evidenceVery High (85%+)
Show full SKILL.md (166 more words)Show less

Output Template

After classification, create these entries:

BR-XXX: Product Type Classification

Type: [Clone | Unbundle | Undercut | Slice | Wrapper | Innovation]
Confidence: [X]%
Primary Evidence: [CFD-XXX reference]
Classification Rationale: [2-3 sentences]

BR-XXX: GTM Constraints (inherited from type)

Pricing Constraint: [See references/gtm-constraints.md]
Channel Constraint: [See references/gtm-constraints.md]
Scope Constraint: [See references/gtm-constraints.md]
Timeline Implication: [See references/gtm-constraints.md]

Anti-Patterns to Avoid

  1. Claiming Innovation when it's really Clone: If competitor exists with revenue, you're not innovating
  2. Undercut without price evidence: Must show 60%+ reduction is possible AND sustainable
  3. Slice without ecosystem validation: Platform must actually want third-party apps
  4. Wrapper without API access confirmed: Technical feasibility must precede classification
  5. Unbundle from small platform: Only works against large horizontal players

Reference Files

  • Decision Framework: See references/decision-framework.md for expanded decision trees
  • Examples: See references/examples.md for good/bad classification cases
  • GTM Constraints: See references/gtm-constraints.md for type → constraint mapping
  • Classification Template: See assets/classification.md for structured worksheet

Downstream Impact

Classification constrains v0.3 decisions:

  • Outcome metrics must match type (Clone = feature parity; Undercut = price advantage)
  • Pricing model anchored to type (Undercut must show savings; Slice follows platform norms)
  • MVP scope bounded by type (Clone = match leader; Undercut = ruthlessly cut features)
  • GTM channel determined by type (Slice = marketplace; Undercut = direct to niche)

© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references, assets) in .claude/skills/prd-v02-product-type-classification of mattgierhart/PRD-driven-context-engineering.

  • SKILL.md
  • assets/classification.md
  • references/decision-framework.md
  • references/examples.md
  • references/gtm-constraints.md

Open the folder on GitHubat commit 30ed1b0

Compare with similar skills

Prd V02 Product Type Classification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prd V02 Product Type Classification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd V02 Product Type Classification this skillmattgierhart/PRD-driven-context-engineering180—~1.8kAutomated safety check: PassMIT
PlaidBuildGreatProducts/plaid218—~1.6kAutomated safety check: PassMIT
Startup Designferdinandobons/startup-skill1.2k—~8.1kAutomated safety check: PassMIT
Organic Growth Path Advisordeanpeters/Product-Manager-Skills7.2k2 repos~5.2kAutomated safety check: PassCustom licence
Product Strategistalirezarezvani/claude-skills28k2 repos~1.8kAutomated safety check: PassMIT
Product Competitive AnalysisFokkyp/claude-skills226—~1.2kAutomated safety check: PassNone

Similar skills

  • Plaid

    BuildGreatProducts/plaid

    Product Led AI Development — guides founders from idea to launched product.

    218 GitHub stars~1.6k tokensUpdated 5 mo ago
    Product & Project ManagementAuto-check passed
  • Startup Design

    ferdinandobons/startup-skill

    Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.

    1.2k GitHub stars~8.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Organic Growth Path Advisor

    deanpeters/Product-Manager-Skills

    Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.

    7.2k GitHub starsUsed in 2 repos~5.2k tokens
    Product & Project ManagementAuto-check passed
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Product & Project ManagementAuto-check passed
  • Product Competitive Analysis

    Fokkyp/claude-skills

    Produces product-manager competitive analysis reports in Chinese, with a confirm-first scoping gate, three-phase evidence collection and single or multi-product modes.

    226 GitHub stars~1.2k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Company Research Brief

    deanpeters/Product-Manager-Skills

    Builds a company research brief covering executive quotes, product strategy, transformation efforts and org context, tailored to interview prep, competitor or partnership work.

    7.2k GitHub starsUsed in 1 repo~3.8k tokens
    Product & Project ManagementAuto-check passed

More from mattgierhart/PRD-driven-context-engineering

All 45 skills in this repo
  • Ghm Gate Check

    mattgierhart/PRD-driven-context-engineering

    Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py).

    180 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Ghm Harvest

    mattgierhart/PRD-driven-context-engineering

    Extracts durable insights from temp/ files to SoT during EPIC Phase E.

    180 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Ghm Id Register

    mattgierhart/PRD-driven-context-engineering

    Validates and registers new SoT IDs with cross-reference integrity.

    180 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Ghm Sot Builder

    mattgierhart/PRD-driven-context-engineering

    Creates new Source of Truth (SoT) files when existing templates don't fit your needs.

    180 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed
  • Prd V01 Problem Framing

    mattgierhart/PRD-driven-context-engineering

    Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark.

    180 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Prd V01 User Value Articulation

    mattgierhart/PRD-driven-context-engineering

    Transform validated pain points into articulated user value statements for PRD v0.1 Spark.

    180 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Prd V02 Product Type Classification

What does Prd V02 Product Type Classification do?

Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Prd V02 Product Type Classification is an agent skill from mattgierhart/PRD-driven-context-engineering. Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape.

When should I use Prd V02 Product Type Classification?

Prd V02 Product Type Classification fits situations like: PRD v0.2 work after competitive analysis; user asks what type of product should we build?; should we clone; is this a fast-follow opportunity?.

How do I install Prd V02 Product Type Classification in Claude Code?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-product-type-classification -a claude-code`. Or copy the skill folder (.claude/skills/prd-v02-product-type-classification in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v02-product-type-classification in your project. Claude Code loads it when a task matches its description.

How do I install Prd V02 Product Type Classification in Codex?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-product-type-classification -a codex`. Or copy the skill folder (.claude/skills/prd-v02-product-type-classification in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v02-product-type-classification in your project. Codex loads it when a task matches its description.

Can I use Prd V02 Product Type Classification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-product-type-classification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-v02-product-type-classification, .gemini/skills/prd-v02-product-type-classification, .github/skills/prd-v02-product-type-classification and .opencode/skills/prd-v02-product-type-classification in your project.

What does Prd V02 Product Type Classification need to run?

SKILL.md names no scripts, command-line tools or credentials: Prd V02 Product Type Classification is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, WebSearch, WebFetch.

Does Prd V02 Product Type Classification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prd V02 Product Type Classification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prd V02 Product Type Classification use?

Prd V02 Product Type Classification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prd V02 Product Type Classification use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.

What are the alternatives to Prd V02 Product Type Classification?

Skills that share tags, products or a category with Prd V02 Product Type Classification: Plaid (BuildGreatProducts/plaid, 218 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars), Organic Growth Path Advisor (deanpeters/Product-Manager-Skills, 7.2k stars) and Product Strategist (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd V02 Product Type Classification?

mattgierhart (a GitHub user) maintains it in mattgierhart/PRD-driven-context-engineering, which has 180 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on August 31, 2026.

Source: mattgierhart/PRD-driven-context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.