New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prd V03 Features Value Planning

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

Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model.

MITAuto-check passedProduct & Project Management

Install Prd V03 Features Value Planning

skills CLI
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v03-features-value-planning -a claude-code

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

GitHub CLI
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v03-features-value-planning --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-v03-features-value-planning .claude/skills/prd-v03-features-value-planning && 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-v03-features-value-planning
GitHub stars
180
Token cost
~2.1k tokens
SKILL.md length
737 words
Files
4 (incl. references, assets)
Skills in repo
45
Repo updated
First seen
Licence
MIT

At a glance

Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model.

  • Requests to define features
  • SKILL.md covers Consumes, Produces, Feature Classification Framework and Product Type × Feature Strategy, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Prioritize capabilities

What it does

Prd V03 Features Value Planning is an agent skill from mattgierhart/PRD-driven-context-engineering. Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `assets/competitive-feature-matrix.md`, `assets/fea.md` and `references/examples.md`).

It sits in Product & Project Management, covering PRD writing, Pricing strategy and Physical and earth sciences. 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

  • Requests to define features
  • Prioritize capabilities
  • Map features to pricing tiers
  • Identify parity vs

Example prompts

  • “what features do we build?”
  • “s in MVP?”
  • “which features matter?”
  • “/prd-v03-features-value-planning”

Requirements

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

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.

    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 V03 Features Value Planning loads about 2.1k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 158 tokens; SKILL.md has 737 words of instructions outside code blocks.

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

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). 737 words, ~2,136 tokens.

Download SKILL.mdSave it as .claude/skills/prd-v03-features-value-planning/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
prd-v03-features-value-planning
description
Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.
allowed-tools
Read, Write, Edit, Glob, Grep, WebSearch, WebFetch
context
fork

Feature Value Planning

Position in workflow: v0.3 Commercial Model → v0.3 Feature Value Planning → v0.4 User Journeys

Features are the unit of scope. Every feature must trace back to why it exists: outcome, moat, competitive position, or pricing tier.

Consumes

This skill requires prior work from v0.1-v0.3:

  • CFD-* entries (customer feedback, from v0.1-v0.2) — Evidence for what users need/want
  • KPI-* entries (outcome definitions, from v0.3 Outcome Definition) — What metrics does each feature support
  • BR-* moat entries (from v0.3 Moat Definition) — What features defend our competitive position
  • BR-* pricing entries (from v0.3 Pricing Model) — What features differentiate tiers
  • Market landscape analysis (from v0.2) — Competitive feature comparison

This skill assumes v0.1-v0.2 research is complete and risk/tech decisions (v0.5) are not yet made.

Produces

This skill creates/updates:

  • FEA-* entries (feature definitions, with confidence scoring) — Every feature in scope with traceability
  • BR-FEA-* entries (governance rules for feature decisions) — Scope protection rules
  • MVP-SCOPE artifact — Explicit list: "These X features (FEA-001, FEA-005, FEA-008) define our MVP"
    • Example: MVP-SCOPE: 5 P0 features + 3 P1 features = 8 total. Rationale: Delivers value on [KPI-001, KPI-002]. Competitive parity [FEA-001-003], Delta [FEA-004], Pricing [FEA-005]
    • This becomes the definition for v0.4 user journeys and v0.7 build scope

All FEA- entries include confidence:

  • confidence: 2-3/5 (based on CFD- evidence strength)
  • Evidence: "CFD-001, CFD-005, competitive-analysis"
  • Forward target: "Would move to 4/5 if beta cohort uses it"

Feature Classification Framework

TypeDefinitionStrategic PurposeEvidence Required
MoatBuilds/defends competitive advantageSupports BR- moat ruleHigh (CFD- proving differentiation)
OutcomeDirectly drives success metricTied to KPI- entryHigh (KPI- link mandatory)
ParityMatches competitor baselineFrom Competitive LandscapeMedium (CFD- competitor evidence)
DeltaDifferentiation from competitorsOur advantage over marketHigh (CFD- gap evidence)
TierDifferentiates pricing packagesFrom Pricing BR-Medium (BR- tier assignment)
Table StakesExpected but not differentiatingIndustry standardLow (common knowledge)

Rule: P0 features require Moat, Outcome, or Delta classification. Table Stakes alone cannot justify P0.

Product Type × Feature Strategy

Feature focus varies by product type (from v0.2 classification):

