bc

Buddy-Council

A multi-agent plugin for detecting contradictions, coverage gaps, and alignment issues between requirements and test cases. Works with both Claude Code and Copilot CLI.

Data is fetched live from external systems via MCP — no RAG, no embeddings, no vector storage.

Supported Sources

Source	Type	Status
TestRail	Test cases	Supported (via MCP server)
Excel (Jama export)	Requirements	Supported (temporary Jama fallback)
Jama	Requirements	Planned (auth in progress)
Jira	Requirements	Planned
Jira	Ticket creation	Supported (via MCP server)
Qase	Test cases	Planned

Available Commands

Command	Description
/bc:setup	Configure data sources and credentials
/bc:contradiction	Detect contradictions between requirements and test cases
/bc:coverage	Find untested requirements, orphan tests, and coverage gaps
/bc:validate	Validate ticket description and create Jira ticket (with dry-run support)
/bc:ask	Natural language query — routes to the right agent

Prerequisites

• Claude Code or Copilot CLI
• uv (Python package manager, for the TestRail MCP server)
• Python 3.10+
• A TestRail account with API access (for test cases)
• An Excel export from Jama (for requirements), or direct Jama API access (when available)

Installation

Claude Code

Step 1: Add the marketplace

/plugin marketplace add https://github.com/Omar-Hegazy-Integrant/buddy-council-plugin

Step 2: Install the plugin

/plugin install bc

Step 3: Reload

/reload-plugins

Copilot CLI

Step 1: Add the marketplace

copilot plugin marketplace add https://github.com/Omar-Hegazy-Integrant/buddy-council-plugin

Step 2: Install the plugin

copilot plugin install bc

Copilot CLI — fewer permission prompts

Claude Code auto-approves the plugin's read-only operations via a bundled hook. Copilot CLI has no equivalent shippable hook, so pre-approve the plugin's read-only tools at launch with --allow-tool (curated — write operations like Jira ticket creation still prompt):

copilot --allow-tool='testrail(testrail_get_projects),testrail(testrail_get_suites),testrail(testrail_get_sections),testrail(testrail_get_cases),testrail(testrail_get_cases_by_refs),testrail(testrail_get_case),shell(jq:*),shell(gh api:*)'

Append the read-only tools for any other sources you configured:

• Jira (ticket validation): jira(jira_get_projects),jira(jira_get_issue_types),jira(jira_get_issue)
• GitHub MCP (doc enrichment): github(get_file_contents)

The Excel parser (python3 … parse.py) and the TestRail connection test run once per analysis — when Copilot first prompts for them, choose "always allow" for the directory and it won't ask again. /bc:setup prints this recipe tailored to your configuration.

Local Development (either platform)

# Clone the repository
git clone https://github.com/Omar-Hegazy-Integrant/buddy-council-plugin.git

# Install the TestRail MCP server dependencies
cd buddy-council-plugin/mcp-servers/testrail-server
uv venv && uv pip install -e .

# Run with Claude Code
claude --plugin-dir /path/to/buddy-council-plugin

# Or with Copilot CLI
copilot plugin install /path/to/buddy-council-plugin

Setup

After installation, run the setup command to configure your data sources:

/bc:setup

This walks you through:

1. Requirements source — choose Excel (Jama export) or Jama (when available)
2. Test cases source — configure TestRail connection
3. Credentials — stored securely in ~/.buddy-council/secrets.json (never committed)
4. MCP server — writes .mcp.json with TestRail credentials for the MCP server

After setup, restart your CLI tool or toggle the MCP server for it to take effect.

Manual Configuration

If you prefer to configure manually instead of using /bc:setup:

1. Create .buddy-council/sources.json (no secrets in this file):

{
  "requirements": {
    "provider": "excel",
    "excel_path": "/absolute/path/to/requirements.xls"
  },
  "test_cases": {
    "provider": "testrail",
    "base_url": "https://your-instance.testrail.io",
    "project_id": 1,
    "suite_id": null
  }
}

2. Create ~/.buddy-council/secrets.json:

{
  "testrail": {
    "username": "[email protected]",
    "api_key": "your-testrail-api-key"
  }
}

chmod 600 ~/.buddy-council/secrets.json

3. Create .mcp.json in the plugin root (copy from .mcp.example.json). It holds no secrets — only the non-secret base URL and BC_SECRETS_FILE, a pointer to the secrets file; the server reads credentials from ~/.buddy-council/secrets.json: