service-boundary-analysislisted

# Skill: service-boundary-analysis ## Activation Contract Use this skill when asked to inspect a backend service, microservice, worker, or API repository to identify what enters the service and what the service sends, writes, publishes, schedules, or otherwise emits. Do **not** use this skill for runtime tracing, code modification, full architecture design, security review, database schema design, or claiming complete certainty for dynamic framework behavior. ## Responsibility This skill teaches read-only, multilingual, heuristic service-boundary inspection. It defines boundary categories, discovery heuristics, evidence requirements, confidence scoring, and the required report shape. It does not decide whether to run a separate agent, coordinate multi-phase work, execute the analyzed application, install dependencies, edit source code, or replace human review. ## Required Context - Target repository, directory, file list, or code excerpts to inspect. - User's requested scope, such as one service, module, bounded context, or selected paths. - Any known language/framework context supplied by the user or visible from files. - Any exclusions, such as generated files, vendored code, fixtures, or migrations. ## Context Budget - Keep the inspection report focused on boundary evidence, confidence, and limitations. - Prefer compact excerpts over large pasted source blocks. - Group repeated equivalent findings when they share the same mechanism and destination. ## Hard Rules