القائمة
Use when multi-component work needs cross-component verification of API contracts, data flow, events, auth, config, UI, background jobs, or tests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when following the Super Compound BRD -> PRD -> FSD -> GOAL -> IMPLEMENTATION -> VERIFICATION delivery path, artifact traceability, FSD authority, optional ADR handling, zero context bloat issue slicing, or OPEN-* stop conditions.
Use when an approved FSD goal or lightweight issue pointer is ready for implementation.
Use when /sc-plan needs FSD GOAL-* packets turned into lightweight issue pointers, local Markdown Kanban boards, blocker DAGs, or multi-agent task contracts.
Use when a plan or issue board has 2+ independent execution streams whose time saving exceeds coordination overhead. Dispatches agents in isolated git worktrees only after required delivery gates pass.
Use when an FSD and goal issue board need requirement coverage, goal quality, dependency DAG, sizing, and verification validated before execution.
Use when an approved BRD must be translated into observable product requirements before FSD planning.
| name | integration-checking |
| description | Use when multi-component work needs cross-component verification of API contracts, data flow, events, auth, config, UI, background jobs, or tests. |
Existence is not integration. A route, component, service, or config file can exist and still be disconnected from the user-visible workflow.
Announce: "I'm using the integration-checking skill to verify cross-component wiring."
For the changed feature, trace:
User action / external event
-> screen -> action / UI-STATE-* -> UIMAP-*
-> operation + pinned SCHEMA-* / error contract
-> validation/auth/permission
-> service/domain logic
-> persistence/external service
-> response/event/job
-> user-visible result or observable side effect
| Area | Verify |
|---|---|
| API contract | Callers send the fields the endpoint expects; responses match consumers |
| Contract revision | FSD index, schema, fixtures, mock, and typed consumer pin the same revision |
| Data flow | Create/read/update/delete path works through all layers |
| Events/jobs | Emitters have handlers; handlers are registered and idempotent |
| Auth | Protected paths enforce auth and authorization at the boundary |
| Config | Required env vars exist in .env.example and are loaded |
| UI | Component is reachable, state updates, loading/error/empty states work |
| UI state mapping | Success, validation, forbidden, conflict, degraded, offline, and async outcomes map to named states or approved N/A |
| Fixtures | Synthetic deterministic fixtures validate against the pinned schema and cover representative failure |
| Responsive/a11y | Reflow, overflow, keyboard, focus, semantics, announcements, errors, contrast, zoom, and motion are verified |
| Environment | Record MOCK or REAL; mock evidence is not real provider integration proof |
| Contract tests | Provider and consumer tests exercise the same operation/schema revision |
| Tests | At least one test exercises the integrated path when practical |
| Docs | API/user/setup docs match the wired behavior |
# Integration Check
**Feature:** <name>
**Contract version:** <qualified CONTRACT-* ref and revision>
**Environment:** MOCK | REAL
## Wiring Trace
<trace>
## Findings
| Severity | Gap | Evidence | Required Fix |
|----------|-----|----------|--------------|
## Verification Commands
| Command | Result |
|---------|--------|
executing-plans, verification-before-completion, and gap-closure.