Skip to content
Back to skills

Cy Spec Preflight

ASecurity

Check a Compozy spec or task artifact during authoring or when its contracts change.

  • 2,785 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
testing

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned September 20, 2026

npx -y skills add compozy/compozy --skill cy-spec-preflight --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cy Spec Preflight?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cy Spec Preflight
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/compozy-cy-spec-preflight/badge)](https://www.skillsdirectory.com/skills/compozy-cy-spec-preflight)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cy-spec-preflight
description: "Check a Compozy spec or task artifact during authoring or when its contracts change."
---

# Spec Preflight

Check the current artifact within its authoring/change step. Reuse accepted
research, decisions, and prior checks; execution of an unchanged task does not
require another preflight or repository survey.

Choose only the relevant branch:

- **Spec:** [Spec contracts](references/spec-contracts.md) for outcome, interfaces,
  compatibility, and applicable companion contracts. Use the playbook only for an
  unresolved authoring convention and `references/phase-lessons.md` when a matching
  design question needs historical evidence.
- **Tasks/task body:** [Task checks](references/tasks-checks.md) for graph consistency,
  outcome coverage, canonical references, test/evidence ownership, and QA scope.

Repair substantive contract or dependency gaps at their owner, then check the
changed facts. User decisions and repository compatibility policy outrank stale
artifacts; an ADR cannot silently narrow the accepted outcome. Missing template
phrases, empty optional sections, or an unused companion document are not blockers.
Ask only when a missing product decision prevents correct authoring. Peer review
of an approved spec remains opt-in.

Files in this skill

  • SKILL.md8.8 KB
  • references/phase-lessons.md1.7 KB
  • references/spec-part1-checks.md2.1 KB
  • references/spec-six-markers.md4.2 KB
  • references/tasks-checks.md4.2 KB
  • scripts/check-spec-markers.py4 KB
  • scripts/check-spec-part1-leak.py3.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…