setup-architect
Setup AI Software Architect Framework
Sets up and customizes the AI Software Architect framework for a project.
Overview
This skill performs a complete framework installation:
- Verifies prerequisites (framework cloned, project root confirmed)
- Analyzes project (languages, frameworks, structure, patterns)
- Installs framework files and directory structure
- Customizes team members and principles for detected tech stack
- Performs initial system analysis
- Reports customizations and findings
Detailed procedures: references/installation-procedures.md Customization guide: references/customization-guide.md
High-Level Workflow
1. Verify Prerequisites
Check requirements before installation:
.architecture/.architecture/directory exists (cloned framework)- Currently in project root directory
If missing: Guide user to clone framework first.
2. Analyze Project
Identify project characteristics:
- Languages: JavaScript/TypeScript, Python, Ruby, Java, Go, Rust
- Frameworks: React, Vue, Django, Rails, Spring, etc.
- Infrastructure: Testing setup, CI/CD, package managers
- Structure: Directory layout, architectural patterns
Use Glob and Grep to detect technologies, Read to examine configs.
3. Install Framework
Execute installation steps (see references/installation-procedures.md):
- Copy framework files to
.architecture/ - Remove clone directory
- Create directory structure (decisions/adrs, reviews, recalibration, etc.)
- Initialize configuration from templates
- Set up agent documentation (ADR-006 progressive disclosure)
Critical: Follow safety procedures when removing .git/ directory.
4. Customize Architecture Team
Add technology-specific members to .architecture/members.yml:
- JavaScript/TypeScript: JavaScript Expert, framework specialists (React/Vue/Angular)
- Python: Python Expert, framework specialists (Django/Flask/FastAPI)
- Ruby: Ruby Expert, Rails Architect
- Java: Java Expert, Spring Boot Specialist
- Go: Go Expert, Microservices Architect
- Rust: Rust Expert, Systems Programmer
Use template from assets/member-template.yml.
Keep core members: Systems Architect, Domain Expert, Security, Performance, Maintainability, AI Engineer, Pragmatic Enforcer.
Customization details: references/customization-guide.md § Customize Team Members
5. Customize Architectural Principles
Add framework-specific principles to .architecture/principles.md:
- React: Component composition, hooks, unidirectional data flow
- Rails: Convention over configuration, DRY, RESTful design
- Django: Explicit over implicit, reusable apps, use built-ins
Principle examples: references/customization-guide.md § Customize Principles
6. Update CLAUDE.md Integration
If CLAUDE.md exists in project root, append framework usage section:
- Available commands
- Where to find documentation
- How to invoke skills
Template: references/customization-guide.md § Update CLAUDE.md
7. Cleanup
Remove framework development files:
- Framework documentation (README.md, USAGE*.md, INSTALL.md)
- Template
.git/directory (with critical safety checks)
⚠️ IMPORTANT: Follow all safeguards in references/installation-procedures.md § Cleanup.
8. Create Initial System Analysis
Generate comprehensive initial analysis document:
- Each member analyzes system from their perspective
- System overview (stack, structure, patterns)
- Strengths identified
- Concerns raised (with impact levels)
- Recommendations prioritized (Critical/Important/Nice-to-Have)
- Collaborative synthesis of findings
Save to .architecture/reviews/initial-system-analysis.md.
Template: assets/initial-analysis-template.md
9. Report to User
Provide setup summary:
AI Software Architect Framework Setup Complete
Customizations:
- Added [N] technology specialists: [list]
- Customized principles for: [frameworks]
- Configuration: Pragmatic mode [enabled/disabled]
Initial Analysis Highlights:
- Overall assessment: [assessment]
- Top strength: [strength]
- Top concern: [concern]
- Critical recommendation: [recommendation]
Location: .architecture/reviews/initial-system-analysis.md
Next Steps:
- Review initial analysis findings
- "List architecture members" to see customized team
- "Create ADR for [first decision]" to start documenting
- "What's our architecture status?" to verify setup
Error Handling
Framework not cloned:
The framework must be cloned first. Please run:
git clone https://github.com/codenamev/ai-software-architect .architecture/.architecture
Then run setup again.
Already set up:
Framework appears to be already set up.
To verify: "What's our architecture status?"
To reconfigure: Manually edit .architecture/members.yml and .architecture/principles.md
Unclear project structure:
Could not clearly identify project type. Please describe:
- Primary programming language(s)
- Framework(s) used
- Project purpose
I'll customize the framework accordingly.
Related Skills
After Setup:
list-members- View customized teamarchitecture-status- Verify setup completioncreate-adr- Document first decision
Initial Work:
- Review
initial-system-analysis.mdfindings specialist-review- Deep-dive on specific concernscreate-adr- Document existing key decisions
Workflow Example: Setup → Review initial analysis → Create ADRs → Status check → Regular reviews
Notes
- Customize based on actual project, not every possible option
- Be specific about why each customization was made
- Initial analysis should be thorough but focused on actionable findings
- Safety checks during cleanup are non-negotiable
Documentation
- Installation details: references/installation-procedures.md
- Customization guide: references/customization-guide.md
- Initial analysis template: assets/initial-analysis-template.md
- Member template: assets/member-template.yml
- Common patterns: ../_patterns.md
More from codenamev/ai-software-architect
architecture-review
Conducts a comprehensive multi-perspective architecture review using ALL architecture team members. Use when the user requests "Start architecture review", "Full architecture review", "Review architecture for version X.Y.Z", "Conduct comprehensive review", or when they want assessment from multiple perspectives. Do NOT use for single-specialist reviews (use specialist-review instead) or for status checks (use architecture-status instead).
11create-adr
Creates a NEW Architectural Decision Record (ADR) documenting a specific architectural decision. Use when the user requests "Create ADR for [topic]", "Document decision about [topic]", "Write ADR for [choice]", or when documenting technology choices, patterns, or architectural approaches. Do NOT use for reviews (use architecture-review or specialist-review), checking existing ADRs (use architecture-status), or general documentation.
5pragmatic-guard
Enables and configures Pragmatic Guard Mode (YAGNI Enforcement) to prevent over-engineering. Use when the user requests "Enable pragmatic mode", "Turn on YAGNI enforcement", "Activate simplicity guard", "Challenge complexity", or similar phrases.
4list-members
Displays the roster of architecture team members with their specialties and expertise areas. Use when the user asks "Who's on the architecture team?", "List architecture members", "Show me the architects", "What specialists are available?", "Who can I ask for reviews?", or wants to discover available experts. Do NOT use for requesting reviews (use specialist-review or architecture-review) or checking documentation status (use architecture-status).
4specialist-review
Conducts a focused review from ONE specific specialist's perspective (e.g., Security Specialist, Performance Expert). Use when the user requests "Ask [specialist role] to review [target]", "Get [specialist]'s opinion on [topic]", "Have [role] review [code/component]", or when they want deep expertise in ONE specific domain. Do NOT use for comprehensive multi-perspective reviews (use architecture-review instead) or for listing available specialists (use list-members instead).
4architecture-status
Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants an overview/summary of documentation state. Do NOT use for listing team members (use list-members), creating new documents (use create-adr), or conducting reviews (use architecture-review or specialist-review).
4