speckit.evaluate

Evaluate clarified Speckit specs against market research to refine features.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-evaluate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.evaluate
Source: https://github.com/lofidonut3/oh-my-speckit/tree/main/skills/speckit.evaluate
Command: npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-evaluate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams validate clarified specs against market research to identify additions, removals, or modifications, ensuring alignment with real user needs.

Core Features & Use Cases

  • Evaluation workflow: Compare specs to research findings to uncover gaps and opportunities.
  • Decision facilitation: Produce structured recommendations with acceptance or rejection options for each feature.
  • Lifecycle integration: Integrates after speckit.research and before speckit.design to optimize the feature set and priorities.

Quick Start

Use speckit.evaluate after completing speckit.research to review results, accept or reject recommendations, and finalize the spec for design.

Frequently Asked Questions about speckit.evaluate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate a product spec against market research findings?

To evaluate a product spec against market research, compare clarified specs to research findings to identify feature gaps, uncover opportunities, and produce structured accept or reject recommendations for each item.

What is feature prioritization and how does spec evaluation work?

Feature prioritization is ranking spec features by market evidence. Spec evaluation works by comparing your product requirements against research data to decide whether to add, remove, or modify features based on real user needs.

How do I prioritize features as P0, P1, or P2 based on user needs?

You prioritize features by applying structured recommendations from a spec evaluation, which aligns your feature set with market research and enforces P0, P1, and P2 priority levels for finalized product design.

Do I need completed market research before evaluating my product spec?

Yes, you need completed market research before evaluating your product spec. The evaluation workflow requires comparing a clarified spec against existing research findings to validate alignment and identify necessary feature modifications.

What's the best way to decide whether to accept or reject features in a spec?

The best way to accept or reject spec features is validating them against market research evidence. This produces structured recommendations with clear acceptance or rejection options, ensuring modifications align with real user needs.

When should I run a spec evaluation in the product development lifecycle?

You should run a spec evaluation after completing market research and before beginning the design phase. This lifecycle integration ensures your finalized spec is optimized and prioritized based on evidence before design work starts.