--- title: "agent-sdlc" description: "A full SDLC crew of agent roles that turn an idea into specs, designs, test cases, a tracked execution plan and TDD-built code." canonical: https://agentpluginsdirectory.com/plugins/agent-sdlc last-updated: 2026-10-02 --- # agent-sdlc A full SDLC crew of agent roles that turn an idea into specs, designs, test cases, a tracked execution plan and TDD-built code. - Slug: agent-sdlc - Publisher: Dritan Xhezo - Repository: https://github.com/dritanxhezo/agent-sdlc-plugins - Manifest: plugins/agent-sdlc/plugin.json - Version: 0.5.4 - License: MIT - Category (editorial): productivity - Skills: 13 (brd-author, decision-interview, defect-triage, execution-plan, frd-author, hld-author, lld-author, pr-flow, sdlc-orchestrator, tdd-implement, test-case-author, test-executor, work-breakdown) - MCP servers: 3 (github, playwright, sdlc-tracker) - Stars: 0 - Repository created: 2026-08-15 - Repository last pushed: 2026-09-02 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/agent-sdlc - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What agent-sdlc does, in the publisher's words A crew of SDLC agent roles: business analysis, architecture, QA, project management, test-driven development and debugging. Skills (13): sdlc-orchestrator routes work; brd-author and frd-author capture requirements; hld-author and lld-author design; test-case-author and test-executor verify; work-breakdown and execution-plan plan and publish; tdd-implement and pr-flow build and merge; defect-triage diagnoses. decision-interview is the shared one: the four decision-dense skills run it before drafting, so the artifact records what you chose rather than what the agent guessed. Agents (6): business-analyst, solution-architect, qa-engineer, project-manager, developer, debugger. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/dritanxhezo/agent-sdlc-plugins/HEAD/plugins/agent-sdlc/README.md ## Skills - brd-author: Writes a Business Requirements Document capturing the problem, stakeholders, business goals, scope boundaries, success metrics and numbered business requirements. Use at the start of a feature, before any functional detail or technical design, or when a request needs its business case made explicit. - decision-interview: Interviews the user about the decisions an artifact is about to commit to, asking dependency-ordered rounds of numbered questions that each carry a recommended answer, and converting whatever stays unanswered into recorded assumptions. Use from brd-author, hld-author, lld-author and work-breakdown… - defect-triage: Debugs a reported failure systematically, reproduce, capture evidence, form a hypothesis that explains all of it, probe it cheaply, then fix behind a regression test, and records the root cause in a DEF-### report. Use when a test fails, a bug is reported, production behaviour is wrong, or an inv… - execution-plan: Publishes a work breakdown to GitHub, one issue per T-###, milestones per phase, Projects v2 board fields, via the sdlc-tracker MCP, then renders a read-only execution plan document with a Mermaid Gantt chart, dependency order and per-phase status. Use after work-breakdown to make GitHub Issues t… - frd-author: Writes a Functional Requirements Document that turns each BR-### business requirement into numbered functional requirements (FR-###) and non-functional requirements (NFR-###), each with Given/When/Then acceptance criteria and a traceability table back to the BRD. Use after a BRD exists and before a… - hld-author: Writes a High Level Design that decomposes a feature into C-### components with responsibilities, owned data, interactions and a Mermaid diagram, records technology choices with rejected alternatives, and shows how each NFR is satisfied by a named design element. Use after an FRD exists and before… - lld-author: Writes a Low Level Design taking each C-### component from the HLD down to implementation-ready detail, module and file structure, interfaces and method signatures, data schemas, API contracts, sequence diagrams, error handling, named constants and the test seams that make TDD possible. Use after… - pr-flow: Takes a completed task from working tree to merged, branch naming, conventional commits referencing the task, pre-push verification, opening a pull request that closes the task issue, handling review and CI feedback, then merging and updating the tracker. Use after a task's tests are green and it… - sdlc-orchestrator: Routes a feature request through the SDLC roles in order, business analysis, architecture, QA, planning, TDD development, and tracks which phase a feature is in. Use when starting a new feature, when asked to "build" or "deliver" something end to end, or when unsure which SDLC role should act nex… - tdd-implement: Implements one tracker task at a time under strict test-driven development, failing test first, minimum code to pass, then refactor, driven by the task's FR-### acceptance criteria and TC-### test cases. Use when the execution plan exists and a task is ready to build, when resuming a partially bu… - test-case-author: Derives numbered TC-### test cases from the functional requirements and low level design, each with preconditions, test data, steps, expected result, priority and type, plus a coverage matrix proving every FR-### is covered. Use after the FRD and LLD exist and before work is broken into tasks, or w… - test-executor: Runs the TC-### test cases for a feature against the built code, detecting the project's own test tooling first, and records Pass/Fail/Blocked/Not run with evidence in a timestamped run report, raising a defect entry for every failure. Use after implementation to verify a feature, before a release… - work-breakdown Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized. ## MCP servers - github: transport: http; url: https://api.githubcopilot.com/mcp/ - playwright: transport: stdio; command: npx -y @playwright/mcp@latest - sdlc-tracker: transport: stdio; command: node ${PLUGIN_ROOT}/mcp/sdlc-tracker/src/index.mjs Read from the plugin's own mcp.json. Environment variable names only, never values.