architect

Design and compare software system implementation plans with trade-offs and recommendations.

Updated May 12, 2026

Search Tags:#documentation #system design #implementation plan #decision-making #risk analysis

Ready to run

npx skills add https://github.com/HillBombCreations/vivreal-skills --skill architect-hillbombcreations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/HillBombCreations/vivreal-skills/tree/main/vivreal-workflow/skills/architect
Command: npx skills add https://github.com/HillBombCreations/vivreal-skills --skill architect-hillbombcreations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps create detailed implementation plans with multiple options and trade-offs for system design, enabling informed decision-making during the architecture phase.

Core Features & Use Cases

Generate Design Options: Produces plans with at least 2-3 alternatives for system design, considering factors like complexity, performance, cost, and migration effort.
Risk Analysis: Assesses risks with named mitigations and suggests the most appropriate path forward.
Documentation: Generates documentation in the form of plan.md or design.md for future reference.

Quick Start

Dispatch the architect to generate a design plan for your new system feature or bug fix.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I create an implementation plan with multiple design options?▼

To create an implementation plan, you need to generate multiple design options by evaluating technical and operational trade-offs. This process produces structured documentation comparing alternatives based on complexity, performance, cost, and migration effort.

What is the best way to analyze system design risks and trade-offs?▼

Analyzing system design risks involves assessing potential operational and technical trade-offs across multiple implementation plans. This approach identifies named mitigations and suggests the most appropriate path forward for your project documentation.

How do I document system design decisions for my project?▼

Documenting system design decisions requires generating structured files like plan.md or design.md. These documents outline design alternatives, risk assessments, and recommendations, making them suitable for future reference and team collaboration.

Can I compare system architecture alternatives before implementation?▼

Yes, comparing system architecture alternatives involves evaluating at least two or three design options. This comparison assesses factors like complexity, performance, and cost to deliver structured documentation outlining the recommended path forward.

When do I need to generate design documentation for a software feature?▼

You need to generate design documentation during the architecture phase of a software feature or bug fix. It enables informed decision-making by providing detailed implementation plans with trade-offs and risk analysis for system design.