sdlc-start

Coordinates a prompt-bound Agentic SDLC loop with checkpointed phase routing and failure classification.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-start-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-start
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/sdlc-start
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-start-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Managing a multi-phase software development lifecycle with an AI agent often loses state across context resets, mixes prompt intent with project specs, and retries failures without diagnosis. This Skill binds each run to an immutable prompt revision, checkpoints every state transition, and routes work through requirements, design, implementation, validation, and documentation phases with deterministic recovery. ## Core Features & Use Cases - Prompt-bound run coordination: Initialize a private prompt workspace and run objectives by exact prompt ref or file, with immutable revisions, FIFO queuing, and idempotent resume after context loss. - Checkpointed phase routing: Select exactly one next skill per iteration (requirements, design, steering, execution, commit, docs) based on checkpoints, fingerprints, and evidence rather than conversation memory. - Deterministic failure handling: Classify every gate failure through a repair-control contract, route ambiguous failures to troubleshooting, and enforce retry budgets and stop conditions. - Use Case: A developer initializes a workspace in a project folder, writes an Ask prompt describing a feature, and repeatedly runs the prompt; the coordinator drives requirements refinement, design validation, TDD execution, and documentation updates while surviving session restarts. ## Quick Start Ask the agent to run sdlc-start workspace init in your project folder, then run your prompt file with sdlc-start run to start the coordinated SDLC workflow.

Frequently Asked Questions about sdlc-start

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

FAQPage Schema
How do I start an Agentic SDLC run with sdlc-start?

Run `sdlc-start workspace init` in your project folder to create a private prompt workspace, then edit the generated prompt's Ask section and invoke `sdlc-start run <prompt-ref-or-file>`. Repeating run on the same prompt steers the active run; unchanged completed prompts return ALREADY_COMPLETE.

How does the SDLC coordinator resume after context loss?

Every state transition writes a checkpoint and history entry under the agent home's sdlc-runs directory. On resume, the coordinator reads the latest checkpoint, current state, feature queue, and fingerprints, then reconciles disagreements by preferring the newest complete checkpoint.

Can sdlc-start implement code or create pull requests directly?

No. The coordinator only routes to specialized phase skills such as sdlc-implement-plan, sdlc-commit, and create-pr. It never edits requirements or design freely, commits, pushes, or merges; those boundaries are enforced as explicit Must Not rules.

What happens when a validation gate fails during a run?

Every gate failure produces an immutable failure event routed to sdlc-classify-failure. Proven mechanical causes take the shortest repair route, while ambiguous or persistent failures enter a troubleshoot diagnostic branch before any repair dispatch, with budgets and stop conditions checkpointed.

Does sdlc-start work in both Codex and Claude Code?

Yes. Use $sdlc-start in Codex, /sdlc-start in Claude Code, or /skills:sdlc-start in the Claude plugin. The skill loads agent-host references to adapt to the selected runtime while preserving the same invocation policy and workflow ownership.

Why does a run stop with WORKFLOW_UPGRADE_REQUIRED?

This occurs when an unfinished active run lacks a managed prompt binding or contains legacy execution coordinator schema records. Completed unbound history stays readable, but the workflow refuses to adopt or migrate it; start a new prompt-bound run instead.