# Sdlc Agentic Pipeline

> Orchestrate a complete multi-agent SDLC pipeline powered by Huawei Cloud CodeArts Agent. 8 agents (PM, Backend, Frontend, Code Reviewer, Tester, DevOps, Architect, Figma Design) across 10 steps from requirements through deployment. Integrates GitHub, Jira, SonarCloud, Semgrep, JFrog, Playwright, Huawei Cloud ECS, Azure DevOps, Figma. Trigger: "start agentic flow", "SDLC pipeline", "agentic DevOps pipeline", "multi-agent development workflow", "figma to code".

- Skill: `codeartsagent/sdlc-agentic-pipeline` (Agent Skill, multi-file: 29 files)
- Install (CLI): `npx skillmds@latest add codeartsagent/sdlc-agentic-pipeline`
- Raw SKILL.md: https://api.skillmd.com/api/skills/codeartsagent/sdlc-agentic-pipeline/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: codeartsagent (https://skillmd.com/u/codeartsagent)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/codeartsagent/sdlc-agentic-pipeline

---


# SDLC Agentic Pipeline

8 agents collaborate asynchronously through Jira comments as a message bus.
Figma MCP is consumed exclusively by `figma-design-agent`; all other agents
read Figma data through `figma-extract.md` and the updated SDD docs.

## Pipeline Steps

| Step | Agent(s) | Action |
|------|----------|--------|
| 0 | PM + Frontend/Backend/DevOps | Onboarding: auto-provision agents, tool selection |
| 0.DA | Architect | Design phase: classify task, DDD/SDD/TDD (reads figma-extract.md) |
| 0.F | Figma Design | (Optional, pre-Step 0.DA) Figma-vs-SDD diff, update SDD docs |
| 1 | PM | Requirement breakdown, PRD, batch Jira tasks |
| 1b | Frontend/Backend | Requirement review (parallel via Jira async) |
| 2 | PM + Developer | Sprint start + SDD setup |
| 3 | Frontend/Backend | Code dev (parallel), Semgrep pre-scan, PR (reads figma-extract.md) |
| 4 | Code Reviewer | PR review, secret scanning, approval |
| 5 | Tester + PM + Dev | E2E testing + visual diff vs Figma + auto-merge feature PRs |
| 6 | DevOps | CI/CD (auto-triggered) + JFrog + SonarCloud |
| 7 | PM + Developer | Release review + merge (dev -> main) |
| 8 | PM + DevOps | Deploy auth + execution (Huawei Cloud ECS) |
| 9 | PM + Developer | Sprint close, retro, HTML report |

## PR Operation Routing

| Scenario | PR Operations Owner |
|----------|---------------------|
| Only Frontend active | Frontend Agent |
| Only Backend active | Backend Agent |
| Both active | Backend Agent (primary) |

## Agents

| Agent | File | Steps |
|-------|------|-------|
| PM | `references/agents/pm-agent.md` | 0, 1, 1b, 2, 5, 7, 8, 9 |
| Backend | `references/agents/backend-agent.md` | 0, 1b, 2, 3, 5, 7, 9 |
| Frontend | `references/agents/frontend-agent.md` | 0, 1b, 2, 3, 5, 7, 9 |
| Code Reviewer | `references/agents/code-reviewer-agent.md` | 4 |
| Tester | `references/agents/tester-agent.md` | 5 |
| DevOps | `references/agents/devops-agent.md` | 0, 6, 8 |
| Architect | `references/agents/architect-agent.md` | 0.DA |
| Figma Design | `references/agents/figma-design-agent.md` | 0.F (pre-Step 0.DA) |

PM Agent = orchestrator (`mode: all`); all others = subagents (`mode: subagent`).
`figma-design-agent` runs in `mode: all` and is the EXCLUSIVE consumer of Figma MCP
(`figma.get_figma_data`, `figma.download_figma_images`). All other agents consume
Figma data through `specs/<YYYY-MM-DD-...>/figma-extract.md` and the SDD docs
that `figma-design-agent` updates after user-confirmed diff.

## Prerequisites

Step 0 (Service Onboarding) must complete first. See `references/setup/service-onboarding.md`.

### Step 0.0.5 - Multi-Tool Selection

PM Agent presents 4 multiselect questions (MCP servers, SDD, TDD, DDD).
Selection persisted to `.codeartsdoer/tool-selections.json`. See `references/setup/multi-tool-selection-plan.md`.
Figma MCP is selectable as part of Q1 (MCP & Services); selecting it triggers Step 0.11 onboarding.

### Step 0.F - Figma-vs-SDD Diff (optional, runs when `figma` selected AND SDD docs already exist)

1. User invokes `figma-design-agent` with a Figma URL + target SDD directory
2. Agent calls `figma.get_figma_data` and `figma.download_figma_images`
3. Agent writes `specs/<YYYY-MM-DD-...>/figma-extract.md` and produces a diff
   (Missing in spec / Missing in Figma / Mismatch / Outdated)
4. User confirms each category; agent updates `spec.md` / `design.md` / `tasks.md`
5. Agent hands off to `pm-agent` with the routing breakdown
   (`frontend` / `backend` / `tester` / `code-reviewer` / `devops`)

## Methodology Skills

