spec-architect

Design functional and technical specifications with modules, contracts, and verification criteria.

Updated May 9, 2026

Search Tags:#architecture #specification #verification #traceability #contracts #boundaries

Ready to run

npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill spec-architect-gustavogutierrez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-architect
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/spec-architect
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill spec-architect-gustavogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you convert vague requirements or product intent into clear, implementation-ready system and software architecture specifications with explicit modules, contracts, boundaries, and verification criteria.

Core Features & Use Cases

High-level functional + technical spec design that separates what the system must do from how it will be built.
Module, contract, and boundary modeling so responsibilities, interfaces, and out-of-scope items are unambiguous.
Traceability and verification planning to ensure requirements map to architecture decisions and measurable acceptance checks.

Quick Start

Use the spec-architect skill to design a high-level functional and technical specification for your system from a PRD by asking the AI to produce the complete required output structure.

Frequently Asked Questions about spec-architect

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

FAQPage Schema

How do I turn rough product requirements into implementation-ready architecture specifications?▼

To turn rough product requirements into architecture specifications, define functional and technical layers covering scope, modules, contracts, and boundaries. This process separates what the system must do from how it will be built, ensuring implementation-ready outputs with explicit traceability and measurable verification criteria.

What is the best way to define system boundaries and contracts during early architecture planning?▼

Defining system boundaries and contracts during architecture planning involves modeling module responsibilities and interfaces explicitly. This ensures out-of-scope items are unambiguous and creates clear functional separation between components, which establishes well-defined failure modes and agent-oriented guardrails for the system.

Can I generate traceability and verification criteria from a PRD without writing source code?▼

Yes, you can generate traceability and verification criteria directly from a PRD without writing source code. Architecture spec design maps product requirements to architecture decisions and measurable acceptance checks across functional, module, data, integration, and operational layers without implementation.

Does spec design work for upgrading existing system baselines across multiple architectural layers?▼

Spec design works for existing system baselines by applying architecture-level planning across functional, module, contract, data, integration, and operational layers. It transforms current baselines into structured, implementation-ready outputs with explicit traceability and well-defined failure modes.

How do I specify measurable non-functional requirements and failure modes in a technical spec?▼

To specify measurable non-functional requirements and failure modes in a technical spec, structure the architecture design with explicit constraints and agent-oriented guardrails. This ensures requirements map directly to architecture decisions and measurable acceptance checks without writing source code.