Verify a Linear issue's spec against actual project state.
npx skills add https://github.com/withpiper/pipekit --skill spec-preflight
Please help me install this Agent Skill. Skill: spec-preflight Source: https://github.com/withpiper/pipekit/tree/main/skills/spec-preflight Command: npx skills add https://github.com/withpiper/pipekit --skill spec-preflight
Empirical pre-flight checks on a Linear issue's spec. Verifies file paths, line refs, phase-detect baseline, Linear status, and dependencies against reality. Read-only.
Run preflight on a Linear issue to verify file paths, line refs, and dependencies before launching.
High-intent search queries and answers about installing and using this skill.
To verify a Linear issue spec before launch, run a preflight check that compares cited file paths, line references, and phase-detect baselines against the repository. It surfaces divergences between the spec and reality without modifying any files.
Yes, you can check Linear dependencies and file paths without modifying project files by running a read-only preflight verification. This safely validates spec citations and surfaces status drift before progressing to launch.
A preflight spec verification for Linear issues is an empirical check that identifies divergences between a ticket's spec and the actual project state. It validates file paths, line references, phase-detect baselines, and dependencies to produce a verbose verdict.
You validate line citations and phase-detect baselines by running a preflight check on the specific Linear issue. The process compares the ticket's cited references against actual files and tool outputs to ensure the spec remains accurate.
You should run a spec verification check on a Linear issue right before launch. It operates as a gating check to compare the reported Linear status and dependencies to the real state, surfacing any drift before you progress.
Preflight spec verification operates on a specific Linear issue rather than a whole project. It checks the cited file paths, line references, and dependencies for that individual ticket to ensure its spec is still accurate.
outfitter-devProcesses FORMAT files via a Bun-based CLI with extract, transform, and create commands.
inflexa-aiOrchestrate OpenSpec change lifecycle status checks and sequential artifact generation.
saajunaidValidate a preflight plan against the repository surface for mismatches.
agentmattersMonitor deployed URLs for HTTP status, console errors, and performance regressions.
