sdlc

Plugin sdlc from marketplace sdlc-workflow in palakornims/sdlc-workflow-ai-driven-development. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• breakdown

  Phase 3 Breakdown. Decompose an approved design into tiered TASK- tickets, delivery plan, and execution-ordered backlog via the project-manager agent.

• codex

  Turn the optional OpenAI Codex second review on or off for this project, or show its current state and whether the Codex CLI, login, and plugin are ready.

• design

  Phase 2 Design. Produce architecture, ADRs, contracts, data model, threat model (OWASP Top 10), and gap analysis from an approved plan via the solution-architect agent.

• doctor

  Diagnose the sdlc workflow environment - MCP tool-name mismatches, stale or duplicate Playwright MCP server processes, port conflicts, missing tools, and status drift between task tickets and the backlog. Reports findings and the exact command to fix each one.

• implement

  Phase 4 Implement. Implement one approved TASK- ticket on its own branch via the dotnet-developer agent, then run /codex:rescue on the result when Codex review is on.

• init

  Scaffold the AI-driven SDLC workflow into the current project - docs folders, templates, logs, WORKFLOW.md, CLAUDE.md section, settings, sdlc.config.json (Codex review on/off), Codex and Playwright config, setup script. Idempotent; never overwrites existing files.

• log

  Append a human action to the correct workflow log (review, test, validation, or task ticket) so the mandatory logging rule is satisfied for approvals, Codex runs, dismissals, and sign-offs.

• plan

  Phase 1 Plan. Turn a feature idea into an approved PRD, REQ- requirements with Given/When/Then scenarios, and STORY- tickets via the product-owner agent.

• review

  Phase 5 Code Review. Review a task's PR with the code-reviewer agent plus a second independent reviewer - Codex (/codex:rescue and the human-only Codex commands) when Codex review is on, otherwise a Sonnet second-opinion review.

• status

  Show where every feature sits in the workflow (approvals, tasks, open findings, defects, validation) and the next command to run.

• triage

  Phase 5 triage-and-fix loop. Register code-reviewer, Codex (when on), or human review findings, get solution-architect and dotnet-developer decisions, fix agreed findings one commit each, and re-review, logging every step.

• validate

  Phase 7 Validation. The product-owner agent walks every acceptance scenario on the running system, builds traceability, routes VAL- findings, and stops for release sign-off.

Subagents (6)

• code-reviewer

  Code Reviewer for the Code Review phase. Use after the dotnet-developer has opened a PR (or after any code change) to review the diff for correctness, Clean Architecture conformance, .NET/C# best practice, OWASP Top 10 (2025) controls, and test adequacy, consolidate second-reviewer findings the main

• dotnet-developer

  .NET / C# Developer for the Implement phase. Use to implement one approved TASK- ticket at a time on its own branch, following Clean Architecture, the dotnet-skills plugin practices, .NET and C# best practice, and the OWASP Top 10 (2025) controls from the threat model, then opening a PR and stopping

• product-owner

  Product Owner for the Plan phase and the Validation phase. Plan mode - use when a new feature, idea, or requirement arrives and needs to be analysed, turned into a PRD with numbered requirements and Given/When/Then acceptance criteria, and broken into story tickets ready for the Design phase. Valida

• project-manager

  Project Manager for the Breakdown phase. Use after the Design documents are approved to decompose the design into an ordered work breakdown of TASK- tickets and sub-tasks under docs/03-tasks/, core structure and main feature first, then components, with dependencies, milestones, and sizing. Follows

• qa-engineer

  Principal QA Engineer for the Test phase. Use after a task or story is merged to define the test strategy, drive the Playwright test agents (planner, generator, healer) from the Given/When/Then acceptance criteria, review generated tests, run the full suite (.NET unit/integration plus Playwright end

• solution-architect

  Principal Solution Architect for the Design phase. Use after the Plan documents are approved to produce the architecture, ADRs, API contracts, data model, threat model, and gap analysis under docs/02-design/. Applies Clean Architecture, the current OWASP Top 10 (2025), and software engineering best

Similar plugins