analyze

Validate brief.md, spec.md, and plan.md for consistency and completeness.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/bernajaber/pi-product-system --skill analyze-bernajaber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/bernajaber/pi-product-system/tree/main/skills/analyze
Command: npx skills add https://github.com/bernajaber/pi-product-system --skill analyze-bernajaber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The analyze skill verifies that the product brief, acceptance spec, and implementation plan are consistent, complete, and aligned with the project's constitutions before building begins. It prevents wasted engineering effort by catching missing scenarios, contradictions, and unaddressed risks early.

Core Features & Use Cases

  • Document validation: Compares brief.md, spec.md, and plan.md to find gaps and contradictions.
  • Issue classification: Classifies findings as spec-problem or plan-problem and recommends corrective loops.
  • Risk & depth assessment: Determines reviewDepth (simple|medium|complex) and highlights product or technical risks.
  • Gate 2 readiness: Produces an internal critique.md and prepares a Portuguese Gate 2 presentation without exposing technical artifacts.
  • Use Case: Before implementation, run analyze to ensure a shared shopping-list feature's spec covers all user scenarios and the plan delivers them.

Quick Start

Run the analyze skill for feature 'shared shopping list' to generate critique.md and a Gate 2 summary in Portuguese.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I validate brief, spec, and plan documents for consistency before development?

Document validation compares brief.md, spec.md, and plan.md to detect missing acceptance scenarios, contradictions, and technical risks before building begins. It classifies findings as spec-problem or plan-problem and recommends corrective loops.

What is a Gate 2 readiness check in product discovery and planning?

A Gate 2 readiness check assesses document alignment and produces an internal critique.md with classified issues and risk assessment. It determines reviewDepth and prepares a presentation while keeping technical artifacts hidden from the operator.

When do I need to run a spec review to catch missing user scenarios?

Run a spec review during product discovery and planning to ensure acceptance specs cover all user scenarios. It identifies gaps between the brief and plan, preventing wasted engineering effort by catching contradictions early.

How do I classify technical and product risks found during plan review?

Plan review classifies risks by categorizing findings as spec-problem or plan-problem, determining reviewDepth as simple, medium, or complex, and recommending corrective loops to address missing scenarios or contradictions.

Does the analyze skill work without external dependencies for risk assessment?

Yes, risk assessment runs without external dependencies. It validates brief.md, spec.md, and plan.md internally, producing critique.md and a Portuguese Gate 2 summary while keeping technical artifacts hidden.

What limitations exist when validating project constitutions during document alignment?

Document alignment focuses on consistency between brief.md, spec.md, and plan.md. It produces an internal critique.md and Portuguese Gate 2 presentation but keeps technical artifacts hidden from the operator during the review process.