aped-arch

Generate architecture decisions from PRD and UX inputs with traceability.

2|Updated Mar 12, 2026

Search Tags:#architecture #system design #Claude Code #PRD #ADR #decision workflow #FR/NFR

Ready to run

npx skills add https://github.com/yabafre/aped-claude --skill aped-arch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aped-arch
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-arch
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

APED Architecture turns ambiguous product requirements into a coherent, decision-driven architecture that downstream agents can implement consistently without drifting.

Core Features & Use Cases

Incremental architecture gates that build architecture.md step-by-step with resume support and explicit user validation.
Traceable decisions that cite PRD FR/NFR IDs as architectural law for later phases.
Council-based convergence for major, high-stakes choices (DB, auth, API paradigm, frontend framework, infra) with minority views preserved.

Quick Start

Use aped-arch after you have a PRD and UX inputs ready, then choose Continue when the architecture gate menu appears.

Frequently Asked Questions about aped-arch

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

FAQPage Schema

How do I turn PRD requirements into buildable system design?▼

System design from PRD inputs is produced by applying incremental architecture gates that generate disciplined decisions, ensuring downstream agents implement consistently without drifting.

How does architecture traceability work for functional and non-functional requirements?▼

Architecture traceability links technical decisions directly to PRD FR/NFR IDs, treating them as architectural law so downstream phases can validate constraints and verify implementation consistency.

What is the best way to handle high-stakes architecture decisions like database or API paradigm selection?▼

High-stakes architecture decisions are resolved through council-based convergence, which evaluates major choices like DB or frontend framework while preserving minority views for future reference.

Can I resume system design generation if the workflow pauses midway?▼

Yes, the architecture workflow supports incremental per-subphase writing with resume capability, allowing you to pause and continue building the architecture document step-by-step through user gates.

When do I need ADR sharding for architecture decisions?▼

ADR sharding is needed for hard-to-reverse trade-offs in system design, isolating complex architectural decisions into discrete records to manage risk and preserve decision context.

Do I need a complete PRD before starting the architecture decision workflow?▼

Yes, the architecture workflow requires PRD and UX inputs as prerequisites to transform ambiguous product requirements into coherent, decision-driven architecture before epic and story creation.