uvs-architect

Decompose approved software specs into act-based architecture plans with tasks and dependencies.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/utsavanand/uv-suite --skill uvs-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uvs-architect
Source: https://github.com/utsavanand/uv-suite/tree/main/skills/uvs-architect
Command: npx skills add https://github.com/utsavanand/uv-suite --skill uvs-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design system architecture and decompose work into Acts with tasks, dependencies, and cycle budgets. Use after a spec is approved, before coding begins.

Core Features & Use Cases

  • Decompose a spec into Acts, tasks, dependencies, and cycle budgets to guide implementation.
  • Coordinate with domain specialists (e.g., distributed-systems, full-stack, ml-systems) to incorporate guardrails and constraints.
  • Produce session-scoped architecture artifacts and traceable design decisions for handoff to engineering.

Quick Start

Provide a curated spec file to invoke the architect and decompose work into Acts and tasks.

Frequently Asked Questions about uvs-architect

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

FAQPage Schema
How do I decompose a software spec into actionable architecture tasks?

Decompose a software spec into actionable architecture tasks by providing a curated spec file to invoke the architect, which structures the work into Acts with dependencies and cycle budgets.

What is an act-based architecture plan for software design?

An act-based architecture plan is a structured breakdown of an approved software spec into Acts, coordinating domain specialists to produce traceable design decisions and session-scoped artifacts for engineering handoff.

When do I need to create an architecture plan from an approved spec?

You need to create an architecture plan from an approved spec after the specification is finalized and before coding begins, ensuring the design decomposes work into manageable Acts with defined risk-management constraints.

Can I coordinate with domain specialists while designing system architecture?

You can coordinate with domain specialists, such as those in distributed-systems or full-stack development, during constraint reconciliation to incorporate specific guardrails into your architecture design.

Does this architecture decomposition approach support risk management?

This architecture decomposition approach supports risk management by structuring the spec into Acts with defined dependencies and cycle budgets, coordinating domain specialist constraints during the design phase.

What is the best way to turn a spec into a structured architecture plan?

The best way to turn a spec into a structured architecture plan is to input a curated spec file, allowing the system to output architecture artifacts and traceable design decisions under the designated session path.