context-service-guide

Analyze legacy WildFly/Maven context service repositories and generate structured summaries.

3|4|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill context-service-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-service-guide
Source: https://github.com/hmcts/agentic-plugins-marketplace/tree/main/plugins/agents/hmcts-sdlc-orchestrator/skills/context-service-guide
Command: npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill context-service-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill assists in navigating and understanding the structure, integrations, and workflow of legacy WildFly/Maven context services.

Core Features & Use Cases

  • Repo Walkthrough: Provides a structured guide to quickly understand the purpose and structure of a context service repository.
  • Integration Mapping: Identifies upstream and downstream contexts, shared components, and external systems.
  • Module Structure Analysis: Maps the CQRS module layout for domain events, commands, queries, and more.
  • Summary Generation: Outputs a structured summary of the service, including purpose, events, commands, queries, dependencies, database schema, and development workflow.

Quick Start

Use the context-service-guide skill to get an overview of the repository 'cpp-context-123'.

Frequently Asked Questions about context-service-guide

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

FAQPage Schema
How do I understand a legacy WildFly context service repository?

A structured repository walkthrough analyzes legacy WildFly context services by mapping the CQRS module layout, identifying domain events, commands, queries, and external dependencies to generate a comprehensive service summary.

How do I map CQRS module layout in a legacy Maven repository?

Mapping a CQRS module layout in a legacy Maven repository requires analyzing the project structure to identify distinct modules for domain events, commands, queries, and shared components, then summarizing their relationships and database schemas.

What is the best way to identify upstream and downstream integrations in a context service?

The best way to identify upstream and downstream integrations in a context service is through integration mapping, which detects connected external systems and shared components to clarify the service's workflow and dependencies.

Can I generate a summary of commands and queries for a CQRS-based WildFly service?

Yes, you can generate a summary of commands and queries for a CQRS-based WildFly service by analyzing the repository structure to extract domain logic, dependencies, database schema, and development workflow details.

Does this approach work for onboarding into CQRS-based systems in WildFly era architecture?

Yes, this approach works for onboarding into CQRS-based systems in WildFly era architecture by providing a structured walkthrough of legacy Maven repositories, mapping integration points, and summarizing core service functionality.