architecture

Decide where durable architecture and design documents belong in the repository.

158|12|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/nteract/nteract --skill architecture-nteract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/nteract/nteract/tree/main/.agents/skills/architecture
Command: npx skills add https://github.com/nteract/nteract --skill architecture-nteract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture and documentation framing for cross-cutting repo decisions, ADRs, memos, PRDs, implementation plans, audits, measurements, runbooks, and source-grounded proposals. Use when deciding where durable docs belong, drafting or moving architecture/product/design docs, or promoting .context/ notes into repo docs.

Core Features & Use Cases

  • Guided documentation strategy: helps teams decide where durable docs belong and how to structure ADRs, PRDs, and runbooks.
  • Documentation governance: promotes workflow for placing notes into docs/ directories and maintaining taxonomy.
  • Use Case: When starting an initiative that requires long-term documentation and cross-functional input, use this to draft architecture decisions and place them in docs/adr or docs/prd.

Quick Start

Create a durable architecture document in docs/adr and outline the initial decision in an ADR.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I structure architecture decision records and product docs in a repository?

To structure architecture decision records and product docs, place durable documents in dedicated repository folders like docs/adr and docs/prd to maintain long-term cross-functional alignment and governance.

Where should durable runbooks and memos live in a git repo?

Durable runbooks and memos should live in organized docs/ directories, specifically under docs/runbooks and docs/memos, ensuring repository documentation taxonomy remains structured and accessible.

What is the best way to promote context notes into permanent repository docs?

The best way to promote context notes into permanent repository docs is using a documentation governance workflow that moves temporary notes into structured docs/adr or docs/prd folders for durable alignment.

When do I need to create an architecture decision record for my project?

You need to create an architecture decision record when starting an initiative that requires long-term documentation and cross-functional input, ensuring durable design decisions are grounded in the repository.

Can I use this documentation framing approach for audits and implementation plans?

Yes, this documentation framing approach supports audits and implementation plans by guiding the placement of source-grounded proposals and cross-cutting design documents into appropriate repository directories.

How does documentation governance maintain taxonomy for architecture docs?

Documentation governance maintains taxonomy for architecture docs by enforcing a workflow that places ADRs, PRDs, and memos into specific docs/ folders, preventing disorganized or misplaced repository documentation.