phase-1-review

Evaluate Phase 1 functional specs against widget-kind rules and generate a PASS/FAIL conformance report.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/tercen/tercen_flutter_apps --skill phase-1-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-1-review
Source: https://github.com/tercen/tercen_flutter_apps/tree/main/.claude/skills/phase-1-review
Command: npx skills add https://github.com/tercen/tercen_flutter_apps --skill phase-1-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews Phase 1 functional specs for conformance by validating widget-kind rules and applying the appropriate checks to produce a conformance report.

Core Features & Use Cases

  • Determine widget kind (panel, runner, or window) from the spec and apply the corresponding checks.
  • Validate required frontmatter (name, description) and ensure the spec content structure.
  • Generate a PASS/FAIL conformance report and save it to _local/phase-1-conformance-report.md.

Quick Start

Provide the path to the functional spec to start the conformance review.

Frequently Asked Questions about phase-1-review

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

FAQPage Schema
How do I check my Phase 1 functional spec for conformance issues?

To check a Phase 1 functional spec for conformance issues, provide the spec file path. The review evaluates widget-kind rules, applies corresponding checks, and generates a PASS/FAIL conformance report saved to _local/phase-1-conformance-report.md.

What widget kinds are supported during a Phase 1 spec review?

Phase 1 spec reviews support three widget kinds: panel, runner, and window. The review identifies the widget kind from the spec content, loads the corresponding shared and kind-specific checks, then produces a formal conformance report.

Does my functional spec require specific frontmatter to pass a conformance check?

Yes, functional specs require YAML frontmatter to pass conformance checks. The review enforces mandatory name and description fields in the frontmatter before applying widget-kind rules and generating the final conformance report.

How do I automate spec conformance reporting for widget-kind rules?

Automate spec conformance reporting by providing the functional spec path to the review process. It automatically detects the widget kind, validates required frontmatter, runs shared and specific checks, and outputs a PASS/FAIL report.

What happens if a functional spec fails a widget-kind conformance check?

If a functional spec fails a widget-kind conformance check, the review generates a FAIL status in the formal conformance report. This report is saved to _local/phase-1-conformance-report.md, detailing the shared and kind-specific rule violations found.