sdlc-cross-review
Skill0 starsChanged 8 months agoUnlicenseView on GitHub
Review a document against its SDLC lifecycle context — assess completeness and check consistency with parent documents in the document hierarchy.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Minh-Tam-Solution/SDLC-Enterprise-Frameworktheir own version, first seen Sep 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Minh-Tam-Solution/SDLC-Enterprise-Framework★ 20same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-optimizeSkill
- dev-recordSkill
- flesh-outSkill
- generator-codingSkill
- light-v-structureSkill
- no-pre-existing-failuresSkill
- review-skillSkill
- review-stepsSkill
- sandboxSkill
- strong-editSkill
- my-skillSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read the target document and its surrounding project structure
- Distinctive: line 17
If the project defines its own hierarchy, use that.
- Distinctive: line 24
If the document isn't ready for cross-review, recommend the appropriate skill and stop
- Distinctive: line 25
Ask: does the developer want to proceed with cross-review now, or address completeness first?
- Distinctive: line 36
Do validation artifacts exist that cover what the document specifies?
- Distinctive: line 39
Ask: are missing validation artifacts a known gap, or an oversight?
- Distinctive: line 93
Not every project will use all levels.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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)
- Read the target document and its surrounding project structure
- What is this document about and where does it sit in the project?
- Can you identify a document hierarchy (V-model, or project-defined)?
- If the project defines its own hierarchy, use that; otherwise ask the developer to clarify
- Confirm understanding of the document's position before proceeding
- Assess completeness (agent proposes, developer decides)
- Is this a skeleton that needs fleshing out, or a draft that needs polishing?
- Skeletons need generative work (structure, diagrams, missing sections) — that's a flesh-out task, not a cross-review
- Drafts with language issues need review-steps first
- If the document isn't ready for cross-review, recommend the appropriate skill and stop
- Ask: does the developer want to proceed with cross-review now, or address completeness first?
- Review vs parent document (agent critiques, developer discusses)
- Identify the parent document(s) that constrain this document (left side, decomposition)
- Is the target document consistent with decisions and constraints in its parent(s)?
- Are there contradictions or gaps between the target and its parent documents?
- Does the target document trace back to requirements or decisions in the parent?
- Present findings and ask: are any inconsistencies intentional or reflect evolved thinking?
- Cross-validate against the right side (agent critiques, developer discusses)
- Identify the validation pair for this document (see V-Model Context below)
- Do validation artifacts exist that cover what the document specifies?
- Is anything specified in the document that has no corresponding validation?
- Is anything validated that isn't specified in the document?
- Ask: are missing validation artifacts a known gap, or an oversight?
- Summary and recommendations (agent leads)
- What is the document's overall consistency with its hierarchy?
- What are the top issues to address?
- Recommendation: consistent / minor gaps / needs rework
Pipeline Position
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.
When to Use This vs Other Skills
| 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 |
V-Model Context
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
▼ │
ImplementationStandard Cross-Validation Pairs
| 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.
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