Product TypePrimary FocusParity ApproachDelta Approach
Fast FollowParity + focused delta1:1 critical feature matchSingle compelling improvement
InnovationMoat-building featuresMinimal (new category)Core differentiation IS the product
SliceSegment-specific featuresPartial (niche needs differ)Deep fit for underserved segment
Fast Follow Constraint

BR-FEA-PARITY-FIRST: No delta features until parity features complete. Users compare to incumbent first.

Innovation Pattern

Moat features = 60%+ of scope. Table stakes minimized. Delta is the entire value proposition.

Slice Pattern

80/20 rule: Match 20% of incumbent features that serve 80% of niche use cases. Delta = niche-specific depth.

Show full SKILL.md (316 more words)Show less

Priority Tier Criteria

TierCriteriaEvidence Threshold
P0 — Must HaveBlocks launch without it; tied to primary KPI- or moat BR-CFD- proof + KPI-/BR- link
P1 — Should HaveMeaningfully improves outcome; supports tier differentiationCFD- user signal
P2 — Nice to HaveEnhances experience; no direct KPI impactReasonable assumption OK
P3 — Defer/CutScope creep signal; can add post-launchNone (remove from scope)

Kill criterion: If >40% of features are P2/P3, scope is bloated. Re-evaluate.

FEA- Output Template

Create FEA- entries in this format:

FEA-XXX: [Feature Name]
Type: [Moat | Outcome | Parity | Delta | Tier | Table Stakes]
Priority: [P0 | P1 | P2 | P3]
Description: [What the feature does — user-facing capability]
Outcome Link: [KPI-XXX this supports, or "N/A"]
Moat Link: [BR-XXX moat rule this supports, or "N/A"]
Pricing Link: [BR-XXX tier this belongs to, or "All tiers"]
Competitor Comparison: [Parity with X | Delta vs X | Unique | Table stakes]
Validation: [CFD-XXX evidence, or validation method]
Acceptance Criteria: [Testable condition for "done"]

Example entries:

FEA-001: One-Click Scheduling
Type: Parity
Priority: P0
Description: Schedule meetings with single click from availability view
Outcome Link: KPI-002 (activation rate)
Moat Link: N/A
Pricing Link: All tiers
Competitor Comparison: Parity with Calendly
Validation: CFD-012 (competitor feature audit)
Acceptance Criteria: User completes scheduling in ≤3 clicks

FEA-002: Offline Mode
Type: Delta
Priority: P0
Description: Full functionality without internet connection
Outcome Link: KPI-001 (TTFV for field users)
Moat Link: BR-012 (moat: works anywhere)
Pricing Link: BR-045 (Pro tier differentiator)
Competitor Comparison: Delta vs Notion (requires connection)
Validation: CFD-018 (user interviews: connectivity complaints)
Acceptance Criteria: All core features function with 0 connectivity for 24h

BR-FEA- Governance Rules

Create governance rules for feature decisions:

BR-FEA-XXX: [Rule Name]
Type: [Scope Protection | Prioritization Rule | Validation Gate]
Rule: [Constraint statement]
Rationale: [Why this rule exists]
Enforcement: [When/how applied]

Standard rules to establish:

  • BR-FEA-001: Outcome Link Required — P0/P1 features must link to KPI- entry
  • BR-FEA-002: Validation Before Build — P0 features require CFD- evidence before development
  • BR-FEA-003: Scope Freeze Gate — Feature list locked after v0.4; changes require EPIC

Anti-Patterns to Avoid

Anti-PatternSignalFix
Feature creepP2/P3 > 40% of scopeCut ruthlessly; defer to backlog
Implementation masquerading as feature"Use Redis caching"Reframe as user outcome
Orphaned featuresNo KPI-, BR-, or CFD- linkAdd traceability or cut
Assumption-based priority"Users will love this"Require CFD- evidence
Parity inflationEverything is "parity"Challenge: is competitor feature actually used?
Delta without moatDelta feature easy to copyTie to defensible BR- moat

Downstream Connections

This skill's outputs feed into multiple downstream skills:

