Page:
Change V5.6.0: Domain Advisory Pattern Proposal
Pages
Change V5.4.0: Multi-Model Agent Support Proposal
Change V5.4.0: Multi-Model Support (Sprint 7 Implementation)
Change V04.1.0: Proposal (Implementation 1)
Change V04.1.0: Proposal
Change-V5.2.0:-Plugin-Enhancements-(Sprint-4-Commands)
Change-V5.2.0:-Plugin-Enhancements-(Sprint-5-Documentation)
Change-V5.2.0:-Plugin-Enhancements-Proposal.-
Change-V5.5.0:-Hook-Efficiency-Quick-Wins-(Sprint-8-Implementation)
Change-V5.6.0:-Domain-Advisory-Pattern-(Sprint-9-Implementation).-
Change V5.6.0: Domain Advisory Pattern Proposal
Change-V5.7.0:-Data-Platform-Domain-Advisory-(Sprint-10-Implementation)
RFC-Hook-Efficiency-Improvements
RFC-Perf-Sentinel-Plugin
Sprint-1-viz-platform-Implementation-Plan
branding/header-templates
branding/plugin-registry
branding/progress-templates
branding/visual-spec
lessons/patterns/agent-model-field-not-supported-by-claude-code
lessons/patterns/command-frontmatter-missing-name-field-causes-silent-load-failure
lessons/patterns/hook-message-wording-affects-claude-continuation-behavior
lessons/patterns/mcp-venv-symlinks-lost-on-marketplace-update---5-hour-debug-loop
lessons/patterns/mcp_servers-field-in-pluginjson---another-failed-debug-theory
lessons/patterns/plugin-hooks-must-be-in-separate-file-not-inline
lessons/patterns/plugin-load-errors---missing-name-field-in-command-frontmatter
lessons/patterns/plugin-load-failure---check-command-frontmatter-first
lessons/patterns/plugin-manifest-validation---hooks-and-agents-format-requirements
lessons/patterns/plugin-version-mismatch-causes-silent-load-failure
lessons/patterns/reset-pandas-index-after-filtering-to-prevent-column-pollution
lessons/patterns/session-2026-02-02---mcp-server-venv-package-installation-failures
lessons/patterns/setup-wizard-url-format-mismatch
lessons/patterns/sprint-4---new-commands-not-discoverable-until-session-restart
lessons/patterns/startup-hooks-must-check-venv-cache-path-first
lessons/patterns/sync-entire-plugin-directory-not-individual-files
lessons/patterns/use-fixes-n-keyword-for-automatic-issue-closing-in-prs
lessons/sprints/cache-clearing-breaks-mcp-tools-mid-session
lessons/sprints/sprint-1---viz-platform-plugin-implementation
lessons/sprints/sprint-10---domain-advisory-pattern-replication-success
lessons/sprints/sprint-2---contract-validator-plugin-implementation
lessons/sprints/sprint-3---agent-runaway-detection-and-timeout-handling
lessons/sprints/sprint-3---background-agent-permissions-must-be-pre-granted
lessons/sprints/sprint-3---mcp-server-branch-detection-bug-runs-from-installed-dir
lessons/sprints/sprint-4---plugin-commands-implementation
lessons/sprints/sprint-6---visual-branding-and-documentation-maintenance
lessons/sprints/sprint-8---parallel-hook-optimization-success
lessons/sprints/v400-release---wiki-workflow-and-versioning-patterns
lessons/sprints/versioning-workflow---use-unreleased-and-release-script
lessons-learned/sprints/hook-efficiency-rfc
unnamed
Clone
1
Change V5.6.0: Domain Advisory Pattern Proposal
Leo Miranda edited this page 2026-02-01 22:48:12 +00:00
Type: Change Proposal Version: V5.6.0 Plugin: projman, viz-platform Status: In Progress Date: 2026-02-01
Domain Advisory Pattern - viz-platform Integration
Summary
Implement a domain advisory pattern that enables projman (sprint management) to consult domain-specific plugins during planning and execution phases. Sprint 1 delivers the full pattern for viz-platform, including the reusable backbone skill.
Motivation
Currently, projman operates independently without domain-specific knowledge. When planning or executing work that touches visualization code, there's no systematic way to:
- Detect that work involves a specific domain (viz-platform, data-platform, etc.)
- Consult domain experts during planning for design considerations
- Run domain-specific quality gates before marking work complete
Design
Core Skill: domain-consultation.md
A projman skill that:
- Detects domain involvement via file patterns, labels, and keywords
- Consults domain plugins during planning (design considerations, risks)
- Gates execution via domain-specific pass/fail checks
viz-platform Integration
| Component | Purpose |
|---|---|
design-reviewer.md (agent) |
Audit agent using viz-platform MCP tools |
design-review.md (command) |
Standalone user command for detailed audits |
design-gate.md (command) |
Binary pass/fail for sprint gates |
design-system-audit.md (skill) |
Audit rules and violation patterns |
Extensibility
The pattern is designed for future domains:
- data-platform: data quality gates, schema validation
- cmdb-assistant: infrastructure compliance checks
Files Changed
Created (5)
plugins/projman/skills/domain-consultation.mdplugins/viz-platform/agents/design-reviewer.mdplugins/viz-platform/commands/design-review.mdplugins/viz-platform/commands/design-gate.mdplugins/viz-platform/skills/design-system-audit.md
Modified (7)
plugins/projman/agents/planner.mdplugins/projman/agents/orchestrator.mdplugins/projman/skills/label-taxonomy/labels-reference.mdplugins/viz-platform/.claude-plugin/plugin.json.claude-plugin/marketplace.jsonCHANGELOG.mdREADME.md
Implementations
- Implementation 1 (Sprint 9) - In Progress