cy-spec-preflight

Load canonical playbook context and run phase-specific structural validation before spec authoring.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill cy-spec-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-spec-preflight
Source: https://github.com/compozy/agh/tree/main/.agents/skills/cy-spec-preflight
Command: npx skills add https://github.com/compozy/agh --skill cy-spec-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

cy-spec-preflight prevents AGH PRDs, TechSpecs, and tasks from entering review with missing or off-scope structure by loading the canonical playbook, standing directives, glossary, and the most relevant phase lessons and then enforcing phase-specific validation gates.

Core Features & Use Cases

  • Loads required authoring context: playbook, standing directives, glossary, phase lessons, and CLAUDE posture/principles/security invariants.
  • Infers phase safely: accepts an optional phase input and can infer phase from the active cy-create-* workflow or artifact path conventions.
  • Runs phase-specific checks: PRD implementation-leak heuristics; TechSpec six-marker enforcement; tasks table shape and QA tail pairing verification.
  • Gates approvals: blocks user approval when required structural surfaces are missing (including required analysis for extensibility, agent-manageability, and config lifecycle).
  • Precedes inner spec authoring: hands control to the corresponding cy-create-* inner skill, then applies after-draft checks before approval or execution.

Quick Start

Use cy-spec-preflight with the phase you are about to author, for example: Run cy-spec-preflight with phase techspec.

Frequently Asked Questions about cy-spec-preflight

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

FAQPage Schema
How do I prevent implementation details from leaking into my PRD drafts?

Preflight checks prevent implementation leaks in PRD drafts by loading canonical playbooks and applying heuristics that block approval when required structural surfaces are missing.

What is the best way to enforce required analysis sections before a TechSpec review?

The best way to enforce required analysis sections before a TechSpec review is running six-marker enforcement checks that validate the presence of structural surfaces like agent-manageability and config lifecycle.

How do I validate task planning tables and QA tail pairing before execution?

You validate task planning tables and QA tail pairing by executing preflight scripts that verify table shape and ensure QA tail pairing is correctly structured before execution approval.

Can I infer the spec authoring phase automatically from artifact path conventions?

Yes, you can infer the spec authoring phase safely from active workflow states or artifact path conventions, though providing an explicit phase input remains the most direct method.

Do I need to load standing directives and glossary context before drafting a spec?

You need to load standing directives, glossary, and phase lessons before drafting a spec to ensure required project context is present and phase-specific validation gates can be enforced.