sa

Transform product requirements into technical design blueprints with component breakdowns and data flows.

Updated Apr 22, 2026

Search Tags:#migration #system-architecture #data-modeling #api-design #technical-design #risk-analysis

Ready to run

npx skills add https://github.com/codetail-ai/skillwright --skill sa-codetail-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sa
Source: https://github.com/codetail-ai/skillwright/tree/main/roles/sa-agent
Command: npx skills add https://github.com/codetail-ai/skillwright --skill sa-codetail-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a feature request or PRD into a concrete technical blueprint when teams need to align on architecture before implementation.

Core Features & Use Cases

Breaks requirements into system components, responsibilities, and data flow.
Defines API contracts, database schema, migration strategy, and rollout plan.
Surfaces non-functional requirements, risks, assumptions, and open questions.
Use it for new feature architecture, redesigns, integration planning, and technical spike preparation.

Quick Start

Give the skill a PRD or feature description and ask it to produce a technical design document.

Frequently Asked Questions about sa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn product requirements into a technical design document?▼

To turn product requirements into a technical design, provide a PRD or feature description to generate a blueprint covering system architecture, API contracts, data modeling, and non-functional requirements for engineering alignment.

What is the best way to plan a database schema migration strategy for a new feature?▼

Planning a database schema migration strategy involves breaking down requirements into component responsibilities, defining the data model, and surfacing rollout plans and risks to ensure a safe architecture redesign.

Can I use a PRD to generate API contracts and system architecture?▼

Yes, a PRD can be transformed into API contracts and system architecture by extracting component interactions, defining data flows, and documenting implementation assumptions for engineer-ready blueprints.

How does technical design handle non-functional requirements and risk analysis?▼

Technical design handles non-functional requirements and risk analysis by surfacing system constraints, identifying potential architectural risks, and documenting open questions and implementation assumptions for the engineering team.

When do I need a technical blueprint for system architecture redesign?▼

You need a technical blueprint for system architecture redesign when aligning on component breakdowns, integration planning, data flows, and rollout strategies before beginning actual implementation.

What limitations should I expect when generating component breakdowns from a feature request?▼

Generating component breakdowns relies on the completeness of the initial feature request, meaning open questions and unresolved implementation assumptions may persist if the input requirements lack sufficient detail.