Review a document against its SDLC lifecycle context — assess completeness and check consistency with parent documents in the document hierarchy.
Review the target document(s) at $ARGUMENTS against its SDLC lifecycle context.
Stop after each stage and have changes reviewed with user.
Note: This skill checks a document's position and consistency within a project hierarchy — it does not polish the document itself. Stages 0-4 are analysis only — findings are presented for discussion, not applied as edits. The developer holds final authority on all judgment calls.
Read and identify context (developer confirms)
Assess completeness (agent proposes, developer decides)
Review vs parent document (agent critiques, developer discusses)
Cross-validate against the right side (agent critiques, developer discusses)
Summary and recommendations (agent leads)
This skill sits outside the main pipeline (flesh-out -> review-steps -> strong-edit -> agent-optimize). It's a lateral check — validating a document against its project context, not polishing the document itself. Run it when a document is mature enough to check against its hierarchy.
| Goal | Use |
|---|---|
| Raw notes need structure and expansion | flesh-out |
| Draft needs polish and consistency | review-steps |
| Complete draft needs critical evaluation | strong-edit |
| Check document against its SDLC hierarchy | sdlc-cross-review |
| Finalized document needs agent-friendly restructuring | agent-optimize |
The V-model pairs each definition stage with a corresponding testing stage. The left side decomposes requirements; the right side validates them. Each level on the right validates the corresponding level on the left.
Requirements Analysis ◄──────────────────► Acceptance Testing
│ ▲
│ constrains │ validates
▼ │
System Design ◄────────────────────────────► System Testing
│ ▲
│ constrains │ validates
▼ │
Architecture Design ◄──────────────────────► Integration Testing
│ ▲
│ constrains │ validates
▼ │
Module Design ◄────────────────────────────► Unit Testing
│ ▲
│ constrains │ validates
▼ │
Implementation
| Left Side (Definition) | Right Side (Validation) |
|---|---|
| Requirements analysis | Acceptance testing |
| System design | System testing |
| Architecture design | Integration testing |
| Module design | Unit testing |
Not every project will use all levels. Identify which levels the project uses and apply the relevant checks.