phase-handoff

Standardize SDLC phase handoff artifacts and checklists with frontmatter and gate checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalized phase handoffs ensure artifacts carry necessary context between SDLC stages, reducing reliance on chat history and manual notes.

Core Features & Use Cases

  • Standardized artifact templates and frontmatter for intake briefs, scout artifacts, execution packs, critic verdicts, and validation reports.
  • Automated gate checks and workflow guidance to prevent advancing with missing or inconsistent data.
  • Resumable handoffs: supports resuming after interruption by reconstructing context from plan artifacts and plan history.

Quick Start

Create an intake brief and the minimal handoff artifacts for the next phase using the templates described.

Frequently Asked Questions about phase-handoff

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

FAQPage Schema
How do I standardize SDLC phase handoffs to preserve context between stages?

You can standardize SDLC phase handoffs by applying structured artifact templates and automated gate checks at the end of each phase to preserve context. This guarantees machine-readable data and prevents advancing with missing information.

What are SDLC gate checks and how do they validate workflow artifacts?

SDLC gate checks are automated validation rules applied during phase transitions to verify artifact consistency and frontmatter requirements. They ensure required handoff data is present and machine-readable before advancing the workflow.

How do I resume an SDLC workflow after an interruption without losing context?

Resuming an SDLC workflow after an interruption requires reconstructing context from existing plan artifacts and plan history. Resumable handoffs surface the required artifacts and next steps to seamlessly continue the current phase.

Do I need specific frontmatter formats for SDLC artifact templates?

Yes, structured SDLC artifact templates require specific frontmatter to ensure consistent, machine-readable handoff data. Defined frontmatter requirements apply to intake briefs, execution packs, and validation reports.

What is the best way to create structured artifacts for intake and scout phases?

The best way to create structured artifacts for intake and scout phases is using standardized templates with defined frontmatter requirements. This ensures briefs and execution packs carry necessary context without relying on manual notes.