sdlc-checkpoint

Validate SDLC phase outputs and issue PASS, CONDITIONAL, or BLOCK verdicts.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill sdlc-checkpoint-kscius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-checkpoint
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/sdlc-checkpoint
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill sdlc-checkpoint-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Intake-to-close phase gating to ensure outputs are complete and verified before moving to the next SDLC phase, reducing costly rework and miscommunications across teams.

Core Features & Use Cases

  • Provides gate-style checks between SDLC phases (intake, scout, plan, critic, build, test, review, document, close) and outputs a clear PASS / CONDITIONAL / BLOCK verdict.
  • Defines and references a phase artifact catalog to validate required inputs, artifacts, and risk considerations for each phase.
  • Supports lightweight operation for low-risk flows and full-guardrails for high-stakes releases, with explicit gaps and remediation guidance.

Quick Start

Run a gate check after completing a phase to verify readiness for the next step.

Frequently Asked Questions about sdlc-checkpoint

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

FAQPage Schema
How do I enforce phase readiness gates across SDLC workflows?

You can enforce SDLC phase readiness by validating completed phase outputs against required artifacts before advancing. The gate check produces a clear PASS, CONDITIONAL, or BLOCK verdict with explicit gaps.

What is the best way to verify SDLC artifacts before moving to the next phase?

Verifying SDLC artifacts involves checking completed phase outputs against a phase artifact catalog. This ensures required inputs and risk considerations are met, outputting structured remediation guidance for any missing items.

Can I apply phase gating to both lightweight and high-stakes release workflows?

Yes, phase gating supports lightweight operation for low-risk flows and full-guardrails for high-stakes releases. It adjusts validation strictness based on the workflow type and risk tier provided as inputs.

How do I identify missing or weak outputs when checking phase completion?

To identify missing or weak outputs during phase completion, run a gate check that validates produced artifacts. It returns a structured gaps list detailing what is missing and providing explicit remediation guidance.

What inputs do I need to perform an SDLC phase gate check?

Performing an SDLC phase gate check requires inputs including the workflow type, the completed phase, the next phase, artifacts produced, and the risk tier. These inputs drive the validation logic and verdict generation.

Which SDLC phases are supported by phase gating verification?

Phase gating verification supports all SDLC phases including intake, scout, plan, critic, build, test, review, document, and close. Each phase transition is validated to ensure outputs are complete before advancing.