ui-spec-planning

Generate plan.md and eval_criteria.yaml from acceptance scenarios, NFRs, and architecture preflight.

20|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Accelerated-Innovation/governed-ai-delivery --skill ui-spec-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-spec-planning
Source: https://github.com/Accelerated-Innovation/governed-ai-delivery/tree/main/agents/codex/skills/ui/spec-planning
Command: npx skills add https://github.com/Accelerated-Innovation/governed-ai-delivery --skill ui-spec-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec Planning for a UI feature provides a structured approach to translate user requests and constraints into a concrete, governance-ready plan by generating plan.md and eval_criteria.yaml from inputs like acceptance scenarios, NFRs, and architecture preflight.

Core Features & Use Cases

  • Generate a Feature Summary, MVVM Breakdown, and Increment Breakdown from inputs.
  • Produce plan.md and eval_criteria.yaml aligned with governance templates.
  • Validate architecture prerequisites and accessibility considerations before implementation.

Quick Start

Provide the user-facing feature name or request, and run the UI Spec Planning skill to produce a plan.md and eval_criteria.yaml.

Frequently Asked Questions about ui-spec-planning

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

FAQPage Schema
How do I generate a plan.md and eval_criteria.yaml for UI feature work?

UI spec planning translates acceptance scenarios, NFRs, and architecture preflight into a governance-ready plan.md and eval_criteria.yaml, validating architecture prerequisites and accessibility considerations before starting MVVM implementation.

How do I create an MVVM breakdown for a new UI feature?

UI spec planning validates architecture prerequisites and accessibility considerations by checking architecture_preflight.md and NFRs before implementation, ensuring the generated plan.md aligns with governance templates and MVVM contracts.

What's the best way to structure evaluation criteria for UI architecture governance?

Structure evaluation criteria for UI architecture governance by generating an eval_criteria.yaml file aligned with eval_criteria.schema.json, translating non-functional requirements and acceptance scenarios into measurable validation metrics for implementation.

Does UI spec planning work with existing acceptance feature files?

Yes, UI spec planning works with existing acceptance feature files by reading features/<feature_name>/acceptance.feature, nfrs.md, and architecture_preflight.md to automatically extract constraints and generate a comprehensive feature implementation plan.

What inputs do I need to run UI spec planning for MVVM features?

You need acceptance scenarios, NFRs, architecture preflight, MVVM_CONTRACT.md, governance templates, and JSON schemas to run UI spec planning, which synthesizes these inputs to produce plan-ready feature documentation and evaluation criteria.