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).
npx skills add majiayu000/claude-skill-registry --skill architecture-status --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Architecture Status Provides overview of architecture documentation state. ## Process ### 1. Check Framework Setup If `.architecture/` doesn't exist: ``` The AI Software Architect framework is not set up yet. To get started: "Setup ai-software-architect" Once set up, you'll have: - Architectural Decision Records (ADRs) - Architecture reviews - Specialist reviews - Recalibration tracking ``` ### 2. Gather Information Collect from `.architecture/`: - **ADRs**: Count files in `decisions/adrs/`, note recent ones, check statuses - **Reviews**: Count files in `reviews/`, categorize (version/feature/specialist/initial) - **Recalibration**: Count files in `recalibration/`, check progress docs - **Comparisons**: List files in `comparisons/` - **Team**: Count members in `members.yml` - **Last Activity**: Most recent date from any document ### 3. Generate Status Report ```markdown # Architecture Framework Status **Report Date**: [Date] **Project**: [Project name if known] ## Summary **Health Status**: Excellent | Good | Needs Attention | Inactive **Key Metrics**: - ADRs: [count] - Reviews: [count] - Recalibration Plans: [count] - Team Members: [count] - Last Activity: [Date] ## Architectura
- Process
- 1. Check Framework Setup
- 2. Gather Information
- 3. Generate Status Report
- 4. Analyze Health
- 5. Provide Recommendations
- 6. Make It Actionable
- Metrics to Track
- Error Handling
- Related Skills
- Notes
What does the architecture-status skill do?
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).
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill architecture-status --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.