architecture-investigate

Investigate proposed changes to a microservice architecture using SERVICE_MAP.yaml.

12|Updated Apr 26, 2026

Search Tags:#architecture #code review #microservices #architectural analysis #change investigation

Ready to run

npx skills add https://github.com/krus210/archspec --skill architecture-investigate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-investigate
Source: https://github.com/krus210/archspec/tree/main/skills/architecture-investigate
Command: npx skills add https://github.com/krus210/archspec --skill architecture-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables you to thoroughly investigate proposed changes to a microservice architecture, ensuring that the changes are well-understood, well-documented, and free of potential pitfalls.

Core Features & Use Cases

Comprehensive Analysis: Inspect the effects of architectural changes across services and their interactions.
Automated Reporting: Generate detailed reports outlining the implications of proposed changes.
Read-only Interaction: Provides a read-only analysis, ensuring that the system remains unaltered during investigation.
Use Case: Before implementing a new feature, use this Skill to analyze how it will impact existing services and ensure that the architecture remains robust.

Quick Start

Run /archspec:investigate to begin an investigation of your proposed architectural change.

Frequently Asked Questions about architecture-investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I analyze the impact of proposed changes on a microservice architecture?▼

This Skill investigates microservice architecture changes by reading SERVICE_MAP.yaml, asking clarifying questions, and generating a self-reviewed plan artifact that details cross-service interaction implications.

What is the best way to document architectural analysis before implementing a new feature?▼

The best way to document architectural analysis is by generating an automated report that outlines the implications of proposed changes, ensuring your microservice architecture remains robust and well-understood before implementation.

Do I need a SERVICE_MAP.yaml file to investigate microservice changes?▼

Yes, you need a SERVICE_MAP.yaml file because the architectural investigation reads directly from it to understand your existing microservice architecture and accurately assess the impact of proposed modifications.

Can I use this architectural analysis to modify my microservices directly?▼

No, you cannot use this architectural analysis to modify microservices directly because it operates in read-only mode, ensuring your system remains completely unaltered during the investigation process.

How does an architectural change investigation handle potential pitfalls across services?▼

An architectural change investigation handles potential pitfalls by performing a comprehensive analysis of effects across services and their interactions, followed by a self-review of the generated plan before finalizing.