personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 9] feat: Create domain-consultation.md skill (projman) #356

New Issue
Closed
opened 2026-02-01 22:49:06 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-02-01 22:49:06 +00:00
Owner
Copy Link

Description

Create the core domain consultation skill for projman that enables detection and consultation of domain-specific plugins during planning and execution phases.

Implementation

Wiki: Change V5.6.0 (Sprint 9 Implementation)

File: plugins/projman/skills/domain-consultation.md

Acceptance Criteria

  • Create skill file with proper frontmatter (name, description)
  • Purpose section explaining cross-plugin consultation
  • When to Use section (planning + execution phases)
  • Domain Detection Rules section with patterns for:
    • viz-platform: file patterns, labels, keywords
    • data-platform: file patterns, labels, keywords (placeholder)
  • Planning Protocol section (detect domains, present considerations)
  • Execution Gate Protocol section (run domain gates before completion)
  • Review Protocol section (include domain compliance in summary)
  • Extensibility section (how to add new domains)

Technical Notes

This is the reusable backbone for all future domain integrations. The skill should be designed for extensibility - new domains can be added by:

  1. Adding detection rules to this skill
  2. Creating domain-specific gate commands in the target plugin

Risk: Medium - core architectural piece that planner and orchestrator depend on

## Description Create the core domain consultation skill for projman that enables detection and consultation of domain-specific plugins during planning and execution phases. ## Implementation **Wiki:** [Change V5.6.0 (Sprint 9 Implementation)](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/Change-V5.6.0%3A-Domain-Advisory-Pattern-%28Sprint-9-Implementation%29) **File:** `plugins/projman/skills/domain-consultation.md` ## Acceptance Criteria - [ ] Create skill file with proper frontmatter (name, description) - [ ] Purpose section explaining cross-plugin consultation - [ ] When to Use section (planning + execution phases) - [ ] Domain Detection Rules section with patterns for: - viz-platform: file patterns, labels, keywords - data-platform: file patterns, labels, keywords (placeholder) - [ ] Planning Protocol section (detect domains, present considerations) - [ ] Execution Gate Protocol section (run domain gates before completion) - [ ] Review Protocol section (include domain compliance in summary) - [ ] Extensibility section (how to add new domains) ## Technical Notes This is the **reusable backbone** for all future domain integrations. The skill should be designed for extensibility - new domains can be added by: 1. Adding detection rules to this skill 2. Creating domain-specific gate commands in the target plugin **Risk:** Medium - core architectural piece that planner and orchestrator depend on
lmiranda added this to the Sprint 9 - Domain Advisory Pattern (viz-platform) milestone 2026-02-01 22:50:08 +00:00
lmiranda commented 2026-02-01 23:07:16 +00:00
Author
Owner
Copy Link

Implementation Complete

Created plugins/projman/skills/domain-consultation.md with all required sections:

Content Summary:

  • Frontmatter with name and description
  • Purpose section explaining cross-plugin consultation pattern
  • When to Use table (Planner, Orchestrator, Code Reviewer)
  • Domain Detection Rules table with label triggers, file patterns, and keyword triggers for both Domain/Viz and Domain/Data
  • Planning Protocol with steps and issue template additions
  • Execution Gate Protocol with PASS/FAIL handling
  • Review Protocol for domain compliance reporting
  • Domain Registry (current and planned)
  • Extensibility section documenting how to add new domains

PR: #364

Branch: feat/357-design-system-audit-skill

Commit: 6eeb4a4 - feat(projman): add domain-consultation skill for cross-plugin integration

## Implementation Complete Created `plugins/projman/skills/domain-consultation.md` with all required sections: **Content Summary:** - Frontmatter with name and description - Purpose section explaining cross-plugin consultation pattern - When to Use table (Planner, Orchestrator, Code Reviewer) - Domain Detection Rules table with label triggers, file patterns, and keyword triggers for both Domain/Viz and Domain/Data - Planning Protocol with steps and issue template additions - Execution Gate Protocol with PASS/FAIL handling - Review Protocol for domain compliance reporting - Domain Registry (current and planned) - Extensibility section documenting how to add new domains **PR:** #364 **Branch:** `feat/357-design-system-audit-skill` **Commit:** `6eeb4a4` - feat(projman): add domain-consultation skill for cross-plugin integration
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Component/Backend Complexity/Medium Effort/S Priority/High Type/Feature
Milestone
No items
No Milestone Sprint 9 - Domain Advisory Pattern (viz-platform)
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#356
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?