sdlc

Sdlc Skill

[!IMPORTANT] Route a task to the next synced SDLC workflow based on current artifacts and repo state.

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

SDLC Router Workflow

Goal: Select the next native workflow without loading every workflow body, while preserving a traceable BA -> PM -> IT Department handoff for offshore delivery.

Steps

1. Inspect state:

   • User request; infer operator_profile (business | hybrid | technical) per common-operator-profile and carry it in every Handoff Payload.
   • Search docs/brd/, docs/prd/, and docs/srs/ for a matching [slug]; if absent, use the newest BRD or git status. Slug = lowercase kebab-case, minted once at brainstorm-feature, reused verbatim downstream; never re-derived.
   • If multiple candidates exist, list them and ask whether to focus, consolidate, or sequence.
   • Baseline reference: docs/requirements-standards-baseline.md
   • Existing ticket, BRD-lite brief, PRD, SRS/FRS design, implementation plan, task list, walkthrough, UAT signoff, deployment report, release notes, and retro
   • Jira, ADO, Zephyr, or other MCP context when already configured
   • Changed files and current test status
   • Offshore delivery context: business owner, product owner, implementation owners, QA owner, timezone/cadence constraints, environments, release window, and dependency teams
   • Requirement trace health: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> test evidence

2. Choose next workflow (apply tie-break order when multiple bullets match: (1) workflow explicitly named by the operator or by the latest recommended_next_workflow, (2) production-incident/urgent-regression signals, (3) earliest missing artifact along the chain below — never skip forward past a gap, (4) cross-cutting audits only on request or as a pre-release gate):

   • Unclear idea, missing business case, missing stakeholder owner, or missing measurable value (BRD-lite / Why, BA-owned intake) -> brainstorm-feature
   • BRD-lite exists or business direction is clear but product scope, priorities, acceptance criteria, rollout, or delivery plan are unclear (PRD / What, PM-owned planning) -> plan-feature
   • Scale, topology, capacity, or store choice unsettled, or an existing system needs an architecture audit -> system-design-session
   • PRD exists but technical behavior/contracts unclear (SRS/FRS / How) -> design-solution
   • Architecture, auth, trust boundaries, compliance controls, or agent/runtime safety need deeper technical validation -> design-solution
   • BRD-lite, PRD, or SRS/FRS exists but readiness unclear -> implementation-readiness
   • Approved plan with BRD/PRD/SRS trace and testable ACs needs code -> implement-feature
   • Production incident or urgent regression -> incident-hotfix
   • Bug ticket needs fix (non-urgent) -> dev-fix
   • Ticket or cross-functional change needs specialist fanout, AC coverage, and PR metadata review -> review-ticket
   • Design arrives as an artifact (diagram, doc, board export, IaC) and needs review -> review-system-design
   • PR diff needs focused merge-risk review -> code-review
   • Implementation GREEN but ACs lack executable E2E/mobile coverage, or an E2E suite is red after a previously green slice -> test-loop.
   • Code complete but unproven -> verify-work
   • Fix implemented and ticket has a UAT/Jira flow -> verify-bug
   • verify-work PASS on a feature, business acceptance not yet granted -> uat-signoff
   • Business acceptance granted and release window open -> deploy-release
   • Deployed and needs user-facing communication -> publish-notes
   • Trace health unknown before release or handoff -> traceability-audit
   • Session ending with unfinished work or context handoff -> session-report
   • Deployed or communicated, capture standards/process lessons -> retro-learn
   • Repo-wide health/debt question with no single feature in scope -> codebase-review