architect

Generate architecture designs and task breakdowns from requirements.

159|41|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill architect-atelier-fashion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/atelier-fashion/adlc-toolkit/tree/main/architect
Command: npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill architect-atelier-fashion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams design software architecture and decompose a requirement into actionable tasks, reducing ambiguity and speeding up project planning.

Core Features & Use Cases

  • Converts a high-level requirement into an architecture outline with major components and interactions.
  • Produces a task graph with dependencies suitable for task planning and scheduling.
  • Provides guidance on ADRs, decisions, and traceable design documents to support later review and implementation.

Quick Start

Plan the architecture for the incoming requirement by outlining the major components and drafting the initial task breakdown.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I generate architecture design and task breakdown from software requirements?

Architecture design generation works by analyzing approved requirements to outline major components, map dependencies, and produce a traceable task graph for project planning workflows.

What is the best way to decompose a high-level requirement into actionable engineering tasks?

Decomposing a requirement involves converting it into an architecture outline, identifying component interactions, and drafting a dependency-driven task graph suitable for engineering scheduling.

Can I use this approach for project planning across my software engineering team?

Yes, this approach applies to project planning workflows across software engineering teams, specifically for defining architecture, components, and task graphs from approved requirements.

How does requirement scope analysis and dependency mapping work for architecture design?

Requirement scope analysis and dependency mapping work by satisfying project constraints to generate traceable documentation, including required frontmatter, task templates, and ADR guidance.

Do I need approved requirements and specifications before starting architecture design?

Yes, approved requirements and specifications are needed as input because the architecture design and task breakdown process relies on analyzing these inputs to scope components and map dependencies.

What limitations exist when generating architecture components from a high-level requirement?

Limitations include reliance on the clarity of the initial requirement; ambiguous specifications will produce less effective architecture outlines and less accurate dependency mapping for the task graph.