ConsumerConsumesPurpose
v0.4 User JourneysFEA-* entries + MVP-SCOPE artifactDesign journey paths through MVP features
v0.5 Red Team ReviewFEA-* entriesAssess technical/risk feasibility of features
v0.6 ArchitectureFEA-* entries + MVP-SCOPEDesign system that supports MVP features
v0.7 Build ExecutionFEA-* entries + MVP-SCOPEDefine EPIC scope (which features = which EPICs)
v0.9 GTMFEA-* entries (especially Delta)Build launch messaging around delta features

Critical handoff: The MVP-SCOPE artifact is the boundary. Everything in the list goes to v0.4+. Everything outside gets deferred to post-launch backlog.

Detailed References

  • Good/bad examples: See references/examples.md
  • FEA- entry template: See assets/fea.md
  • Competitive feature matrix: See assets/competitive-feature-matrix.md

© 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 3 other files (references, assets) in .claude/skills/prd-v03-features-value-planning of mattgierhart/PRD-driven-context-engineering.

  • SKILL.md
  • assets/competitive-feature-matrix.md
  • assets/fea.md
  • references/examples.md

Open the folder on GitHubat commit 30ed1b0

Compare with similar skills

Prd V03 Features Value Planning 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 V03 Features Value Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd V03 Features Value Planning this skillmattgierhart/PRD-driven-context-engineering180—~2.1kAutomated safety check: PassMIT
Prdjuanandresgs/claude-ctrl193—~2.9kAutomated safety check: PassNone
Eval Business LogicIbrahim-3d/orchestrator-supaconductor381—~1.6kAutomated safety check: PassAGPL-3.0
Idea Ossickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassMIT
Specifygenkovich/sdd171—~3.6kAutomated safety check: PassMIT
Utility Pm Criticproduct-on-purpose/pm-skills716—~1.5kAutomated safety check: PassApache-2.0

Similar skills

  • Prd

    juanandresgs/claude-ctrl

    Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.

    193 GitHub stars~2.9k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

  • Eval Business Logic

    Ibrahim-3d/orchestrator-supaconductor

    Specialized business logic evaluator for the Evaluate-Loop. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

    381 GitHub stars~1.6k tokensUpdated 13 days ago
    Product & Project ManagementAuto-check passed

  • Idea Os

    sickn33/agentic-awesome-skills

    Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased…

    47k GitHub starsUsed in 1 repo~1.5k tokens
    Product & Project ManagementAuto-check passed

  • Specify

    genkovich/sdd

    A skill your agent uses to turn a raw feature idea into a reviewed spec.md — a lightweight Socratic interview front (capture the idea, deep-dive the problem) merged with a full product spec…

    171 GitHub stars~3.6k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Utility Pm Critic

    product-on-purpose/pm-skills

    Run adversarial review on a PM artifact via the pm-critic sub-agent.

    716 GitHub stars~1.5k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Evaluate Artifact

    andreaskelm/pm-brain

    Evaluate quality of a PM artifact or substantive session output using the shared evaluation procedure — gut check, red/green flags, optional full scored review.

    234 GitHub stars~1.4k tokensUpdated yesterday
    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

Categories

Questions about Prd V03 Features Value Planning

What does Prd V03 Features Value Planning do?

Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Prd V03 Features Value Planning is an agent skill from mattgierhart/PRD-driven-context-engineering.3 Commercial Model.

When should I use Prd V03 Features Value Planning?

Prd V03 Features Value Planning fits situations like: requests to define features; prioritize capabilities; map features to pricing tiers; identify parity vs.

How do I install Prd V03 Features Value Planning in Claude Code?

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

How do I install Prd V03 Features Value Planning in Codex?

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

Can I use Prd V03 Features Value Planning 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-v03-features-value-planning -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-v03-features-value-planning, .gemini/skills/prd-v03-features-value-planning, .github/skills/prd-v03-features-value-planning and .opencode/skills/prd-v03-features-value-planning in your project.

What does Prd V03 Features Value Planning need to run?

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

Does Prd V03 Features Value Planning 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 V03 Features Value Planning 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 V03 Features Value Planning use?

Prd V03 Features Value Planning 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 V03 Features Value Planning use?

About 2.1k tokens (SKILL.md is roughly 8.5k 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 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Prd V03 Features Value Planning?

Skills that share tags, products or a category with Prd V03 Features Value Planning: Prd (juanandresgs/claude-ctrl, 193 stars), Eval Business Logic (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Idea Os (sickn33/agentic-awesome-skills, 47k stars) and Specify (genkovich/sdd, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd V03 Features Value Planning?

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.