Architecture designer

Skill Razaib-khan/ForgeWeave/src/forgeweave/templates/qwen/.qwen/skills/architecture-designer

Behavioral execution framework for AI agents — define deterministic, portable skills & agents across OpenCode, Claude Code, Gemini CLI, and Qwen Code.

Install

npx -y skills add Razaib-khan/ForgeWeave --skill architecture-designer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Designs system-level structures including modules, services, data flow, and scaling strategy before implementation begins

SKILL.md

2.8 KB, as published. Nobody here has run it

Architecture Designer

Purpose

Design system-level architecture before any code is written. Produces module boundaries, service decomposition, data flow diagrams, and scaling strategy. Ensures the architecture is coherent, testable, and aligned with project constraints.

When to Use

Starting a new project or major subsystem
The current architecture cannot support upcoming requirements
Performance, scalability, or reliability concerns need addressing at the architectural level
Multiple services or modules need to be designed together

When Not to Use

The change is contained within a single module — use planner + code-builder
The user just needs a quick code pattern — not architectural design
The architecture is already documented and just needs implementation

Inputs

Input	Type	Required	Description
`requirements`	string	Yes	Functional and non-functional requirements
`constraints`	string	No	Technical, organizational, or timeline constraints
`existing_architecture`	string	No	Description of existing system if extending it

Expected Outputs

Output	Description
Module decomposition	List of modules with responsibilities
Data flow	How data moves between modules and external systems
Scaling strategy	How the system handles growth
Technology decisions	Key tech choices with rationale

Exact Workflow Steps

Understand requirements and constraints thoroughly
Identify bounded contexts and module boundaries
Define interfaces and data flow between modules
Design for failure: error handling, retries, fallbacks
Plan scaling strategy (horizontal vs vertical, caching, sharding)
Document technology decisions with alternatives considered
Review with planner to create execution plan

Required Checks

Every requirement is addressed by the architecture
Module boundaries are clear and non-overlapping
Data flow is documented with direction and format
Failure modes are identified per module

Failure Modes

Failure Condition	Response
Requirements are too vague	Ask clarifying questions before designing
Architecture contradicts existing system	Document trade-offs and seek user input
Too many modules for scope	Consolidate into coarser boundaries

References

Reference	Path
Planner skill	`../planner/SKILL.md`
Code Builder skill	`../code-builder/SKILL.md`