skills.rest
chaimt
chaimtCOMMUNITY
Explore all skills by this author →
Website𝕏@chaimtGitHub

adlc-architect-implement

Convert ADRs into a DAG-based Architecture Description with a three-phase workflow.

Updated Apr 21, 2026
Search Tags:#automation#architecture#documentation#adr#dag#subsystem#architecture-description
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-architect-implement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adlc-architect-implement
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/adlc-architect-implement
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-architect-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs contain decisions and rationale but do not directly produce a publishable architecture description. This skill orchestrates a three-phase workflow that translates ADRs into a comprehensive Architecture Description (AD.md) using a DAG-based, multi-agent approach, enabling plan, execute, and summarize stages with per-subsystem views and cross-subsystem consistency.

Core Features & Use Cases

  • Transform ADRs into a unified Architecture Description (AD.md) across multiple sub-systems.
  • Plan, execute, and summarize with ADR-driven conflict resolution and lifecycle management.
  • Maintain resumable state, per-subsystem DAG customization, and template-driven view generation.

Quick Start

Provide your ADR set and run the architect implement workflow to generate AD.md.

Frequently Asked Questions about adlc-architect-implement

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

FAQPage Schema
How do I convert ADRs into a complete architecture description?▼

To convert ADRs into an architecture description, provide your ADR set to trigger a multi-agent workflow that generates a unified AD.md file. This process applies phased planning, per-subsystem views, and cross-subsystem conflict resolution.

What is a DAG-based workflow for architecture documentation?▼

A DAG-based workflow for architecture documentation uses a directed acyclic graph to orchestrate multi-agent tasks across Plan, Execute, and Summarize phases. This structure enables per-subsystem DAG customization and resumable state persistence during AD generation.

Can I generate per-subsystem architecture views from existing ADRs?▼

Yes, you can generate per-subsystem architecture views from existing ADRs using template-driven view generation. The workflow isolates subsystems within the DAG to apply customized views and resolve cross-subsystem conflicts.

Does this architecture generation approach handle ADR lifecycle and conflict resolution?▼

Yes, this architecture generation approach handles ADR lifecycle rules and cross-subsystem conflict resolution. It applies ADR-driven decision logic during the Execute phase to ensure consistency across the final architecture description.

What is the best way to maintain state during a multi-agent architecture generation process?▼

The best way to maintain state during multi-agent architecture generation is using a workflow that supports state persistence. This allows the Plan, Execute, and Summarize phases to resume seamlessly without losing subsystem progress.

Related Skills

Explore More Software Engineering Skills→
ZendevveZendevve
20

mcaf-adr-writing

Create standardized Architecture Decision Records with templates and Mermaid diagrams.

Community
Intermediate
chaimtchaimt

architect-implement

Generate a unified AD.md from ADRs using multi-agent DAG orchestration.

Community
Advanced
spencerbeggsspencerbeggs

design-split

Split monolithic design documents into subsystem-specific files with bidirectional links.

Community
Advanced
chaimtchaimt

speckit-adlc-architect-implement

Generate a unified AD.md from ADRs using multi-agent DAG orchestration.

Community
Advanced