skills.rest
CornFedKratos
CornFedKratosCOMMUNITY
Explore all skills by this author →
GitHub

aidlc-project-touchchain

Coordinate AI-DLC delivery through gate-based touchchain with multi-role transitions.

Updated Apr 11, 2026
Search Tags:#workflow#planning#execution#epic#gate#touchchain#handoff-card
One-click install
npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-project-touchchain
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aidlc-project-touchchain
Source: https://github.com/CornFedKratos/s3-aidlc/tree/main/plugins/s3-aidlc/skills/aidlc-project-touchchain
Command: npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-project-touchchain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate end-to-end AI-DLC delivery with hard stops and structured role transitions across CPO, CTO, and CQO to maintain governance, accountability, and efficient ticket flow.

Core Features & Use Cases

  • Gate-based orchestration: load the appropriate role skill (CPO, CTO, CQO, etc.), execute gates, and capture governance artifacts.
  • Hand-off card handling: locate, validate, and interpret the hand-off card to drive sequential Epic tickets through the chain.
  • Velocity and state management: track velocity signals, epic backlog, and session ledgers across gates to align with project goals.

Quick Start

Initiate a touchchain run for a ticket by approving Gate 0 to load the CPO skill and begin State 1 work.

Frequently Asked Questions about aidlc-project-touchchain

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

FAQPage Schema
How do I orchestrate end-to-end AI-DLC delivery with enforced governance and role transitions?▼

A gate-based touchchain orchestrates AI-DLC delivery by enforcing hard stops and multi-role transitions across CPO, CTO, and CQO. It drives sequential Epic tickets through structured gates to maintain accountability and generate governance artifacts.

How do I manage cross-functional planning and Go/No-Go decisions for Epic-level tickets?▼

You manage cross-functional planning by loading role skills like CPO, CTO, or CQO to execute gates and capture artifacts. The touchchain requires explicit Go/No-Go decisions to progress Epic-level tickets through the delivery lifecycle.

What is a hand-off card and how does it drive workflow execution?▼

A hand-off card is a structured artifact that the touchchain locates, validates, and interprets to drive sequential Epic tickets through the chain. It ensures proper state management and velocity tracking across cross-functional role transitions.

Can I track velocity readiness and epic backlog status during AI-DLC execution?▼

Yes, you can track velocity readiness and epic backlog status across gates. The touchchain manages session ledgers and velocity signals to align cross-functional execution with your project goals and governance requirements.

When should I use a gate-based touchchain for AI-DLC project planning?▼

Use a gate-based touchchain for AI-DLC planning when Epic-level tickets require cross-functional governance, complexity classification at Gate 0, and structured artifact generation for Insight Journal and Growth Log tracking.

How do I start a touchchain run for an Epic ticket?▼

To start a touchchain run, approve Gate 0 to classify complexity and assess velocity readiness. This loads the CPO skill to begin State 1 work, initiating the structured workflow execution for your Epic ticket.

Related Skills

Explore More Product & Management Skills→
CornFedKratosCornFedKratos

aidlc-verification-before-completion

Enforce evidence-based verification before AIDLC gate completion claims.

Community
Advanced
humansyshumansys
71

rai-session-close

Close working sessions by capturing outcomes and updating memory.

Official
Advanced
CornFedKratosCornFedKratos

aidlc-requesting-code-review

Automate pre-merge code review gating for AIDLC projects.

Community
Intermediate
SJTU-IPADSSJTU-IPADS
7

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from backlog details.

Official
Advanced