sdlc-check

Validates whether SDLC phase input documents are ready to start the next phase.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/juartaurus98/codebase --skill sdlc-check-juartaurus98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-check
Source: https://github.com/juartaurus98/codebase/tree/main/.claude/skills/sdlc-check
Command: npx skills add https://github.com/juartaurus98/codebase --skill sdlc-check-juartaurus98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? At a handoff between roles (e.g., PO to Tech Lead), it is unclear whether a PRD, SRS, or other phase document is complete enough to support the next phase. This Skill reports readiness without generating any output, naming every missing or unclear item by file, section, and the role that owns it. ## Core Features & Use Cases - Readiness gating: Runs the framework's input-check protocol against any phase (intake, prd, srs, techdocs, code, testcases, unit, acceptance, review) and reports READY or NOT_READY. - Role-grouped gap reporting: Groups blocking gaps by owning role (PO/BA, Tech Lead) so the reader immediately knows whether to fix it or hand it back. - Persistent gap recording: Appends blocking gaps to the source document's open-questions table and findings.tsv so the answer survives the terminal session. - Use Case: A Tech Lead picking up a PO's PRD runs /check srs PTK-001 and gets a one-screen verdict listing the two blocking gaps owned by the PO, without generating any SRS content. ## Quick Start Run /check srs PTK-001 to verify whether the PRD for feature PTK-001 is complete enough to begin writing the SRS.

Frequently Asked Questions about sdlc-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a PRD is ready for SRS writing?▼

Run /check srs with the feature ID, for example /check srs PTK-001. It evaluates the PRD against the srs phase input contract and reports every missing or unclear item by file, section, and owning role.

How to check readiness of all SDLC phases at once?▼

Run /check with no phase argument. It reports the readiness of every phase whose source documents exist, giving a one-screen answer to where a feature is actually blocked.

Does the readiness check modify my documents?▼

It never edits content a person wrote or generates phase output. It only appends auto-marked questions to the source document's open-questions table and records blocking gaps in findings.tsv.

Can I check a document written outside the framework?▼

Yes. A document pasted directly into docs/srs/ can be validated with /check techdocs even if the corresponding phase command never ran. The check evaluates the document against the input contract regardless of origin.

What are the limitations of an automated readiness check?▼

It reports readiness but never fixes gaps, marks items resolved, or asks questions interactively. Requirements it cannot evaluate are reported as unclear rather than READY, and only a person editing the document can close a gap.