sdlc-pipeline

Orchestrates SDLC documentation flow across 13 phases with dependency and signature gate enforcement.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill sdlc-pipeline-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-pipeline
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/pipeline/sdlc-pipeline
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill sdlc-pipeline-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a 34-document, 13-phase software specification process manually makes it easy to lose track of what is done, what is blocked, and what comes next. This Skill resolves the next runnable document, enforces prerequisite dependencies and human signature gates, and reports overall pipeline progress. ## Core Features & Use Cases - Next-Skill Resolution: Reads the project checklist and canonical SDLC model to determine which document skill is runnable, blocked, pending signature, or complete. - Dependency & Gate Enforcement: Applies a fixed dependency table so no document is generated before its prerequisites are signed and its approval authority is assigned. - Progress Reporting: Supports commands to report the next step, run it immediately, show one phase's status, or print the full remaining path to completion. - Use Case: After the functional specification is signed, ask what is next and the pipeline reports that experience design is runnable while nonfunctional specification remains blocked until experience design is signed. ## Quick Start Ask the agent to run the pipeline and tell you what the next runnable SDLC document is for the current project.

Frequently Asked Questions about sdlc-pipeline

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

FAQPage Schema
How do I find the next document to produce in an SDLC pipeline?▼

Run the pipeline command and it reads the project checklist, skips signed documents, checks prerequisites for each pending skill in canonical order, and reports the first runnable one. If several phases run in parallel, it lists all runnable options.

How do signature gates work in an SDLC documentation workflow?▼

Each document requires sign-off from its assigned approval authority before dependent documents unlock. A document stays pending until signed, and collective roles stay partial until their quorum is met.

Can SDLC phases run in parallel?▼

Phases 1 through 7 are strictly sequential. Phases 8 through 11 (Development, Quality, Security, Infrastructure) open together after Governance is signed, so multiple skills can be runnable at once.

What happens if a prerequisite document is not signed?▼

The dependent skill is marked blocked and the pipeline continues scanning for other runnable skills. It never generates a document whose prerequisites are unsigned or whose approval authority is unassigned.

When can the experience design phase be skipped?▼

It can be skipped only when the product has no human interface at all. The skip must be recorded with a reason in the project configuration, otherwise downstream requirements documents stay blocked.