openspec-preflight

Inspect OpenSpec proposal artifacts for gaps and human-required tasks.

Updated Apr 22, 2026

Search Tags:#code review #change management #OpenSpec #preflight #task identification

Ready to run

npx skills add https://github.com/aditrioka/nearyou-id --skill openspec-preflight

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-preflight
Source: https://github.com/aditrioka/nearyou-id/tree/main/.claude/skills/openspec-preflight
Command: npx skills add https://github.com/aditrioka/nearyou-id --skill openspec-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies and surfaces critical tasks and gaps in OpenSpec changes before implementation begins, reducing mid-implementation surprises and follow-ups.

Core Features & Use Cases

Preflight Check: Inspects proposal artifacts for human-required tasks, counterpart-layer gaps, and unmapped test scenarios.
Human-required Tasks: Flags tasks that require operator intervention, such as credentials, GCP provisioning, and external dashboards.
Counterpart-layer Check: Ensures that user-facing capabilities have corresponding client surfaces and data consistency.
Doc Reconciliation: Compares proposal claims against canonical documentation for consistency.
Test Scenario Mapping: Verifies that all scenarios have corresponding test tasks.

Quick Start

Run the openspec-preflight skill to preflight the change before implementing.

Frequently Asked Questions about openspec-preflight

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

FAQPage Schema

What is a preflight check for code changes and when do I need it?▼

A preflight check for code changes inspects proposal artifacts to identify critical gaps and human-required tasks before implementation begins. You need it to reduce mid-implementation surprises and ensure workflow cohesion.

How do I identify human-required tasks in OpenSpec changes before implementation?▼

To identify human-required tasks in OpenSpec changes, run a preflight check that flags operator interventions like credentials, GCP provisioning, and external dashboards. This surfaces manual requirements early in the workflow.

How do I verify counterpart-layer cohesion for user-facing capabilities?▼

To verify counterpart-layer cohesion, run a preflight inspection that checks user-facing capabilities for corresponding client surfaces and data consistency. This ensures data layers align before implementation starts.

Can I reconcile proposal claims against canonical documentation automatically?▼

Yes, you can reconcile proposal claims against canonical documentation automatically. The preflight process compares artifacts against canonical docs to check for consistency and flags discrepancies before implementation.

Does preflight mapping verify that all test scenarios have corresponding tasks?▼

Yes, preflight mapping verifies that all test scenarios have corresponding test tasks. It inspects proposal artifacts to map test scenarios, ensuring complete test coverage before implementation begins.

What proposal artifacts and documentation access do I need to run a preflight check?▼

To run a preflight check, you need proposal artifacts and access to canonical documentation. The preflight process requires these inputs to inspect gaps, reconcile claims, and map test scenarios effectively.