sdlc

Automates SDLC pipeline orchestration from issue creation to learnings capture with resumable progress and session logging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating and automating the entire Software Development Lifecycle pipeline—from issue creation through implementation, documentation, and learnings—so teams can reproduce consistent workflows with minimal manual overhead.

Core Features & Use Cases

  • End-to-end SDLC orchestration that sequences sub-skills (e.g., /create-issue, /create-requirements, /create-plan, /create-tests, /deploy-pr, /create-learnings) and backtracks when blockers arise.
  • Phase-level invocation and per-phase execution, allowing teams to run individual stages or the full pipeline as needed.
  • Persistent artifact and progress management, including session logs and learnings capture to enable resumable work and auditability.

Quick Start

Run /sdlc with an optional phase name to start the full pipeline from issue to learnings.

Frequently Asked Questions about sdlc

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

FAQPage Schema
How do I automate the full software development lifecycle pipeline from issue creation to deployment?

Automating the SDLC pipeline is done by orchestrating phases from issue creation through requirements, planning, tests, and deployment. It sequences sub-skills end-to-end and supports backtracking when blockers arise to ensure consistent, reproducible workflows.

Can I run individual phases of the SDLC pipeline instead of the entire process?

Running individual phases of the SDLC pipeline is supported through phase-level invocation. You can execute specific stages like planning or testing independently, while persistent progress management and session logging allow resuming work later.

How do I ensure traceability and reproducibility when orchestrating an automated development workflow?

Traceability in an automated development workflow is enforced through state transitions, backtracking rules, and session logging. Persistent artifact management captures outputs and learnings, enabling auditability and resumable work across pipeline executions.

What is the best way to manage pipeline artifacts and capture learnings across multiple development sessions?

Managing pipeline artifacts across sessions is handled by persistent progress management that logs state transitions and outputs. It automatically captures learnings at the end of the lifecycle, ensuring work remains resumable and auditable.

Do I need any specific dependencies or external tools to orchestrate the SDLC pipeline?

Orchestrating the SDLC pipeline requires no external dependencies or specific components. It operates as a standalone automation skill that sequences sub-skills and manages state transitions natively.

When should I not use a full end-to-end SDLC orchestration approach?

End-to-end SDLC orchestration may be excessive for isolated tasks or ad-hoc changes that do not require full traceability. If your workflow does not need state transitions, session logging, or artifact management, a lighter manual approach is more efficient.