capability-discoveryInventory the capabilities already available in the current session so the SDLC team can reuse them. Use at pipeline start (Phase 0) to discover project-local agents and skills (.claude/agents, .claude/skills), agents/skills from other installed plugins, and connected MCP servers, plus the repo's CL
cicd-failure-diagnosisDiagnose a failing CI/CD run — retrieve the failed-step logs, classify the root cause (config | code/test | infra/transient), and route or fix. Use when a CI run is red, e.g. by the ci-doctor agent and the /sdlc-fix-ci loop. Forge-aware; reuses the cicd-pipeline-audit fix catalog.
cicd-pipeline-auditAudit CI/CD pipeline config (CI workflows + Dockerfiles) for security, correctness, reliability/cost, and plugin-convention issues. Use when reviewing or generating pipeline config — by the pipeline-reviewer (Phase 4) and the release-engineer (Phase 5). Prefers real linters, falls back to a checklis
clean-code-standardsApply pragmatic clean-code standards — DRY, YAGNI, KISS, separation of concerns, naming, small functions, low complexity. Use when writing or reviewing code to keep it readable and maintainable. Cited by the implementer, QA, and code reviewer as a shared rubric.
database-designDesign and review relational schemas, MySQL-focused. Use when the design or implementation involves data modeling — tables, keys, relationships, normalization, indexing, constraints, migrations, and query/EXPLAIN optimization. Used by the architect (data model) and implementer (schema/migrations).
devops-gcpContainerize and ship apps with Docker, CI/CD pipelines that deploy on a MANUAL trigger, and Google Cloud Platform. Use when setting up build/deploy, writing Dockerfiles or CI workflows, or planning a release. Primary skill of the release-engineer.
end-to-end-testingDrive a running web app end-to-end as a real user (mouse + keyboard) with Playwright and record a screen video — with a visible mouse pointer — for review. Use in the review phase (the e2e-tester agent and /sdlc-e2e) to produce a per-feature recording the user approves before merge. No-ops when ther
framework-expertiseFramework- and architecture-specific implementation guidance. Use when building or reviewing code in a known stack (Laravel, Filament, Vue, React, Next, Electron, Ionic, shadcn, Tailwind) or when choosing between microservice and monolithic architectures. A router — load only the reference file(s) m
git-conventionsApply Conventional Commits and Conventional Branch naming, the three-tier branch model, the per-task branch workflow, and the promotion policy (every stage merge goes through a PR/MR; merged non-protected branches are deleted, the protected main/staging/development are not). Use when committing, cre
notion-syncMirror the SDLC pipeline to a Notion workspace as a Jira-Scrum board — a shared Projects registry plus, per project, a hub page holding its own Tickets and Sprints databases with backlog and active-sprint views, plus sprint-planning Ready sign-off. Use when syncing artifacts/status to Notion (the /s
performance-and-costKeep the whole application performant and cost-effective. Use when designing, implementing, or reviewing for latency, throughput, resource use, and cloud cost. Covers N+1 queries, caching, async/queues, payload size, and right-sizing. Used by the architect, implementer, and code-reviewer.
project-memoryConventions for the repo-local, committed agent-memory store at .claude/agent-memory/. Use whenever reading project memory at the start of an SDLC run, forwarding it to subagents, or persisting a durable project fact. Defines the MEMORY.md index + per-fact file layout, what is worth remembering, and
release-managementManage versioning and release communication. Use when cutting a release — semantic-versioning decisions, changelog entries, and release notes. Used by the release-engineer.
requirements-engineeringTurn a raw request into clear, testable requirements. Use when writing 01-requirements.md — eliciting user stories, INVEST-quality criteria, Given/When/Then acceptance criteria, scope boundaries, and assumptions. Primary skill of the requirements-analyst.
scrum-masterAgile/Scrum methodology expert — the orchestrator's scrum master. Facilitates the sprint lifecycle: backlog refinement, Definition of Ready/Done, sprint planning, scope discipline, and sprint review/retro. Use when planning or running sprints (the /sdlc-plan and /sdlc-sprint commands and the orchest
sdlc-artifactsConventions for SDLC pipeline artifacts and handoffs. Use whenever creating, reading, or updating files under docs/sdlc/<slug>/, writing the 00-manifest.md, or applying the QUESTIONS FOR USER / NO QUESTIONS clarification protocol. Defines the artifact layout, manifest schema, feature slug rules, and
sdlc-gatesFlow-control primitives for the SDLC pipeline — GATE (human approval), LOOP-GUARD (N tries then ask), and PRECONDITION (state guard). Apply whenever presenting an approval gate, running a fix/repair loop, or refusing an action based on sprint state. Used by the orchestrator (skills/sdlc) and the /sd
sdlcOrchestrate the SDLC pipeline end to end. Use when the user runs /sdlc with a request, or asks to "run the SDLC pipeline", "build this feature properly", or take a feature/fix from requirements through design and implementation. Routes work to the requirements-analyst, solution-architect, and implem
software-architectureTurn requirements into a technical design. Use when writing 02-design.md — decomposition into components with clear boundaries, interfaces/contracts, data flow, a file-level build sequence, trade-off analysis, and a test strategy outline. Primary skill of the solution-architect.
solid-principlesApply and review against the five SOLID object-oriented design principles. Use when designing components, writing classes/modules, or reviewing code for maintainability and coupling. Language-neutral guidance with review heuristics for the architect, implementer, and code reviewer.
stack-detectionDetect and adapt to any repository's tech stack and conventions. Use as the FIRST step of every SDLC agent, before doing phase work, to identify language, framework, package manager, test runner, build/lint tooling, and the repo's own conventions (including its CLAUDE.md). Ensures the team follows e
technical-writingWrite clear technical documentation. Use when producing or updating a README, API docs, usage guides, or changelogs. Audience-first structure and conventions. Primary skill of the tech-writer.
test-engineeringDesign test cases — UAT (stakeholder-readable acceptance scenarios) and automated tests adapted to the project's stack. Use when planning or writing tests, verifying acceptance criteria, or deciding coverage. Primary skill of the qa-tester; also used by the implementer.
threat-modelingDesign-time security risk analysis. Use when reviewing a design or change for what could go wrong — assets, trust boundaries, attack surface, and STRIDE categories. Used by the security-reviewer and consulted by the architect.
ui-ux-designApply modern UI/UX design language. Use when designing or building user interfaces — layout, visual hierarchy, accessibility, responsive/cross-platform (web/mobile/desktop), and Tailwind as a design system. Used by the architect and implementer.
vulnerability-scanningFind and prevent concrete code-level security vulnerabilities. Use when writing or reviewing code that handles input, auth, data access, files, or external requests. Covers XSS, SQL injection, CSRF, SSRF, IDOR, command injection, insecure deserialization, auth/session flaws, secrets exposure, and de