backend-architecture

Generates a backend architecture document by interviewing users on project-relevant technical decisions.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill backend-architecture-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architecture
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/backend-architecture
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill backend-architecture-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a backend architecture document from a blank page is slow and often produces generic content disconnected from the actual project. This Skill reads your existing product, business, and design docs, identifies which architectural decisions actually matter for your project, and interviews you only on those topics before writing a tailored document. ## Core Features & Use Cases - Context-aware decision detection: Scans PRD, domain model, data model, business rules, UX spec, and slice docs to determine which decision areas (stack, API style, auth, real-time, sync, module boundaries) are relevant. - Adaptive interview: Asks only the questions that apply to this project, one at a time, instead of a fixed questionnaire. - Tailored document generation: Writes docs/04_tech/backend_architecture.md containing only the sections supported by actual decisions, including open questions for later. - Use Case: After defining your domain model and data model, run this Skill to produce a backend architecture doc that links stack, API, and data-access choices directly to your project's entities, rules, and first slice. ## Quick Start Ask the assistant to create the backend architecture document for this project based on the existing docs.

Frequently Asked Questions about backend-architecture

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

FAQPage Schema
How do I create a backend architecture document for my project?▼

Run the backend-architecture skill after your product and business docs exist. It scans those docs, identifies which decisions matter, interviews you on topics like stack, API style, and auth, then writes docs/04_tech/backend_architecture.md.

What documents does the backend architecture skill read first?▼

It reads the PRD, product principles, domain model, business rules, data model, UX spec, and any slice discovery files under docs/. The content of these files determines which interview questions are asked.

Does the skill ask the same questions for every project?▼

No. It always asks about stack, API style, and authentication, but only asks about data access, rule enforcement, real-time, sync, or module boundaries when the existing docs indicate those concerns are relevant.

What happens if no project docs exist yet?▼

The skill falls back to a standard set of questions covering stack, API style, auth, deployment, database, and structure. The resulting document will be more generic since no project context was available.

Where is the backend architecture document saved?▼

The output is written to docs/04_tech/backend_architecture.md, and the folder is created if it does not exist. If multiple docs folders are found, the skill asks which one to use.