create-architecture

Facilitates collaborative step-by-step creation of software architecture decision documents.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/chrissstellee/Movix --skill create-architecture-chrissstellee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-architecture
Source: https://github.com/chrissstellee/Movix/tree/main/.agents/skills/create-architecture
Command: npx skills add https://github.com/chrissstellee/Movix --skill create-architecture-chrissstellee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents implementing a project often make inconsistent architectural choices, causing conflicting code. This Skill guides a structured, collaborative workflow that produces a complete architecture decision document so all agents implement consistently. ## Core Features & Use Cases - Guided Multi-Step Workflow: Walks through initialization, project context analysis, starter template evaluation, core decisions, implementation patterns, project structure, and validation across sequential step files. - Collaborative Decision Making: Acts as an architectural facilitator with A/P/C menus (Advanced Elicitation, Party Mode, Continue) so the user approves every section before it is appended to the document. - Customizable Activation: Supports team and user-level TOML overrides for activation steps and persistent facts, plus config-driven language and output locations. - Use Case: After writing a PRD for a new web app, run this workflow to produce an architecture.md covering technology stack, naming conventions, API patterns, and directory structure that every AI coding agent must follow. ## Quick Start Say "let's create architecture" to start the guided architecture decision workflow from your PRD.

Frequently Asked Questions about create-architecture

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

FAQPage Schema
How do I create a software architecture document with an AI agent?▼

Invoke the workflow by saying "let's create architecture". The skill loads your PRD and project documents, then walks you through context analysis, starter template selection, core decisions, patterns, structure, and validation, appending each approved section to an architecture.md file.

What inputs does the architecture workflow require?▼

A PRD is mandatory; the workflow will not proceed without one. It also discovers optional inputs like UX designs, research documents, project documentation, and project-context.md files, and asks you to confirm what was found before loading them.

Can I resume an interrupted architecture workflow?▼

Yes. The initialization step detects an existing architecture document with stepsCompleted frontmatter and hands off to a continuation handler. You can resume where you left off, jump to a specific step, review remaining steps, or start over.

How do I customize the architecture workflow for my team?▼

Place TOML override files in the project's .stellar-build/custom directory named after the skill. Team and user overrides merge with the base customize.toml, letting you add activation steps, persistent facts, and post-completion behavior.

Does the architecture skill decide technologies automatically?▼

No. It acts as a facilitator, not a generator. It presents options with trade-offs, verifies current technology versions via web search, and only records decisions after you explicitly approve them through the menu prompts.