architecture-doc

architecture-doc is a skill for Claude Code, Codex from ihatesea69/kiro-kit. It costs 63 tokens per session (1,271 once invoked), scanned A, original, MIT.

A method for writing a formal solution architecture document in Word. It records a system’s context, requirements, design views, technical decisions, and quality requirements.

In plain words
What is it for?
Use it for high-level or detailed designs, formal design sign-off, migration planning, and vendor proposals.
Why use it?
It creates a durable document that teams can review, approve, and use as a reference during implementation or audits.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for high-level or detailed designs, formal design sign-off, migration planning, and vendor proposals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ihatesea69/kiro-kit/architecture-doc
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ihatesea69/kiro-kit --skill architecture-doc
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for architecture-doc

README.md
[![agentmods](https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/architecture-doc/github.svg)](https://agentmods.dev/skills/ihatesea69/kiro-kit/architecture-doc)
Your own site
<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/architecture-doc"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/architecture-doc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for architecture-doc

Your own site · 80×15
<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/architecture-doc"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/architecture-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,271 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.01271
Opus 5.5 $0.00025 $0.00508
Sonnet 5.5 $0.00013 $0.00254
Haiku 4.5 $0.00006 $0.00127

Measured 1mo ago against content hash e3c01814fc8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

architecture-doc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

presets/sa/skills/architecture-doc/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architecture Document (SAD)

Generate Solution Architecture Documents as .docx files with python-docx. The document is the durable, reviewable record of a design; the deck (see the architecture-deck skill) is its presentation companion.

When to Use

  • "Write the solution architecture document"
  • "Turn this spec into an HLD/LLD"
  • Formal design sign-off, vendor RFP responses, audit evidence
  • Any .docx deliverable whose subject is a system architecture

Prerequisites

python -c "import docx" 2>/dev/null || pip install python-docx

Diagrams are embedded as PNG exports of their .drawio / .mmd sources (drawio-ai render, mmdc) — same rule as the deck skill: never fork diagram content into a second tool.

SAD Template

Use these sections in this order. Sections may be marked "Not applicable — " but never silently dropped.

  1. Document Control — version table (version, date, author, change), reviewers/approvers, distribution.
  2. Executive Summary — one page max: problem, proposed solution, cost band, key risks.
  3. Business Context — drivers, goals, success metrics, stakeholders (table: name, role, concern).
  4. Requirements
    • Functional requirements summary (reference the spec's requirements.md IDs — do not duplicate full text).
    • Non-functional requirements (table: NFR, target, measurement method) — availability, latency, throughput, RTO/RPO, security/compliance, cost ceiling.
  5. Constraints & Assumptions — technology mandates, budget, deadlines, team skills, regulatory scope.
  6. Architecture Views (the core — one subsection per view)
    • Context view (C4 L1 diagram + external dependency table)
    • Functional/container view (C4 L2–3 diagrams, responsibility table)
    • Data view (data stores, classification, retention, lineage)
    • Deployment view (regions/AZs, environments, sizing, scaling policy)
    • Security view (identity, network boundaries, encryption, secrets)
    • Operations view (observability, alerting, runbooks, DR)
  7. Architecture Decisions — ADR summary table (ID, decision, status, rationale); link full ADRs from docs/adr/.
  8. Well-Architected Review — 6-pillar table: pillar, finding, severity, remediation.
  9. Risks & Mitigations — table: risk, likelihood, impact, mitigation, owner.
  10. Roadmap — phases with scope and exit criteria.
  11. Glossary & References

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 113 lines · 63 tokens per session scan A e3c01814fc8e

Subscribe to this mod's changes

architecture-doc is a skill published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 1,271 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.