| Methodology | Tools | Primary/Supplementary Rule |
|-------------|-------|---------------------------|
| SDD | SDD Toolkit, OpenSpec | First selected = PRIMARY; others = SUPPLEMENTARY |
| TDD | Playwright (E2E), Postman/Newman (API), Jest/Vitest/Pytest/JUnit (Unit) | Each tool owns its own test layer; all must pass |
| DDD | Context Mapper, EventStorming, Structurizr | First selected = PRIMARY; others = SUPPLEMENTARY |
| DevOps | Azure DevOps CLI | Mutually exclusive with GitHub + Jira |
| Design-to-Code | Figma MCP | Figma data → SDD docs → frontend/backend implementation |

Built-in utility skills (always on, not selectable): `ide-tool`, `doc-expert`, `pptx`, `data-analysis`, `prd`, `frontend-design`, `i18n-integration`, `skill-installer`

## Permission Setup

Deny-by-default. Only explicitly allowed skills can be invoked.

| Agent | Additional Allowed Skills (beyond `ide-tool`) |
|-------|-----------------------------------------------|
| PM | `creating-sdd-directory`, `data-analysis`, `doc-expert`, `managing-design-document`, `managing-spec-document`, `managing-tasks-document`, `openspec`, `pptx`, `prd`, `skill-installer` |
| Backend | `creating-sdd-directory`, `managing-spec-document`, `managing-design-document`, `managing-tasks-document`, `openspec`, `skill-installer` |
| Frontend | `creating-sdd-directory`, `frontend-design`, `i18n-integration`, `managing-spec-document`, `managing-design-document`, `managing-tasks-document`, `openspec`, `skill-installer` |
| Code Reviewer | _(none)_ |
| Tester | `playwright-cli`, `skill-installer` |
| DevOps | _(none)_ |
| Architect | `creating-sdd-directory`, `managing-spec-document`, `managing-design-document`, `managing-tasks-document`, `skill-installer` + TDD/DDD tool permissions (dynamic) |
| Figma Design | `brainstorming`, `managing-spec-document`, `managing-design-document` |

## Directory Structure

```
sdlc-agentic-pipeline/
|-- SKILL.md
`-- references/
    |-- setup/
    |   |-- service-onboarding.md
    |   |-- multi-tool-selection-plan.md
    |   `-- critical-warnings.md
    |-- agents/
    |   |-- pm-agent.md
    |   |-- backend-agent.md
    |   |-- frontend-agent.md
    |   |-- code-reviewer-agent.md
    |   |-- tester-agent.md
    |   |-- devops-agent.md
    |   |-- architect-agent.md
    |   |-- figma-design-agent.md
    |   `-- shared/
    |       `-- developer-agent-base.md

    |-- pipeline.md
    |-- branch-strategy.md
    |-- report-spec.md
    |-- config-reference.md
    |-- skill-registry.json
    `-- templates/
        |-- mcp-settings.json
        |-- ci-cd.yml
        |-- sonar-project.properties
        |-- env-template.env
        |-- set-secrets.js
        |-- add_ssh_key.py
        |-- SKILL.md
        |-- apply-tool-selections.ps1
        |-- apply-tool-selections.sh
        `-- sprint-scripts/
            |-- README.md
            |-- sprint-start.ps1
            |-- sprint-start.sh
            |-- sprint-close.ps1
            `-- sprint-close.sh
```

## Quick Start

1. **Create a GitHub repository manually** — the pipeline never creates repos
2. Copy `sdlc-agentic-pipeline/` into `.codeartsdoer/skills/`
3. Append `sdlc-agentic-pipeline=true` to `.codeartsdoer/skills/ProjectSkillStatus.txt`
4. Run Step 0 (Service Onboarding) — if `figma` is selected, run Step 0.11 first
5. (Optional) Run Step 0.F (`figma-design-agent`) when an SDD directory + Figma URL exist
6. Say "start agentic flow"

## Reference Index

| Topic | File |
|-------|------|
| Per-step orchestration | `references/pipeline.md` |
| Branch strategy & PR merge gate | `references/branch-strategy.md` |
| HTML report specification | `references/report-spec.md` |
| Config templates & runtime files | `references/config-reference.md` |
| Critical warnings | `references/setup/critical-warnings.md` |
| Service onboarding | `references/setup/service-onboarding.md` |
| Multi-tool selection plan | `references/setup/multi-tool-selection-plan.md` |
| Skill registry | `references/skill-registry.json` |
| E2E visual diagram | `references/sdlc-e2e-diagram.md` |

## Execution Notes

- Repo creation is manual, human-only — no agent ever calls `github_create_repository`
- PM Agent is the only agent that can authorize deployment and close sprints
- PM Agent is READ-ONLY with the repository; all git writes delegated to developer agents
- DevOps Agent does NOT create or merge PRs
- Existing artifacts are sacred (Option A) — never modified without explicit user approval
- Tester Agent exclusively owns E2E/Playwright tests; Frontend/Backend own unit/component tests
- CI/CD is auto-triggered on push to `dev`
- Pipeline degrades gracefully — steps that depend on unselected tools are skipped
- Azure DevOps CLI is mutually exclusive with GitHub + Jira — when selected, the `azure-devops-cli` skill replaces GitHub MCP (Repos), Jira MCP (Boards), and GitHub Actions (Pipelines)
- **Figma MCP is EXCLUSIVE to `figma-design-agent`** — no other agent may call
  `figma.get_figma_data` or `figma.download_figma_images`; all other agents read
  `specs/<YYYY-MM-DD-...>/figma-extract.md` and the SDD docs that
  `figma-design-agent` updates after user-confirmed diff.