Pre-Flight Check Skill
Role: Check essential info and project status before starting work to reduce omissions and emit machine-readable readiness signals.
Inputs
analysisContext.* (structured state, if exists)- Feature name/branch name (optional)
- Required doc paths:
CLAUDE.md, PROJECT.md, context.md, verification contract, etc.
- Project reference docs when present:
workflow/README.md, docs/design/README.md, docs/glossary/README.md, docs/daily/README.md, TEST_GUIDE.md, docs/analysis/README.md
Checklist
- execution plane (
read_only, product_project, meta_harness)
- UI spec version/design assets availability
- API spec availability
- Similar feature references
- git status/branch, build status
- context.md freshness, unresolved items in pending-questions.md
- downstream project contract readiness (
PROJECT.md)
- project reference docs readiness (workflow/design/glossary/daily/test/analysis)
- downstream verification contract readiness (
.claude/verification.contract.yaml or equivalent policy)
- local policy-set and ignore strategy readiness (
policySets, .claudeignore, or documented equivalent)
- Document Memory Policy check:
- context.md token usage (warn if > 6,000 tokens, ~80% of limit)
- specification.md exists and is summarized (if large spec)
- archives/ directory structure in place
- Doc Freshness Check:
- Check
ARCHITECTURE.md last modified vs code change
- Check
docs/generated/* vs related source code
Structured Output Contract
Return machine-readable readiness signals first, then optional human summary.
signals:
executionPlane: product_project
projectContractReady: false
contextReady: false
verificationContractReady: false
shouldEscalateStrict: true
docStale: false
notes:
- "pre-flight: executionPlane=product_project"
- "pre-flight: project contract missing required command/test sections"
- "pre-flight: project reference docs missing workflow/design/test guidance"
- "pre-flight: ignore or protected-path policy missing"
recommendedActions:
- "run project-contract-gate"
- "run context-readiness-gate"
- "refresh security and ignore policy docs"
Optional human-readable example:
# Pre-flight Check Results
## Plane
product_project
## Readiness
WARN PROJECT.md incomplete
WARN context.md missing minimum sections
WARN verification contract missing
## Recommended Actions
1. [HIGH] Run `project-contract-gate`
2. [HIGH] Run `context-readiness-gate`
3. [MEDIUM] Add `.claude/verification.contract.yaml`
Anti-Pattern Check
Detect common mistakes based on "How to write a good spec for AI agents" guide
Checklist
| Anti-Pattern |
Detection Method |
Status |
| Vague prompts |
"Make something cool", "Make it work better" |
⚠️ |
| Large context without summary |
specification.md > 3,000 tokens + no summary |
⚠️ |
| Missing 6 core areas |
PROJECT.md lacks commands/tests/structure/style/Git/boundaries |
⚠️ |
| Vibe coding ↔ Production confusion |
Attempting production deploy without tests |
⚠️ |
| Ignoring deadly trinity |
Proceeding without verification for speed/non-determinism/cost |
⚠️ |
Recommended Actions on Detection
| Detected Anti-Pattern |
Recommended Action |
| Vague request |
Invoke requirements-analyzer to clarify |
| Large document |
Follow document-memory-policy.md to summarize |
| Missing areas |
Set projectContractReady=false, recommend project-contract-gate or project-md-refresh |
| No tests |
Recommend writing tests before completion-verifier |
| No ignore/protected-path policy |
Refresh security docs and add .claudeignore or equivalent |
References
docs/public/guidelines/document-memory-policy.mddocs/public/guidelines/context-readiness-schema.mddocs/public/guidelines/verification-contract.md
1---2name: pre-flight-check3description: Checks essential information and project status before starting work and emits readiness signals for orchestration.4---56# Pre-Flight Check Skill78**Role**: Check essential info and project status before starting work to reduce omissions and emit machine-readable readiness signals.910## Inputs11- `analysisContext.*` (structured state, if exists)12- Feature name/branch name (optional)13- Required doc paths: `CLAUDE.md`, `PROJECT.md`, `context.md`, verification contract, etc.14- Project reference docs when present: `workflow/README.md`, `docs/design/README.md`, `docs/glossary/README.md`, `docs/daily/README.md`, `TEST_GUIDE.md`, `docs/analysis/README.md`1516## Checklist17- execution plane (`read_only`, `product_project`, `meta_harness`)18- UI spec version/design assets availability19- API spec availability20- Similar feature references21- git status/branch, build status22- context.md freshness, unresolved items in pending-questions.md23- downstream project contract readiness (`PROJECT.md`)24- project reference docs readiness (workflow/design/glossary/daily/test/analysis)25- downstream verification contract readiness (`.claude/verification.contract.yaml` or equivalent policy)26- local policy-set and ignore strategy readiness (`policySets`, `.claudeignore`, or documented equivalent)27- **Document Memory Policy check**:28 - context.md token usage (warn if > 6,000 tokens, ~80% of limit)29 - specification.md exists and is summarized (if large spec)30 - archives/ directory structure in place31- **Doc Freshness Check**:32 - Check `ARCHITECTURE.md` last modified vs code change33 - Check `docs/generated/*` vs related source code3435## Structured Output Contract3637Return machine-readable readiness signals first, then optional human summary.3839```yaml40signals:41 executionPlane: product_project42 projectContractReady: false43 contextReady: false44 verificationContractReady: false45 shouldEscalateStrict: true46 docStale: false47notes:48 - "pre-flight: executionPlane=product_project"49 - "pre-flight: project contract missing required command/test sections"50 - "pre-flight: project reference docs missing workflow/design/test guidance"51 - "pre-flight: ignore or protected-path policy missing"52recommendedActions:53 - "run project-contract-gate"54 - "run context-readiness-gate"55 - "refresh security and ignore policy docs"56```5758Optional human-readable example:5960```markdown61# Pre-flight Check Results6263## Plane64product_project6566## Readiness67WARN PROJECT.md incomplete68WARN context.md missing minimum sections69WARN verification contract missing7071## Recommended Actions721. [HIGH] Run `project-contract-gate`732. [HIGH] Run `context-readiness-gate`743. [MEDIUM] Add `.claude/verification.contract.yaml`75```7677## Anti-Pattern Check7879> Detect common mistakes based on "How to write a good spec for AI agents" guide8081### Checklist8283| Anti-Pattern | Detection Method | Status |84|--------------|-----------------|--------|85| **Vague prompts** | "Make something cool", "Make it work better" | ⚠️ |86| **Large context without summary** | specification.md > 3,000 tokens + no summary | ⚠️ |87| **Missing 6 core areas** | PROJECT.md lacks commands/tests/structure/style/Git/boundaries | ⚠️ |88| **Vibe coding ↔ Production confusion** | Attempting production deploy without tests | ⚠️ |89| **Ignoring deadly trinity** | Proceeding without verification for speed/non-determinism/cost | ⚠️ |9091### Recommended Actions on Detection9293| Detected Anti-Pattern | Recommended Action |94|----------------------|-------------------|95| Vague request | Invoke `requirements-analyzer` to clarify |96| Large document | Follow `document-memory-policy.md` to summarize |97| Missing areas | Set `projectContractReady=false`, recommend `project-contract-gate` or `project-md-refresh` |98| No tests | Recommend writing tests before `completion-verifier` |99| No ignore/protected-path policy | Refresh security docs and add `.claudeignore` or equivalent |100101## References102- `docs/public/guidelines/document-memory-policy.md`103- `docs/public/guidelines/context-readiness-schema.md`104- `docs/public/guidelines/verification-contract.md`
munlucky