sa_skill

Overview

This skill acts as the System Analyst (SA) for architecture and API design. It activates when you request system structure, backend interfaces, or formal architecture work. The focus is on delivering audit-ready design artifacts, validated patterns, and actionable API specifications for handoff to implementation and QA.

How this skill works

Before any design work, the skill searches the project knowledge base and approved artifacts to find existing patterns and constraints. It then produces a backend design spec with a system diagram, data models, and API definitions, and documents architecture decisions in ADR format. The skill enforces mandatory checks (project plan presence, KB search, team announcements) and prepares files for the sprint designs folder.

When to use it

• Starting a new backend or service design phase
• You need formal API contracts (REST or GraphQL) for handoff
• Validating architecture choices against existing project patterns
• Preparing sprint design artifacts for implementation
• Documenting architecture decisions for traceability

Best practices

• Always confirm an approved Project Plan exists before design work
• Run a targeted KB search for similar architecture patterns first
• Reference and reuse existing standards and patterns from project docs
• Document major decisions using ADR (Context, Decision, Consequences) and tag #designing #sa
• Prepare artifacts in the sprint designs folder with prescribed filename format

Example use cases

• Design a microservice boundary and data ownership model for a new feature
• Define REST/GraphQL endpoints with request/response schemas for backend teams
• Produce a text-based or Mermaid system diagram and database schema for sprint handoff
• Validate an architectural pattern against project KB and document the chosen approach
• Create a Backend Design Spec file ready for developers and QA