claude-sdlc-agents

Use this skill when working on Yandex Cloud infrastructure — provisioning clusters, databases, buckets, VMs; writing OpenTofu / Argo CD / Crossplane; setting up GitLab CI pipelines for infra; onboarding a new tenant; or reviewing a `tofu plan`. Encodes the modern 2026 default stack (OpenTofu Stacks + Argo CD + Crossplane + external-secrets → YC Lockbox), the blast-radius classification for applies, and the discipline rules that keep IaC repeatable — plan-as-review-artifact, no long-lived tokens, semver-pinned modules, no manual UI steps in bootstrap.

Use this skill at the start of every Plane Conductor agent run. Provides the shared session-start checklist (greeting, project context loading, common Plane STOPs) and the boilerplate every role re-uses (mention rules, comment-only communication, no @-mentioning the next agent). Read this before doing any role-specific work.

Use this skill when working as a Business Analyst (the business-analyst role) — eliciting requirements from stakeholders, structuring requirements per BABOK v3 framework, classifying needs by type (Business / Stakeholder / Solution / Transition), and applying analysis techniques (5 Whys, MoSCoW, INVEST, Stakeholder Analysis). Read this skill before composing interview questions or filling the REQUIREMENTS document.

Use this skill when working as the final Reviewer (the reviewer role) — comprehensive cross-cutting review before closing a Plane issue. Encodes OWASP Top 10 (security), SOLID principles (code quality), Google engineering practices (review checklist), cross-trace validation between REQUIREMENTS, SPEC, CHANGES, tests, design.

Use this skill when working as a tester (the api-tester for API testing, the ui-tester for UX/E2E testing) — designing test cases per ISTQB Foundation framework, choosing the right test design technique (Equivalence Partitioning, Boundary Value Analysis, Decision Table, State Transition, Use Case Testing), classifying test levels and types, structuring bug reports. Read before composing a test plan or executing test cases.

Use this skill when an agent in the Plane Conductor pipeline writes any artifact — REQUIREMENTS, SPEC, ARCH_REVIEW, SPEC_APPROVED marker, Design brief, PLAN, CHANGES, test plan, bug report, REVIEW. Provides canonical Markdown templates so all agents produce uniform structure across the pipeline. Read the matching template before composing your artifact.

Use this skill when a coder (django-developer / vue-developer / react-developer) or a tester (api-tester / ui-tester) executes a multi-step PLAN. Encodes (a) how to size steps with the 5-budget AND-filter and vertical-slice rule, (b) the one-step-per-invocation loop with checkbox state in PLAN sub-issue description, and (c) the self-handoff that lets plane-conductor re-spawn the agent for the next step.

Use this skill when working as the architect — reviewing a SPEC produced by the system-analyst, evaluating ADRs, checking cross-trace to REQUIREMENTS, producing ARCH_REVIEW with verdict (APPROVED / CHANGES_REQUIRED) and the SPEC_APPROVED marker. Encodes a 7-area review checklist (Area 0 implementation-readiness + 6 technical areas), SOLID and DDD lenses, and ADR governance.

Use this skill whenever an agent interacts with Plane (https://plane.so) — picking up issues, creating sub-issues for artifacts, posting comments, finding artifacts by label, mentioning users, handling re-entry (continuation vs rework), or completing work. Triggers on any usage of mcp__plane__* tools. Encodes the Plane Conductor pipeline protocol.

Use this skill when working as a coder (the django-developer / the vue-developer / the react-developer) and your implementation is complete — what documentation to update, where, and how. Covers docstrings, README updates, API endpoint docs, ADR status updates, migration notes, inline comments. The author of the change is responsible for the documentation.

Use this skill when working as the system-analyst — translating REQUIREMENTS into a technical SPEC. Encodes C4 Model for architecture views, DDD bounded contexts for service mapping, REST API design conventions, IEEE 29148 terminology, and ADR (Architecture Decision Records) pattern. Read before composing or revising SPEC sections.

Use this skill when working as the designer — producing UX flow + Figma frame inventory for SPEC implementation, evaluating accessibility (WCAG 2.1 AA), applying Nielsen usability heuristics, choosing platform conventions (Material 3 web / iOS HIG / desktop). Also covers UX-Review mode — verifying frontend implementation against design.