From archspec
Reads SERVICE_MAP.yaml, generates a chat-only Mermaid diagram for a proposed architecture change, and proposes YAML edits before any code is written.
How this command is triggered — by the user, by Claude, or both
Slash command
/archspec:investigateThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /archspec:investigate Run the `architecture-investigate` skill. Read-only. Open `skills/architecture-investigate/SKILL.md` and follow the steps verbatim.
Run the architecture-investigate skill. Read-only.
Open skills/architecture-investigate/SKILL.md and follow the steps verbatim.
npx claudepluginhub krus210/archspec --plugin archspec/flow-architecture-evolutionOrchestrates architecture evolution workflows: assess triggers, manage ADRs, analyze breaking changes, plan migrations, and update architecture documentation (SAD, diagrams).
/architecturePlans system architecture by reading the current baseline, producing architecture diagrams and integration points, and using a question gate before decomposition.
/generate-visual-planGenerates a self-contained HTML implementation plan with architecture diagrams, file maps, and test plans after researching the codebase.
/investigateStarts a deep root-cause investigation on the AWS DevOps Agent, gathering local context and streaming progress until completion. Shows findings and recommendations without auto-applying.
/investigateInvestigates and debugs any Laravel API issue by checking data before code, recognizing patterns like cache, queue, or timezone bugs, and optionally consulting the knowledge base.
/investigateInvestigates a GitHub issue — validates it's real, determines root cause, and posts structured findings as a GitHub comment with workflow label updates.