list-members

Solid

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).

AI & Automation 73 stars 11 forks Updated 4 days ago

Install

View on GitHub

Quality Score: 78/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
0
Description 5%
100

Skill Content

# List Architecture Members Displays all architecture team members and their expertise areas. ## Process ### 1. Check Setup If `.architecture/members.yml` doesn't exist: ``` The AI Software Architect framework hasn't been set up yet. To get started: "Setup ai-software-architect" ``` ### 2. Load Members Read `.architecture/members.yml` and parse all members (id, name, title, specialties, disciplines, skillsets, domains, perspective). ### 3. Display Team Roster ```markdown # Architecture Team Members Your AI Software Architect team consists of [count] specialized reviewers. Total Members: [count] --- ## Team Roster ### [Member 1 Name] - [Member 1 Title] **ID**: `[member_id]` **Specialties**: [Specialty 1], [Specialty 2], [Specialty 3] **Disciplines**: [Discipline 1], [Discipline 2] **Domains**: [Domain 1], [Domain 2], [Domain 3] **Perspective**: [Their unique perspective] **Request review**: `Ask [Member Title] to review [your target]` --- [Repeat for all members] --- ## Quick Reference **Specialist reviews**: - `Ask [Specialist Title] to review [target]` **Examples**: - "Ask Security Specialist to review authentication" - "Ask Performance Specialist to review database queries" - "Ask [Your Specialist] to review [anything]" **Full architecture review**: - `Start architecture review for version X.Y.Z` **Other commands**: - `Create ADR for [decision topic]` - `What's our architecture status?` --- ## Team by Specialty [Group members by their primary dom...

Details

Author
codenamev
Repository
codenamev/ai-software-architect
Created
1 years ago
Last Updated
4 days ago
Language
JavaScript
License
None

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

architecture-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).

73 Updated 4 days ago
codenamev
Code & Development Solid

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).

73 Updated 4 days ago
codenamev
AI & Automation Solid

design-architecture

Reviews the current codebase architecture and proposes improvements using four parallel specialist subagents: System Architect, Software Architect, Data Architect, and an Adversarial Architect that red-teams failure paths, LLM adversarial output scenarios, silent corruption risks, and invariant bypasses. Each subagent independently analyzes the codebase from their domain perspective, then their findings are consolidated into a living `architecture.md` file with a tracked to-do list and change log. Use this skill whenever the user asks to review, analyze, audit, or improve the architecture — or when they ask questions like "what should we change structurally?", "how is the system organized?", "what are our architecture problems?", "can you do an architecture review?", or "let's redesign X". Also trigger when the user mentions technical debt, structural improvements, security concerns, failure modes, vulnerabilities, or wants a second opinion on design decisions, even if they don't use the word "architecture".

58 Updated 2 days ago
SenolIsci