architecture

Generates architecture documents, OpenAPI contracts, and milestone roadmaps from business requirements.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/FerEscobarDev/Specture --skill architecture-ferescobardev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/FerEscobarDev/Specture/tree/main/skills/architecture
Command: npx skills add https://github.com/FerEscobarDev/Specture --skill architecture-ferescobardev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump from requirements straight into coding, which causes frontend and backend to drift apart with mismatched endpoints and shapes. This Skill turns business requirements into a validated architecture document, a single-source-of-truth API contract, and a dependency-ordered ROADMAP before any code is written. ## Core Features & Use Cases - Architecture Document: Produces a stack-grounded, tech-agnostic architecture with Mermaid diagrams, component slugs, and boundaries, validated by the architecture-validator agent. - API Contract: Generates an OpenAPI contract (or GraphQL SDL / proto equivalent) plus a readable companion, with bidirectional traceability between boundary capabilities and operations. - ROADMAP Generation: Creates a milestone/epic roadmap where frontend epics declare the operationIds they consume and backend epics declare the ones they implement, enforcing dependency order. - Use Case: After finishing requirements discovery for a web app, invoke this Skill to produce architecture.md, api-contract.openapi.yaml, and ROADMAP.md, each gated by validator approval before the build phase begins. ## Quick Start Ask the assistant to design the architecture and generate the roadmap from the existing business requirements document.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I generate a software architecture document from business requirements?▼

Provide business requirements, a locked stack definition, and any architecture decision records, then produce a structured document covering components, communication patterns, data model, and cross-cutting concerns. Each output passes a validator gate before the next phase begins.

How to keep frontend and backend API contracts in sync?▼

Use a single OpenAPI contract file as the source of truth where every operation has a stable operationId. Backend epics declare the operations they implement and frontend epics declare the ones they consume, so drift is caught during roadmap validation.

When should the API contract be skipped?▼

Skip the contract only when there is no network boundary at all, such as a standalone CLI, library, or desktop app with no API. A pure backend service exposing endpoints still requires the contract.

Does this approach support GraphQL or gRPC instead of REST?▼

Yes. If the stack declares GraphQL or gRPC, the contract is produced as an SDL schema or proto file with the same stable-identifier discipline, plus a readable companion document. OpenAPI is the default for REST.

What happens if the architecture validator rejects a document?▼

The validator returns REJECTED with specific violations, and the document must be fixed and re-dispatched. The workflow does not proceed to the next part until the validator returns APPROVED.