Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
fcda26e
feat: Initialize AI Software Architect framework and baseline reviews
jhutar Mar 15, 2026
5ca1624
docs: Plan for reorganizing repo
jhutar Mar 15, 2026
d1a73d9
docs: Review of reorganizing repo ADR
jhutar Mar 15, 2026
8ad3e36
refactor: Prepare repository for split directories
jhutar Mar 15, 2026
02d9bcb
refactor: Migrate code to split directories
jhutar Mar 15, 2026
7cefa58
build: Implement PEP 420 meta-packaging for split directories
jhutar Mar 15, 2026
db1747f
ci: Validate PEP 420 namespace structure in GitHub actions
jhutar Mar 15, 2026
636bf43
docs: Update README to reflect split directory workspace layout
jhutar Mar 16, 2026
0a488de
docs: Revert extras core dependency and update README installation notes
jhutar Mar 16, 2026
c56a1ea
docs: Discourage manual extras installation
jhutar Mar 16, 2026
9ad6c80
feat: Add skills for planning for software assistant from https://git…
jhutar Mar 16, 2026
463de92
fix: Resolve test failures by adding missing dependency and fixing ar…
jhutar Mar 16, 2026
866c69d
feat: Implement test coverage measurements with pytest-cov
jhutar Mar 16, 2026
3151da8
chore: Clean up extraneous AI Software Architect framework files
jhutar Mar 16, 2026
9a0cd0c
docs: Rename ADR-012 to ADR-001 and reset framework deferrals
jhutar Mar 16, 2026
bfd9670
test: Fix temporary file leaks and update documentation for coverage
jhutar Mar 16, 2026
9704597
style: Reformat with black and ruff
jhutar Mar 16, 2026
198b5f6
style: Fix flake8 E226 whitespace issues in extras/
jhutar Mar 16, 2026
c7b45c3
fix: Resolve pylint errors and namespace package import issues
jhutar Mar 16, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
918 changes: 918 additions & 0 deletions .agents/skills/_patterns.md

Large diffs are not rendered by default.

132 changes: 132 additions & 0 deletions .agents/skills/architecture-review/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,132 @@
---
name: architecture-review
description: 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).
allowed-tools: Read,Write,Glob,Grep,Bash(git:*)
---

# Architecture Review

Conducts comprehensive multi-perspective architecture reviews with all team members.

## Process Overview

1. **Determine Scope** - Identify what to review (version, feature, or component)
2. **Load Team** - Read members from `.architecture/members.yml` and check pragmatic mode
3. **Analyze System** - Examine architecture using Read, Glob, Grep, and git tools
4. **Individual Reviews** - Each member reviews from their specialized perspective
5. **Collaborative Discussion** - Synthesize findings and establish priorities
6. **Create Document** - Generate comprehensive review using template
7. **Report Results** - Summarize findings and next steps for user

**Detailed guidance**: [references/review-process.md](references/review-process.md)

## Workflow Steps

### 1. Determine Scope

Identify review target and create filename:
- **Version**: "version X.Y.Z" → `X-Y-Z.md`
- **Feature**: "feature name" → `feature-kebab-case.md`
- **Component**: "component name" → `component-kebab-case.md`

Apply input validation (see `_patterns.md` § Filename Sanitization).

### 2. Load Configuration and Team

```bash
cat .architecture/config.yml # Check pragmatic_mode.enabled
cat .architecture/members.yml # Load all members
```

Include Pragmatic Enforcer if pragmatic mode enabled for reviews.

### 3. Analyze the Target

Use available tools to examine the system:
- `Read` - Code, configs, documentation
- `Glob` - Find files by pattern
- `Grep` - Search for specific patterns
- `Bash(git:*)` - Git history and status

Focus based on review type:
- **Version**: Overall architecture, components, patterns, technical debt
- **Feature**: Implementation, integration, security, performance
- **Component**: Structure, dependencies, boundaries, interfaces

### 4. Conduct Individual Member Reviews

For each member in `members.yml`, write a review including:
- Perspective statement
- Key observations (3-5)
- Strengths (3-5)
- Concerns with impact and recommendations (3-7)
- Prioritized recommendations with effort estimates (3-7)

**Format details**: [references/review-process.md § Individual Member Review Format](references/review-process.md#individual-member-review-format)

**Pragmatic integration**: If enabled, add pragmatic analysis after each member. See [references/pragmatic-integration.md](references/pragmatic-integration.md)

### 5. Facilitate Collaborative Discussion

Synthesize findings:
- Identify common concerns
- Discuss disagreements
- Establish consensus
- Prioritize: Critical (0-2 weeks) | Important (2-8 weeks) | Nice-to-Have (2-6 months)

**Discussion format**: [references/review-process.md § Collaborative Discussion](references/review-process.md#collaborative-discussion-process)

### 6. Create Review Document

Load template and fill in all sections:
```bash
cat .claude/skills/architecture-review/assets/review-template.md
```

Include:
- Executive summary and overall assessment
- Individual member reviews
- Collaborative discussion
- Consolidated findings (strengths, improvements, debt, risks)
- Recommendations (immediate, short-term, long-term)
- Success metrics and follow-up plan

Save to `.architecture/reviews/[filename].md`

**Template**: [assets/review-template.md](assets/review-template.md)

### 7. Report to User

```
Architecture Review Complete: [Target]

Location: .architecture/reviews/[filename].md
Overall Assessment: [Strong | Adequate | Needs Improvement]

Top 3 Priorities:
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

Immediate Actions:
- [Action 1]
- [Action 2]

Next Steps:
- Review with team
- "Start architecture recalibration for [target]"
- Create ADRs for key decisions
```

## Related Skills

**Before**: `architecture-status`, `list-members`
**During**: `specialist-review`, `create-adr`
**After**: `architecture-recalibration`, `create-adr`

## Documentation

- **Process guide**: [references/review-process.md](references/review-process.md)
- **Pragmatic mode**: [references/pragmatic-integration.md](references/pragmatic-integration.md)
- **Template**: [assets/review-template.md](assets/review-template.md)
- **Patterns**: [../_patterns.md](../_patterns.md)
Loading
Loading