sdlc-automation

SDLC Automation Platform — AI-Powered Software Development Lifecycle

Drop a meeting transcript in. Get requirements, documentation, sprint plans, tickets, architecture, code, tests, and deployment configs out. For ANY industry domain.

---

Install (1 command)

claude plugin marketplace add richard-devbot/claude_code_sdlc_automation && \
claude plugin install sdlc-automation@claude_code_sdlc_automation

Restart Claude Code. Type /sdlc — all 22 pipeline commands appear.

---

Quick Start (3 steps)

Step 1 — Add your transcript

cp your_meeting_notes.txt inputs/transcript.txt
# No transcript yet? Use a sample:
cp inputs/samples/healthcare_transcript.txt inputs/transcript.txt

Step 2 — Start the pipeline

/sdlc-start

Or choose an execution mode:

Command	Mode	Best for
/sdlc-start	Interactive	First run, full control over decisions
/sdlc-parallel	Parallel DAG	Speed — each agent gets a fresh 200K context window
/sdlc-sequential	Sequential	Debugging — one agent at a time

Step 3 — Review your deliverables

outputs/PROJECT_COMPLETE_SUMMARY.md   ← full project summary
outputs/EXECUTIVE_DASHBOARD.md        ← one-page stakeholder view

---

Overview

The SDLC Automation Platform is an end-to-end software development lifecycle engine built on Claude Code's agent pipeline. It takes a raw client meeting transcript — from a Zoom call, a Teams recording, or handwritten discovery notes — and autonomously produces every deliverable a development team needs: structured requirements, BRD/FRD/SOW documentation, sprint plans, Jira-ready tickets, system architecture, code scaffolding, test plans, deployment configurations, cost estimates, security threat models, and compliance matrices. The entire pipeline is orchestrated through a chain of 15 AI agents that communicate via structured JSON contracts, with a DAG-based execution model that runs independent phases in parallel. It works for any industry domain — healthcare, fintech, e-commerce, education, government, and more — with automatic domain detection and compliance-aware generation.

---

Architecture

Pipeline Flow (DAG-Based Parallel Execution)

                               +---------------------+
                               |  Meeting Transcript  |
                               +----------+----------+
                                          |
                          +---------------+---------------+
                          |                               |
                   +------v------+                 +------v------+
                   | 00 Environ- |                 | 01 Tran-    |
                   |    ment     |                 |   script    |
                   +------+------+                 +------+------+
                          |                               |
                          +---------------+---------------+
                                          |
                                   +------v------+
                                   | 02 Require- |
                                   |    ment     |
                                   +------+------+
                                          |
                          +---------------+---------------+
                          |                               |
                   +------v------+                 +------v------+
                   | 03 Documen- |                 | 04 Planning |
                   |   tation    |                 |             |
                   +------+------+                 +------+------+
                          |                               |
                          +---------------+---------------+
                                          |
                          +---------------+---------------+
                          |                               |
                   +------v------+                 +------v------+
                   | 05 Jira /   |                 | 06 Architec-|
                   |   Tickets   |                 |    ture     |
                   +------+------+                 +------+------+
                          |                               |
                          |                        +------v------+
                          |                        | 12 Security | (optional)
                          |                        | Threat Model|