squad-architecture

Plan and document system architecture using YAML and Markdown templates.

48|3|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/picassio/pi-squad --skill squad-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-architecture
Source: https://github.com/picassio/pi-squad/tree/main/src/skills/squad-architecture
Command: npx skills add https://github.com/picassio/pi-squad --skill squad-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit provides a framework for defining and documenting system architecture, making it easier to create structured projects and maintain clear APIs and shared types.

Core Features & Use Cases

  • Project Structure: Offers guidance on defining component boundaries and using monorepos for shared dependencies.
  • API Contract Definition: Aids in detailing API endpoints with consistent formats and specifications.
  • Shared Types: Encourages defining TypeScript interfaces and validation schemas for robust data models.
  • Technical Decisions: Documents decisions and their rationales to ensure consistency and clarity for future reference.
  • Handoff Quality: Ensures outputs are precise, leaving no ambiguity for downstream components.

Quick Start

Run the 'squad-architecture' skill to create a new system architecture for your project.

Frequently Asked Questions about squad-architecture

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

FAQPage Schema
How do I document system architecture and API contracts for a new project?

You can document system architecture and API contracts using provided YAML and Markdown templates that define project structures, API endpoints, and shared type specifications to ensure clear boundaries and consistent technical documentation.

What is the best way to define shared types and TypeScript interfaces for data models?

The best way to define shared types is by specifying TypeScript interfaces and validation schemas within your architecture documentation, ensuring robust data models and clear boundaries for downstream components.

How do I structure a monorepo for shared dependencies and component boundaries?

You can structure a monorepo for shared dependencies by defining clear component boundaries and using architecture templates that guide project structure organization to ensure consistency and clarity across the codebase.

Can I use YAML and Markdown for technical decision documentation in system architecture?

Yes, you can use YAML and Markdown for technical decision documentation. The architecture framework allows you to document decisions and their rationales to ensure consistency and clarity for future technical reference.

Does this system architecture template work for API design workflows in software engineering?

Yes, the system architecture framework is designed for software engineering API design workflows. It provides detailed templates for API endpoints with consistent formats and specifications to facilitate clear project and API design.

Why document API contract definitions and project structure for downstream components?

Documenting API contract definitions and project structure ensures handoff quality, leaving no ambiguity for downstream components. It maintains clear APIs and shared types for robust software engineering workflows.