architecture-spec-writer

Generate architecture specification documents with goals, interfaces, and rollout plans.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/KirillKlem/codex-skills --skill architecture-spec-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-spec-writer
Source: https://github.com/KirillKlem/codex-skills/tree/main/skills/architecture-spec-writer
Command: npx skills add https://github.com/KirillKlem/codex-skills --skill architecture-spec-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a clear, detailed, and implementation-oriented architecture specification document.

Core Features & Use Cases

  • Document Creation: Writes architecture specifications, design documents, or tech specs based on chosen architecture.
  • Implementation Guidance: Ensures the document acts as an engineering contract for implementation, detailing goals, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, observability, validation plan, and open questions.
  • Use Case: When a software architecture is chosen, this Skill helps in preparing a comprehensive document that guides the implementation process.

Quick Start

Write a design document for the chosen architecture 'my-architecture'.

Frequently Asked Questions about architecture-spec-writer

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

FAQPage Schema
How do I generate a system design document for my chosen architecture?

A tech spec serves as an engineering contract for implementation by defining goals, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, and observability metrics to guide developers.

What do I need to provide to create an architecture specification?

Creating a design document requires a chosen architecture and system context as inputs. The Skill processes these inputs to define invariants, interfaces, data flow, dependencies, failure modes, and validation plans.

How do I write a tech spec that includes rollout and observability plans?

A comprehensive architecture specification includes goals, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, observability, validation plan, and open questions to ensure complete implementation guidance.

What is the best way to document failure modes and data flow in a design document?

An architecture specification acts as an implementation contract by explicitly defining goals, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, observability, validation plan, and open questions.

Can I use this to generate implementation guidance for any system context?

An architecture specification acts as an engineering contract by detailing goals, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, observability, validation plan, and open questions for precise implementation guidance.