lmiranda
2925ec4229
Domain Advisory Pattern Hardening - patch release to close gaps from v5.6.0/v5.7.0: ## Added - New `validate_workflow_integration` MCP tool validates domain plugins expose required advisory interfaces (gate command, review command, advisory agent) - New `MISSING_INTEGRATION` issue type for workflow integration validation - New `WorkflowIntegrationResult` Pydantic model for structured validation output - `integrates_with` field on viz-platform and data-platform in marketplace.json declaring projman integration metadata - 4 new test cases for workflow integration validation ## Fixed - scripts/setup.sh banner version updated from v5.1.0 to v5.7.1 ## Documentation - Updated mcp-tools-reference.md with new tool - Updated validation-rules.md with Workflow Integration Checks section - Added /design-gate, /design-review, /data-gate, /data-review to COMMANDS-CHEATSHEET - Added contract-validator to CONFIGURATION.md plugin table - Updated README.md Contract Validator tools table Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
70 lines
1.9 KiB
Markdown
70 lines
1.9 KiB
Markdown
# Skill: MCP Tools Reference
|
|
|
|
Available MCP tools for contract-validator operations.
|
|
|
|
## Tool Categories
|
|
|
|
### Parse Tools
|
|
| Tool | Description |
|
|
|------|-------------|
|
|
| `parse_plugin_interface` | Extract interface from plugin README.md |
|
|
| `parse_claude_md_agents` | Extract agents and tool sequences from CLAUDE.md |
|
|
|
|
### Validation Tools
|
|
| Tool | Description |
|
|
|------|-------------|
|
|
| `validate_compatibility` | Check two plugins for conflicts |
|
|
| `validate_agent_refs` | Check agent tool references exist |
|
|
| `validate_data_flow` | Verify data flow through agent sequence |
|
|
| `validate_workflow_integration` | Check domain plugin exposes required advisory interfaces |
|
|
|
|
### Report Tools
|
|
| Tool | Description |
|
|
|------|-------------|
|
|
| `generate_compatibility_report` | Generate full marketplace report (JSON) |
|
|
| `list_issues` | Filter issues by severity or type |
|
|
|
|
## Tool Usage Patterns
|
|
|
|
### Full Marketplace Validation
|
|
```
|
|
1. generate_compatibility_report(marketplace_path)
|
|
2. list_issues(severity="ERROR") # Get critical issues
|
|
3. list_issues(severity="WARNING") # Get warnings
|
|
```
|
|
|
|
### Single Agent Check
|
|
```
|
|
1. parse_claude_md_agents(claude_md_path)
|
|
2. validate_agent_refs(agent_name, agents_data)
|
|
3. validate_data_flow(agent_workflow)
|
|
```
|
|
|
|
### Interface Listing
|
|
```
|
|
1. For each plugin:
|
|
parse_plugin_interface(readme_path)
|
|
2. Aggregate results into summary table
|
|
```
|
|
|
|
### Dependency Graph
|
|
```
|
|
1. generate_compatibility_report(marketplace_path)
|
|
2. validate_data_flow(cross_plugin_flows)
|
|
3. Build Mermaid diagram from results
|
|
```
|
|
|
|
### Workflow Integration Check
|
|
```
|
|
1. validate_workflow_integration(plugin_path, domain_label) # Check single domain plugin
|
|
2. For each domain in domain-consultation.md detection rules:
|
|
validate_workflow_integration(domain_plugin_path, domain_label)
|
|
```
|
|
|
|
## Error Handling
|
|
|
|
If MCP tools fail:
|
|
1. Check if `/initial-setup` has been run
|
|
2. Verify session was restarted after setup
|
|
3. Check MCP server venv exists and is valid
|