skills.rest
hieubui2409
hieubui2409COMMUNITY
Explore all skills by this author →
GitHub

cleanmatic:product-spec-critique

Critique product specs across product, tech, market, and craft lenses.

17|8|Updated May 28, 2026
Search Tags:#automation#markdown#provenance#evidence#critique#product-spec#lenses
One-click install
npx skills add https://github.com/hieubui2409/product-spec --skill cleanmatic-product-spec-critique
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cleanmatic:product-spec-critique
Source: https://github.com/hieubui2409/product-spec/tree/main/.claude/skills/product-spec-critique
Command: npx skills add https://github.com/hieubui2409/product-spec --skill cleanmatic-product-spec-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill provides brutal, evidence-based critique of a product spec across four lenses (product, tech, market, craft), helping teams surface risks and opportunities before coding starts.

Core Features & Use Cases

  • Reads the output of cleanmatic:product-spec and reuses its --validate findings as ammunition to deliver cross-lens judgments.
  • Produces a single Markdown critique with per-line evidence IDs, why-it-dies, fixes, and a front matter for provenance.
  • Supports configurable scope, language, level, and voice to fit product teams’ governance and safety boundaries.

Quick Start

Provide a sample run by specifying a target scope, language, and level, then read the generated Markdown critique report.

Frequently Asked Questions about cleanmatic:product-spec-critique

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

FAQPage Schema
How do I critique a product spec to surface risks before coding starts?▼

A product spec critique analyzes your document across four lenses: product, tech, market, and craft. It surfaces why-it-dies risks, market implications, and craft notes using per-line evidence IDs and specific fixes rendered in a Markdown report.

What is the best way to validate product spec assumptions using evidence?▼

The best way to validate product spec assumptions is reusing upstream --validate findings as ammunition. This delivers evidence-based cross-lens judgments, generating per-line evidence IDs and frontmatter provenance for reuse in DEC workflows.

How do I generate a Markdown report with provenance for product spec reviews?▼

Generate a Markdown report with provenance by running an automated critique that never edits the source spec. The output includes frontmatter for provenance, per-line evidence IDs, why-it-dies statements, and actionable fixes.

Can I configure the critique scope and voice for my product team's governance?▼

Yes, you can configure the critique by scope, level, language, and voice. This flexibility fits product teams' governance and safety boundaries while delivering brutal, practical cross-lens judgments across product, tech, market, and craft dimensions.

Does the product spec critique modify the original source document?▼

No, the product spec critique never edits the source document. It reads upstream --validate findings and renders a separate Markdown critique report, ensuring the original spec remains intact while providing evidence-based fixes.

Related Skills

Explore More Product & Management Skills→
akiojinakiojin
8

speckit-update

Apply upstream Spec Kit updates while preserving local conventions.

Community
Advanced
chf3198chf3198

role-consultant-critique

Score role risks and generate a structured CLOSEOUT report with grades.

Community
Advanced
notta50notta50

kiro-spec-batch

Generates and validates feature specs from roadmap.md in dependency order with parallel waves.

Community
Advanced
JohnnnmaiJohnnnmai
1

bigtech-vs-startup-decision-advisor

Evaluate user priorities to recommend big tech or startup Product Manager roles.

Community
Intermediate