agentic-engineering-architecture

Designs system boundaries, contracts, data models, and ADRs for approved specifications.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-architecture-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentic-engineering-architecture
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/skills/agentic-engineering-architecture
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-architecture-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved specification into a concrete technical architecture is error-prone: teams skip explicit system boundaries, data ownership, and decision records, leading to costly rework later. This Skill produces a complete architecture package before any implementation begins. ## Core Features & Use Cases - Architecture Package Generation: Produces system and trust boundaries, API contracts, data model and ownership, deployment topology, dependency policy, and quality attributes. - Decision Documentation: Records alternatives, ADRs, migration constraints, and verification implications, preferring reversible decisions and explicit compatibility boundaries. - Phase-Gated Workflow: Routes missing specifications or constraints back to earlier phases and stops before execution planning or implementation. - Use Case: After approving a product spec, invoke this Skill to design the service boundaries, choose technologies, document build-versus-buy decisions, and capture ADRs before handing off to implementation planning. ## Quick Start Use $agentic-engineering-architecture to design and document the technical architecture for the approved specification.

Frequently Asked Questions about agentic-engineering-architecture

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

FAQPage Schema
How do I design a technical architecture from an approved specification?▼

Invoke the architecture phase with your approved specification. It produces a package covering system and trust boundaries, contracts, data model and ownership, deployment view, dependency policy, quality attributes, alternatives, and ADRs.

What does the architecture package include?▼

The package includes system and trust boundaries, API contracts, data model and ownership, deployment topology, dependency policy, quality attributes, alternatives analysis, ADRs, migration constraints, and verification implications.

What happens if the specification is missing or incomplete?▼

The Skill routes the work back to the earlier specification phase rather than guessing. It requires an approved specification and constraints as input before designing the architecture.

Does this Skill handle implementation or execution planning?▼

No. It explicitly stops before execution planning or implementation. Its scope ends at delivering the architecture package with ADRs and verification implications for downstream phases.

When should architecture decisions be revisited with this Skill?▼

Use it for consequential architecture changes such as new integration contracts, multi-tenancy shifts, or technology replacements. It prefers reversible decisions and explicit compatibility boundaries when recording changes.