skills.rest
nholder88
nholder88COMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-planning

Generate architecture documents and an implementable backlog from feature requests.

2|Updated Mar 1, 2026
Search Tags:#planning#architecture#adr#backlog#threat-modeling#system-design
One-click install
npx skills add https://github.com/nholder88/ai-agent-workflows --skill architecture-planning-nholder88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-planning
Source: https://github.com/nholder88/ai-agent-workflows/tree/main/skills/architecture-planning
Command: npx skills add https://github.com/nholder88/ai-agent-workflows --skill architecture-planning-nholder88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture teams need to translate vague ideas into a coherent set of architecture artifacts and a ready-to-implement backlog.

Core Features & Use Cases

  • Generate system overview, component breakdown, deployment topology, API contracts, and data model specifications.
  • Produce ADRs, threat models, and observability architecture to guide secure, observable designs.
  • Create a ready-to-define backlog with acceptance criteria aligned to architecture decisions.

Quick Start

Provide a project idea or system request to generate architecture documents and a task backlog.

Frequently Asked Questions about architecture-planning

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

FAQPage Schema
How do I translate a feature request into architecture documents and a backlog?▼

Architecture planning converts a feature request into system overviews, component breakdowns, API contracts, and a ready-to-implement backlog. It generates traceable architecture decisions and acceptance criteria aligned with the requested feature.

Can I generate ADRs and threat models during early-stage system design?▼

ADRs and threat models are generated during early-stage system design to capture traceable architecture decisions. This approach ensures feature decomposition includes security considerations and deployment topology definitions across systems and services.

What is the best way to plan deployment topology and API contracts for a new system?▼

The best way to plan deployment topology and API contracts is providing a project idea to generate architecture documents. This outputs data model specifications, deployment topology, and API contracts alongside an actionable implementation backlog.

Do I need a fully detailed specification to start architecture planning?▼

A fully detailed specification is not required; a simple project idea or system request is sufficient to start architecture planning. The process decomposes vague ideas into structured artifacts like component breakdowns, ADRs, and a defined backlog.

Why does feature decomposition require an observability plan and data models?▼

Feature decomposition requires an observability plan and data models to ensure the resulting backlog is implementable and traceable. Generating these architecture artifacts guarantees the system design remains coherent, observable, and secure across services.

Related Skills

Explore More Software Engineering Skills→
BasharAmsoBasharAmso
1

Plan From Idea

Transform a project idea into a PRD stub and initial task queue.

Community
Intermediate
sablier-labssablier-labs
7

etherscan-verification

Verify deployed smart contracts on Etherscan-compatible explorers with Forge.

Official
Advanced
barrydobsonbarrydobson

devops

Advocate DevOps principles including CI/CD, IaC, automated testing, monitoring, and security scanning for delivery pipelines.

Community
Intermediate
williamzujkowskiwilliamzujkowski
6

Architecture Decision Framework

Generate ADRs, MADRs, Y-statements, and C4 diagrams from requirements.

Community
Advanced