Merge pull request 'development' (#289) from development into main

Reviewed-on: #289

.claude-plugin/marketplace.json

@@ -6,12 +6,12 @@
   },
   "metadata": {
     "description": "Project management plugins with Gitea and NetBox integrations",
-    "version": "5.1.0"
+    "version": "5.3.0"
   },
   "plugins": [
     {
       "name": "projman",
-      "version": "3.2.0",
+      "version": "3.3.0",
       "description": "Sprint planning and project management with Gitea integration",
       "source": "./plugins/projman",
       "author": {
@@ -27,7 +27,7 @@
     },
     {
       "name": "doc-guardian",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "description": "Automatic documentation drift detection and synchronization",
       "source": "./plugins/doc-guardian",
       "author": {
@@ -75,7 +75,7 @@
     },
     {
       "name": "cmdb-assistant",
-      "version": "1.1.0",
+      "version": "1.2.0",
       "description": "NetBox CMDB integration with data quality validation and machine registration",
       "source": "./plugins/cmdb-assistant",
       "author": {
@@ -91,7 +91,7 @@
     },
     {
       "name": "claude-config-maintainer",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "description": "CLAUDE.md optimization and maintenance for Claude Code projects",
       "source": "./plugins/claude-config-maintainer",
       "author": {
@@ -106,7 +106,7 @@
     },
     {
       "name": "clarity-assist",
-      "version": "1.0.0",
+      "version": "1.2.0",
       "description": "Prompt optimization and requirement clarification with ND-friendly accommodations",
       "source": "./plugins/clarity-assist",
       "author": {
@@ -121,7 +121,7 @@
     },
     {
       "name": "git-flow",
-      "version": "1.0.0",
+      "version": "1.2.0",
       "description": "Git workflow automation with intelligent commit messages and branch management",
       "source": "./plugins/git-flow",
       "author": {
@@ -136,7 +136,7 @@
     },
     {
       "name": "pr-review",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "description": "Multi-agent pull request review with confidence scoring and actionable feedback",
       "source": "./plugins/pr-review",
       "author": {
@@ -152,7 +152,7 @@
     },
     {
       "name": "data-platform",
-      "version": "1.0.0",
+      "version": "1.2.0",
       "description": "Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration",
       "source": "./plugins/data-platform",
       "author": {
@@ -168,7 +168,7 @@
     },
     {
       "name": "viz-platform",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "description": "Visualization tools with Dash Mantine Components validation, Plotly charts, and theming",
       "source": "./plugins/viz-platform",
       "author": {
@@ -184,7 +184,7 @@
     },
     {
       "name": "contract-validator",
-      "version": "1.0.0",
+      "version": "1.2.0",
       "description": "Cross-plugin compatibility validation and Claude.md agent verification",
       "source": "./plugins/contract-validator",
       "author": {

CHANGELOG.md

@@ -4,10 +4,76 @@ All notable changes to the Leo Claude Marketplace will be documented in this fil
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
-## [Unreleased]
+## [5.3.0] - 2026-01-28
 
 ### Added
 
+#### Sprint 6: Visual Branding Overhaul
+Consistent visual headers and progress tracking across all plugins.
+
+**Visual Output Headers (109 files):**
+- **Projman**: Double-line headers (╔═╗) with phase indicators (🎯 PLANNING, ⚡ EXECUTION, 🏁 CLOSING)
+- **Other Plugins**: Single-line headers (┌─┐) with plugin icons
+- **All 23 agents** updated with Visual Output Requirements section
+- **All 86 commands** updated with Visual Output section and header templates
+
+**Plugin Icon Registry:**
+| Plugin | Icon |
+|--------|------|
+| projman | 📋 |
+| code-sentinel | 🔒 |
+| doc-guardian | 📝 |
+| pr-review | 🔍 |
+| clarity-assist | 💬 |
+| git-flow | 🔀 |
+| cmdb-assistant | 🖥️ |
+| data-platform | 📊 |
+| viz-platform | 🎨 |
+| contract-validator | ✅ |
+| claude-config-maintainer | ⚙️ |
+
+**Wiki Branding Specification (4 pages):**
+- [branding/visual-spec](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/branding%2Fvisual-spec) - Central specification
+- [branding/plugin-registry](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/branding%2Fplugin-registry) - Icons and styles
+- [branding/header-templates](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/branding%2Fheader-templates) - Copy-paste templates
+- [branding/progress-templates](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/branding%2Fprogress-templates) - Sprint progress blocks
+
+### Fixed
+- **Docs:** Version sync - CLAUDE.md, marketplace.json, README.md now consistent
+- **Docs:** Added 18 missing commands from Sprint 4 & 5 to README.md and COMMANDS-CHEATSHEET.md
+- **MCP:** Registered `/sprint-diagram` as invokable skill
+
+**Sprint Completed:**
+- Milestone: Sprint 6 - Visual Branding Overhaul (closed 2026-01-28)
+- Issues: #272, #273, #274, #275, #276, #277, #278
+- PRs: #284, #285
+- Wiki: [Sprint 6 Lessons](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/lessons/sprints/sprint-6---visual-branding-and-documentation-maintenance)
+
+---
+
+## [5.2.0] - 2026-01-28
+
+### Added
+
+#### Sprint 5: Documentation (V5.2.0 Plugin Enhancements)
+Documentation and guides for the plugin enhancements initiative.
+
+**git-flow v1.2.0:**
+- **Branching Strategy Guide** (`docs/BRANCHING-STRATEGY.md`) - Complete documentation of `development -> staging -> main` promotion flow with Mermaid diagrams
+
+**clarity-assist v1.2.0:**
+- **ND Support Guide** (`docs/ND-SUPPORT.md`) - Documentation of neurodivergent accommodations, features, and usage examples
+
+**Gitea MCP Server:**
+- **`update_issue` milestone parameter** - Can now assign/change milestones programmatically
+
+**Sprint Completed:**
+- Milestone: Sprint 5 - Documentation (closed 2026-01-28)
+- Issues: #266, #267, #268, #269
+- Wiki: [Change V5.2.0: Plugin Enhancements (Sprint 5 Documentation)](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/Change-V5.2.0%3A-Plugin-Enhancements-%28Sprint-5-Documentation%29)
+
+---
+
 #### Sprint 4: Commands (V5.2.0 Plugin Enhancements)
 Implementation of 18 new user-facing commands across 8 plugins.
 
@@ -55,6 +121,7 @@ Implementation of 18 new user-facing commands across 8 plugins.
 
 ### Fixed
 - **MCP:** Project directory detection - all run.sh scripts now capture `CLAUDE_PROJECT_DIR` from PWD before changing directories
+- **Docs:** Added Gitea auto-close behavior and MCP session restart notes to DEBUGGING-CHECKLIST.md
 
 ---
 

CLAUDE.md

@@ -50,24 +50,24 @@ See `docs/DEBUGGING-CHECKLIST.md` for details on cache timing.
 ## Project Overview
 
 **Repository:** leo-claude-mktplace
-**Version:** 5.1.0
+**Version:** 5.3.0
 **Status:** Production Ready
 
 A plugin marketplace for Claude Code containing:
 
 | Plugin | Description | Version |
 |--------|-------------|---------|
-| `projman` | Sprint planning and project management with Gitea integration | 3.2.0 |
-| `git-flow` | Git workflow automation with smart commits and branch management | 1.0.0 |
-| `pr-review` | Multi-agent PR review with confidence scoring | 1.0.0 |
-| `clarity-assist` | Prompt optimization with ND-friendly accommodations | 1.0.0 |
-| `doc-guardian` | Automatic documentation drift detection and synchronization | 1.0.0 |
+| `projman` | Sprint planning and project management with Gitea integration | 3.3.0 |
+| `git-flow` | Git workflow automation with smart commits and branch management | 1.2.0 |
+| `pr-review` | Multi-agent PR review with confidence scoring | 1.1.0 |
+| `clarity-assist` | Prompt optimization with ND-friendly accommodations | 1.2.0 |
+| `doc-guardian` | Automatic documentation drift detection and synchronization | 1.1.0 |
 | `code-sentinel` | Security scanning and code refactoring tools | 1.0.0 |
-| `claude-config-maintainer` | CLAUDE.md optimization and maintenance | 1.0.0 |
-| `cmdb-assistant` | NetBox CMDB integration for infrastructure management | 1.0.0 |
-| `data-platform` | pandas, PostgreSQL, and dbt integration for data engineering | 1.0.0 |
-| `viz-platform` | DMC validation, Plotly charts, and theming for dashboards | 1.0.0 |
-| `contract-validator` | Cross-plugin compatibility validation and agent verification | 1.0.0 |
+| `claude-config-maintainer` | CLAUDE.md optimization and maintenance | 1.1.0 |
+| `cmdb-assistant` | NetBox CMDB integration for infrastructure management | 1.2.0 |
+| `data-platform` | pandas, PostgreSQL, and dbt integration for data engineering | 1.2.0 |
+| `viz-platform` | DMC validation, Plotly charts, and theming for dashboards | 1.1.0 |
+| `contract-validator` | Cross-plugin compatibility validation and agent verification | 1.2.0 |
 | `project-hygiene` | Post-task cleanup automation via hooks | 0.1.0 |
 
 ## Quick Start
@@ -85,16 +85,17 @@ A plugin marketplace for Claude Code containing:
 | Category | Commands |
 |----------|----------|
 | **Setup** | `/initial-setup`, `/project-init`, `/project-sync` |
-| **Sprint** | `/sprint-plan`, `/sprint-start`, `/sprint-status`, `/sprint-close` |
+| **Sprint** | `/sprint-plan`, `/sprint-start`, `/sprint-status`, `/sprint-close`, `/sprint-diagram` |
 | **Quality** | `/review`, `/test-check`, `/test-gen` |
 | **Versioning** | `/suggest-version` |
-| **PR Review** | `/pr-review:initial-setup`, `/pr-review:project-init` |
-| **Docs** | `/doc-audit`, `/doc-sync` |
+| **PR Review** | `/pr-review`, `/pr-summary`, `/pr-findings`, `/pr-diff` |
+| **Docs** | `/doc-audit`, `/doc-sync`, `/changelog-gen`, `/doc-coverage`, `/stale-docs` |
 | **Security** | `/security-scan`, `/refactor`, `/refactor-dry` |
-| **Config** | `/config-analyze`, `/config-optimize` |
-| **Data** | `/ingest`, `/profile`, `/schema`, `/explain`, `/lineage`, `/run` |
-| **Visualization** | `/component`, `/chart`, `/dashboard`, `/theme`, `/theme-new`, `/theme-css` |
-| **Validation** | `/validate-contracts`, `/check-agent`, `/list-interfaces` |
+| **Config** | `/config-analyze`, `/config-optimize`, `/config-diff`, `/config-lint` |
+| **Data** | `/ingest`, `/profile`, `/schema`, `/explain`, `/lineage`, `/lineage-viz`, `/run`, `/dbt-test`, `/data-quality` |
+| **Visualization** | `/component`, `/chart`, `/chart-export`, `/dashboard`, `/theme`, `/theme-new`, `/theme-css`, `/accessibility-check`, `/breakpoints` |
+| **Validation** | `/validate-contracts`, `/check-agent`, `/list-interfaces`, `/dependency-graph` |
+| **CMDB** | `/cmdb-search`, `/cmdb-device`, `/cmdb-ip`, `/cmdb-site`, `/cmdb-audit`, `/cmdb-register`, `/cmdb-sync`, `/cmdb-topology`, `/change-audit`, `/ip-conflicts` |
 | **Debug** | `/debug-report`, `/debug-review` |
 
 ## Repository Structure
@@ -376,4 +377,4 @@ The script will:
 
 ---
 
-**Last Updated:** 2026-01-24
+**Last Updated:** 2026-01-28

README.md

@@ -1,4 +1,4 @@
-# Leo Claude Marketplace - v5.1.0
+# Leo Claude Marketplace - v5.3.0
 
 A collection of Claude Code plugins for project management, infrastructure automation, and development workflows.
 
@@ -19,7 +19,7 @@ AI-guided sprint planning with full Gitea integration. Transforms a proven 15-sp
 - Branch-aware security (development/staging/production)
 - Pre-sprint-close code quality review and test verification
 
-**Commands:** `/sprint-plan`, `/sprint-start`, `/sprint-status`, `/sprint-close`, `/labels-sync`, `/initial-setup`, `/project-init`, `/project-sync`, `/review`, `/test-check`, `/test-gen`, `/debug-report`, `/debug-review`, `/suggest-version`, `/proposal-status`
+**Commands:** `/sprint-plan`, `/sprint-start`, `/sprint-status`, `/sprint-close`, `/sprint-diagram`, `/labels-sync`, `/initial-setup`, `/project-init`, `/project-sync`, `/review`, `/test-check`, `/test-gen`, `/debug-report`, `/debug-review`, `/suggest-version`, `/proposal-status`
 
 #### [git-flow](./plugins/git-flow/README.md) *NEW in v3.0.0*
 **Git Workflow Automation**
@@ -44,14 +44,14 @@ Comprehensive pull request review using specialized agents.
 - Actionable feedback with suggested fixes
 - Gitea integration for automated review submission
 
-**Commands:** `/pr-review`, `/pr-summary`, `/pr-findings`, `/initial-setup`, `/project-init`, `/project-sync`
+**Commands:** `/pr-review`, `/pr-summary`, `/pr-findings`, `/pr-diff`, `/initial-setup`, `/project-init`, `/project-sync`
 
 #### [claude-config-maintainer](./plugins/claude-config-maintainer/README.md)
 **CLAUDE.md Optimization and Maintenance**
 
 Analyze, optimize, and create CLAUDE.md configuration files for Claude Code projects.
 
-**Commands:** `/config-analyze`, `/config-optimize`, `/config-init`
+**Commands:** `/config-analyze`, `/config-optimize`, `/config-init`, `/config-diff`, `/config-lint`
 
 #### [contract-validator](./plugins/contract-validator/README.md) *NEW in v5.0.0*
 **Cross-Plugin Compatibility Validation**
@@ -64,7 +64,7 @@ Validate plugin marketplaces for command conflicts, tool overlaps, and broken ag
 - Data flow validation for agent sequences
 - Markdown or JSON reports with actionable suggestions
 
-**Commands:** `/validate-contracts`, `/check-agent`, `/list-interfaces`, `/initial-setup`
+**Commands:** `/validate-contracts`, `/check-agent`, `/list-interfaces`, `/dependency-graph`, `/initial-setup`
 
 ### Productivity
 
@@ -84,7 +84,7 @@ Transform vague requests into clear specifications using structured methodology.
 
 Automatic documentation drift detection and synchronization.
 
-**Commands:** `/doc-audit`, `/doc-sync`
+**Commands:** `/doc-audit`, `/doc-sync`, `/changelog-gen`, `/doc-coverage`, `/stale-docs`
 
 #### [project-hygiene](./plugins/project-hygiene/README.md)
 **Post-Task Cleanup Automation**
@@ -107,7 +107,7 @@ Security vulnerability detection and code refactoring tools.
 
 Full CRUD operations for network infrastructure management directly from Claude Code.
 
-**Commands:** `/initial-setup`, `/cmdb-search`, `/cmdb-device`, `/cmdb-ip`, `/cmdb-site`, `/cmdb-audit`, `/cmdb-register`, `/cmdb-sync`
+**Commands:** `/initial-setup`, `/cmdb-search`, `/cmdb-device`, `/cmdb-ip`, `/cmdb-site`, `/cmdb-audit`, `/cmdb-register`, `/cmdb-sync`, `/cmdb-topology`, `/change-audit`, `/ip-conflicts`
 
 ### Data Engineering
 
@@ -122,7 +122,7 @@ Comprehensive data engineering toolkit with persistent DataFrame storage.
 - 100k row limit with chunking support
 - Auto-detection of dbt projects
 
-**Commands:** `/ingest`, `/profile`, `/schema`, `/explain`, `/lineage`, `/run`
+**Commands:** `/ingest`, `/profile`, `/schema`, `/explain`, `/lineage`, `/lineage-viz`, `/run`, `/dbt-test`, `/data-quality`, `/initial-setup`
 
 ### Visualization
 
@@ -138,7 +138,7 @@ Visualization toolkit with version-locked component validation and design token
 - 5 Page tools for multi-page app structure
 - Dual theme storage: user-level and project-level
 
-**Commands:** `/chart`, `/dashboard`, `/theme`, `/theme-new`, `/theme-css`, `/component`, `/initial-setup`
+**Commands:** `/chart`, `/chart-export`, `/dashboard`, `/theme`, `/theme-new`, `/theme-css`, `/component`, `/accessibility-check`, `/breakpoints`, `/initial-setup`
 
 ## MCP Servers
 

docs/COMMANDS-CHEATSHEET.md

@@ -24,6 +24,7 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **projman** | `/debug-review` | | X | Investigate diagnostic issues and propose fixes with approval gates |
 | **projman** | `/suggest-version` | | X | Analyze CHANGELOG and recommend semantic version bump |
 | **projman** | `/proposal-status` | | X | View proposal and implementation hierarchy with status |
+| **projman** | `/sprint-diagram` | | X | Generate Mermaid diagram of sprint issues with dependencies |
 | **git-flow** | `/commit` | | X | Create commit with auto-generated conventional message |
 | **git-flow** | `/commit-push` | | X | Commit and push to remote in one operation |
 | **git-flow** | `/commit-merge` | | X | Commit current changes, then merge into target branch |
@@ -39,10 +40,14 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **pr-review** | `/pr-review` | | X | Full multi-agent PR review with confidence scoring |
 | **pr-review** | `/pr-summary` | | X | Quick summary of PR changes |
 | **pr-review** | `/pr-findings` | | X | List and filter review findings by category/severity |
+| **pr-review** | `/pr-diff` | | X | Formatted diff with inline review comments and annotations |
 | **clarity-assist** | `/clarify` | | X | Full 4-D prompt optimization with ND accommodations |
 | **clarity-assist** | `/quick-clarify` | | X | Rapid single-pass clarification for simple requests |
 | **doc-guardian** | `/doc-audit` | | X | Full documentation audit - scans for doc drift |
 | **doc-guardian** | `/doc-sync` | | X | Synchronize pending documentation updates |
+| **doc-guardian** | `/changelog-gen` | | X | Generate changelog from conventional commits |
+| **doc-guardian** | `/doc-coverage` | | X | Documentation coverage metrics by function/class |
+| **doc-guardian** | `/stale-docs` | | X | Flag documentation behind code changes |
 | **doc-guardian** | *PostToolUse hook* | X | | Silently detects doc drift on Write/Edit |
 | **code-sentinel** | `/security-scan` | | X | Full security audit (SQL injection, XSS, secrets, etc.) |
 | **code-sentinel** | `/refactor` | | X | Apply refactoring patterns to improve code |
@@ -51,6 +56,8 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **claude-config-maintainer** | `/config-analyze` | | X | Analyze CLAUDE.md for optimization opportunities |
 | **claude-config-maintainer** | `/config-optimize` | | X | Optimize CLAUDE.md structure with preview/backup |
 | **claude-config-maintainer** | `/config-init` | | X | Initialize new CLAUDE.md for a project |
+| **claude-config-maintainer** | `/config-diff` | | X | Track CLAUDE.md changes over time with behavioral impact |
+| **claude-config-maintainer** | `/config-lint` | | X | Lint CLAUDE.md for anti-patterns and best practices |
 | **cmdb-assistant** | `/initial-setup` | | X | Setup wizard for NetBox MCP server |
 | **cmdb-assistant** | `/cmdb-search` | | X | Search NetBox for devices, IPs, sites |
 | **cmdb-assistant** | `/cmdb-device` | | X | Manage network devices (create, view, update, delete) |
@@ -59,6 +66,9 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **cmdb-assistant** | `/cmdb-audit` | | X | Data quality analysis (VMs, devices, naming, roles) |
 | **cmdb-assistant** | `/cmdb-register` | | X | Register current machine into NetBox with running apps |
 | **cmdb-assistant** | `/cmdb-sync` | | X | Sync machine state with NetBox (detect drift, update) |
+| **cmdb-assistant** | `/cmdb-topology` | | X | Infrastructure topology diagrams (rack, network, site views) |
+| **cmdb-assistant** | `/change-audit` | | X | NetBox audit trail queries with filtering |
+| **cmdb-assistant** | `/ip-conflicts` | | X | Detect IP conflicts and overlapping prefixes |
 | **project-hygiene** | *PostToolUse hook* | X | | Removes temp files, warns about unexpected root files |
 | **data-platform** | `/ingest` | | X | Load data from CSV, Parquet, JSON into DataFrame |
 | **data-platform** | `/profile` | | X | Generate data profiling report with statistics |
@@ -66,6 +76,9 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **data-platform** | `/explain` | | X | Explain query execution plan |
 | **data-platform** | `/lineage` | | X | Show dbt model lineage and dependencies |
 | **data-platform** | `/run` | | X | Run dbt models with validation |
+| **data-platform** | `/lineage-viz` | | X | dbt lineage visualization as Mermaid diagrams |
+| **data-platform** | `/dbt-test` | | X | Formatted dbt test runner with summary and failure details |
+| **data-platform** | `/data-quality` | | X | DataFrame quality checks (nulls, duplicates, types, outliers) |
 | **data-platform** | `/initial-setup` | | X | Setup wizard for data-platform MCP servers |
 | **data-platform** | *SessionStart hook* | X | | Checks PostgreSQL connection (non-blocking warning) |
 | **viz-platform** | `/initial-setup` | | X | Setup wizard for viz-platform MCP server |
@@ -75,7 +88,15 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **viz-platform** | `/theme-new` | | X | Create new custom theme with design tokens |
 | **viz-platform** | `/theme-css` | | X | Export theme as CSS custom properties |
 | **viz-platform** | `/component` | | X | Inspect DMC component props and validation |
+| **viz-platform** | `/chart-export` | | X | Export charts to PNG, SVG, PDF via kaleido |
+| **viz-platform** | `/accessibility-check` | | X | Color blind validation (WCAG contrast ratios) |
+| **viz-platform** | `/breakpoints` | | X | Configure responsive layout breakpoints |
 | **viz-platform** | *SessionStart hook* | X | | Checks DMC version (non-blocking warning) |
+| **contract-validator** | `/validate-contracts` | | X | Full marketplace compatibility validation |
+| **contract-validator** | `/check-agent` | | X | Validate single agent definition |
+| **contract-validator** | `/list-interfaces` | | X | Show all plugin interfaces |
+| **contract-validator** | `/dependency-graph` | | X | Mermaid visualization of plugin dependencies |
+| **contract-validator** | `/initial-setup` | | X | Setup wizard for contract-validator MCP |
 
 ---
 
@@ -91,6 +112,7 @@ Quick reference for all commands in the Leo Claude Marketplace.
 | **Infrastructure** | cmdb-assistant | NetBox CMDB management |
 | **Data Engineering** | data-platform | pandas, PostgreSQL, dbt operations |
 | **Visualization** | viz-platform | DMC validation, Plotly charts, theming |
+| **Validation** | contract-validator | Cross-plugin compatibility checks |
 | **Maintenance** | project-hygiene | Automatic cleanup |
 
 ---
@@ -249,9 +271,10 @@ Some plugins require MCP server connectivity:
 | cmdb-assistant | NetBox | Infrastructure CMDB |
 | data-platform | pandas, PostgreSQL, dbt | DataFrames, database queries, dbt builds |
 | viz-platform | viz-platform | DMC validation, charts, layouts, themes, pages |
+| contract-validator | contract-validator | Plugin interface parsing, compatibility validation |
 
 Ensure credentials are configured in `~/.config/claude/gitea.env`, `~/.config/claude/netbox.env`, or `~/.config/claude/postgres.env`.
 
 ---
 
-*Last Updated: 2026-01-26*
+*Last Updated: 2026-01-28*

mcp-servers/gitea/mcp_server/gitea_client.py

@@ -53,6 +53,7 @@ class GiteaClient:
         self,
         state: str = 'open',
         labels: Optional[List[str]] = None,
+        milestone: Optional[str] = None,
         repo: Optional[str] = None
     ) -> List[Dict]:
         """
@@ -61,6 +62,7 @@ class GiteaClient:
         Args:
             state: Issue state (open, closed, all)
             labels: Filter by labels
+            milestone: Filter by milestone title (exact match)
             repo: Repository in 'owner/repo' format
 
         Returns:
@@ -71,6 +73,8 @@ class GiteaClient:
         params = {'state': state}
         if labels:
             params['labels'] = ','.join(labels)
+        if milestone:
+            params['milestones'] = milestone
         logger.info(f"Listing issues from {owner}/{target_repo} with state={state}")
         response = self.session.get(url, params=params)
         response.raise_for_status()

mcp-servers/gitea/mcp_server/server.py

@@ -26,6 +26,44 @@ logging.getLogger("mcp").setLevel(logging.ERROR)
 logger = logging.getLogger(__name__)
 
 
+def _coerce_types(arguments: dict) -> dict:
+    """
+    Coerce argument types to handle MCP serialization quirks.
+
+    MCP sometimes passes integers as strings and arrays as JSON strings.
+    This function normalizes them to the expected Python types.
+    """
+    coerced = {}
+    for key, value in arguments.items():
+        if value is None:
+            coerced[key] = value
+            continue
+
+        # Coerce integer fields
+        int_fields = {'issue_number', 'milestone_id', 'pr_number', 'depends_on', 'milestone', 'limit'}
+        if key in int_fields and isinstance(value, str):
+            try:
+                coerced[key] = int(value)
+                continue
+            except ValueError:
+                pass
+
+        # Coerce array fields that might be JSON strings
+        array_fields = {'labels', 'tags', 'issue_numbers', 'comments'}
+        if key in array_fields and isinstance(value, str):
+            try:
+                parsed = json.loads(value)
+                if isinstance(parsed, list):
+                    coerced[key] = parsed
+                    continue
+            except json.JSONDecodeError:
+                pass
+
+        coerced[key] = value
+
+    return coerced
+
+
 class GiteaMCPServer:
     """MCP Server for Gitea integration"""
 
@@ -88,6 +126,10 @@ class GiteaMCPServer:
                                 "items": {"type": "string"},
                                 "description": "Filter by labels"
                             },
+                            "milestone": {
+                                "type": "string",
+                                "description": "Filter by milestone title (exact match)"
+                            },
                             "repo": {
                                 "type": "string",
                                 "description": "Repository name (for PMO mode)"
@@ -899,6 +941,9 @@ class GiteaMCPServer:
                 List of TextContent with results
             """
             try:
+                # Coerce types to handle MCP serialization quirks
+                arguments = _coerce_types(arguments)
+
                 # Route to appropriate tool handler
                 if name == "list_issues":
                     result = await self.issue_tools.list_issues(**arguments)

mcp-servers/gitea/mcp_server/tools/issues.py

@@ -98,6 +98,7 @@ class IssueTools:
         self,
         state: str = 'open',
         labels: Optional[List[str]] = None,
+        milestone: Optional[str] = None,
         repo: Optional[str] = None
     ) -> List[Dict]:
         """
@@ -106,6 +107,7 @@ class IssueTools:
         Args:
             state: Issue state (open, closed, all)
             labels: Filter by labels
+            milestone: Filter by milestone title (exact match)
             repo: Override configured repo (for PMO multi-repo)
 
         Returns:
@@ -124,7 +126,7 @@ class IssueTools:
         loop = asyncio.get_event_loop()
         return await loop.run_in_executor(
             None,
-            lambda: self.gitea.list_issues(state, labels, repo)
+            lambda: self.gitea.list_issues(state, labels, milestone, repo)
         )
 
     async def get_issue(

plugins/clarity-assist/agents/clarity-coach.md

@@ -1,5 +1,15 @@
 # Clarity Coach Agent
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  💬 CLARITY-ASSIST · Clarity Coach                               │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Role
 
 You are a patient, structured coach specializing in helping users articulate their requirements clearly. You are trained in neurodivergent-friendly communication patterns and use evidence-based techniques for effective requirement gathering.

plugins/clarity-assist/commands/clarify.md

@@ -1,5 +1,17 @@
 # /clarify - Full Prompt Optimization
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  💬 CLARITY-ASSIST · Prompt Optimization                         │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the workflow.
+
 ## Purpose
 
 Transform vague, incomplete, or ambiguous requests into clear, actionable specifications using the 4-D methodology with neurodivergent-friendly accommodations.

plugins/clarity-assist/commands/quick-clarify.md

@@ -1,5 +1,17 @@
 # /quick-clarify - Rapid Clarification Mode
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  💬 CLARITY-ASSIST · Quick Clarify                               │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the workflow.
+
 ## Purpose
 
 Single-pass clarification for requests that are mostly clear but need minor disambiguation.

plugins/claude-config-maintainer/agents/maintainer.md

@@ -7,6 +7,16 @@ description: CLAUDE.md optimization and maintenance agent
 
 You are the **Maintainer Agent** - a specialist in creating and optimizing CLAUDE.md configuration files for Claude Code projects. Your role is to ensure CLAUDE.md files are clear, concise, well-structured, and follow best practices.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ⚙️ CONFIG-MAINTAINER · CLAUDE.md Optimization                   │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Your Personality
 
 **Optimization-Focused:**

plugins/claude-config-maintainer/commands/analyze.md

@@ -6,6 +6,18 @@ description: Analyze CLAUDE.md for optimization opportunities and plugin integra
 
 This command analyzes your project's CLAUDE.md file and provides a detailed report on optimization opportunities and plugin integration status.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ⚙️ CONFIG-MAINTAINER · CLAUDE.md Analysis                       │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the analysis.
+
 ## What This Command Does
 
 1. **Read CLAUDE.md** - Locates and reads the project's CLAUDE.md file

plugins/claude-config-maintainer/commands/config-diff.md

@@ -6,6 +6,18 @@ description: Show diff between current CLAUDE.md and last commit
 
 This command shows differences between your current CLAUDE.md file and previous versions, helping track configuration drift and review changes before committing.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ⚙️ CONFIG-MAINTAINER · CLAUDE.md Diff                           │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the diff.
+
 ## What This Command Does
 
 1. **Detect CLAUDE.md Location** - Finds the project's CLAUDE.md file

plugins/claude-config-maintainer/commands/config-lint.md

@@ -6,6 +6,18 @@ description: Lint CLAUDE.md for common anti-patterns and best practices
 
 This command checks your CLAUDE.md file against best practices and detects common anti-patterns that can cause issues with Claude Code.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ⚙️ CONFIG-MAINTAINER · CLAUDE.md Lint                           │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the linting.
+
 ## What This Command Does
 
 1. **Parse Structure** - Validates markdown structure and hierarchy

plugins/claude-config-maintainer/commands/init.md

@@ -6,6 +6,18 @@ description: Initialize a new CLAUDE.md file for a project
 
 This command creates a new CLAUDE.md file tailored to your project, gathering context and generating appropriate content.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ⚙️ CONFIG-MAINTAINER · CLAUDE.md Initialization                 │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the initialization.
+
 ## What This Command Does
 
 1. **Gather Context** - Analyzes project structure and asks clarifying questions

plugins/claude-config-maintainer/commands/optimize.md

@@ -6,6 +6,18 @@ description: Optimize CLAUDE.md structure and content
 
 This command automatically optimizes your project's CLAUDE.md file based on best practices and identified issues.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ⚙️ CONFIG-MAINTAINER · CLAUDE.md Optimization                   │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the optimization.
+
 ## What This Command Does
 
 1. **Analyze Current File** - Identifies all optimization opportunities

plugins/cmdb-assistant/agents/cmdb-assistant.md

@@ -2,6 +2,16 @@
 
 You are an infrastructure management assistant specialized in NetBox CMDB operations. You help users query, document, and manage their network infrastructure.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Infrastructure Management                   │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Capabilities
 
 You have full access to NetBox via MCP tools covering:

plugins/cmdb-assistant/commands/change-audit.md

@@ -4,6 +4,18 @@ description: Audit NetBox changes with filtering by date, user, or object type
 
 # CMDB Change Audit
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Change Audit                                │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the audit.
+
 Query and analyze the NetBox audit log for change tracking and compliance.
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-audit.md

@@ -4,6 +4,18 @@ description: Audit NetBox data quality and identify consistency issues
 
 # CMDB Data Quality Audit
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Data Quality Audit                          │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the audit.
+
 Analyze NetBox data for quality issues and best practice violations.
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-device.md

@@ -1,5 +1,17 @@
 # CMDB Device Management
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Device Management                           │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the operation.
+
 Manage network devices in NetBox - create, view, update, or delete.
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-ip.md

@@ -1,5 +1,17 @@
 # CMDB IP Management
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · IP Management                               │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the operation.
+
 Manage IP addresses and prefixes in NetBox.
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-register.md

@@ -4,6 +4,18 @@ description: Register the current machine into NetBox with all running applicati
 
 # CMDB Machine Registration
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Machine Registration                        │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the registration.
+
 Register the current machine into NetBox, including hardware info, network interfaces, and running applications (Docker containers, services).
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-search.md

@@ -1,5 +1,17 @@
 # CMDB Search
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Search                                      │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the search.
+
 Search NetBox for devices, IPs, sites, or any CMDB object.
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-site.md

@@ -1,5 +1,17 @@
 # CMDB Site Management
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Site Management                             │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the operation.
+
 Manage sites and locations in NetBox.
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-sync.md

@@ -4,6 +4,18 @@ description: Synchronize current machine state with existing NetBox record
 
 # CMDB Machine Sync
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Machine Sync                                │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the synchronization.
+
 Update an existing NetBox device record with the current machine state. Compares local system information with NetBox and applies changes.
 
 ## Usage

plugins/cmdb-assistant/commands/cmdb-topology.md

@@ -4,6 +4,18 @@ description: Generate infrastructure topology diagrams from NetBox data
 
 # CMDB Topology Visualization
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Topology                                    │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the visualization.
+
 Generate Mermaid diagrams showing infrastructure topology from NetBox.
 
 ## Usage

plugins/cmdb-assistant/commands/initial-setup.md

@@ -4,6 +4,18 @@ description: Interactive setup wizard for cmdb-assistant plugin - configures Net
 
 # CMDB Assistant Setup Wizard
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · Setup Wizard                                │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the setup.
+
 This command sets up the cmdb-assistant plugin with NetBox integration.
 
 ## Important Context

plugins/cmdb-assistant/commands/ip-conflicts.md

@@ -4,6 +4,18 @@ description: Detect IP address conflicts and overlapping prefixes in NetBox
 
 # CMDB IP Conflict Detection
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🖥️ CMDB-ASSISTANT · IP Conflict Detection                       │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the analysis.
+
 Scan NetBox IPAM data to identify IP address conflicts and overlapping prefixes.
 
 ## Usage

plugins/code-sentinel/agents/refactor-advisor.md

@@ -6,6 +6,16 @@ description: Code structure and refactoring specialist
 
 You are a software architect specializing in code quality, design patterns, and refactoring.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔒 CODE-SENTINEL · Refactor Advisory                            │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Expertise
 
 - Martin Fowler's refactoring catalog

plugins/code-sentinel/agents/security-reviewer.md

@@ -6,6 +6,16 @@ description: Security-focused code review agent
 
 You are a security engineer specializing in application security and secure coding practices.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔒 CODE-SENTINEL · Security Review                              │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Expertise
 
 - OWASP Top 10 vulnerabilities

plugins/code-sentinel/commands/refactor-dry.md

@@ -6,6 +6,18 @@ description: Preview refactoring changes without applying them
 
 Analyze and preview refactoring opportunities without making changes.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔒 CODE-SENTINEL · Refactor Preview                             │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the analysis.
+
 ## Usage
 ```
 /refactor-dry <target> [--all]

plugins/code-sentinel/commands/refactor.md

@@ -6,6 +6,18 @@ description: Apply refactoring patterns to improve code structure and maintainab
 
 Apply refactoring transformations to specified code.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔒 CODE-SENTINEL · Refactor                                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the refactoring workflow.
+
 ## Usage
 ```
 /refactor <target> [--pattern=<pattern>]

plugins/code-sentinel/commands/security-scan.md

@@ -6,6 +6,18 @@ description: Full security audit of codebase - scans all files for vulnerability
 
 Comprehensive security audit of the project.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔒 CODE-SENTINEL · Security Scan                                │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the scan workflow.
+
 ## Process
 
 1. **File Discovery**

plugins/contract-validator/agents/agent-check.md

@@ -2,6 +2,16 @@
 
 You are an agent definition validator. Your role is to verify that a specific agent's tool references and data flow are valid.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ✅ CONTRACT-VALIDATOR · Agent Validation                        │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Capabilities
 
 - Parse agent definitions from CLAUDE.md

plugins/contract-validator/agents/full-validation.md

@@ -2,6 +2,16 @@
 
 You are a contract validation specialist. Your role is to perform comprehensive cross-plugin compatibility validation for the entire marketplace.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ✅ CONTRACT-VALIDATOR · Full Validation                         │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Capabilities
 
 - Parse plugin interfaces from README.md files

plugins/contract-validator/commands/check-agent.md

@@ -1,5 +1,17 @@
 # /check-agent - Validate Agent Definition
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ✅ CONTRACT-VALIDATOR · Agent Check                              │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the validation.
+
 Validate a single agent's tool references and data flow.
 
 ## Usage

plugins/contract-validator/commands/dependency-graph.md

@@ -1,5 +1,17 @@
 # /dependency-graph - Generate Dependency Visualization
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ✅ CONTRACT-VALIDATOR · Dependency Graph                         │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the visualization.
+
 Generate a Mermaid flowchart showing plugin dependencies, data flows, and tool relationships.
 
 ## Usage

plugins/contract-validator/commands/initial-setup.md

@@ -4,6 +4,18 @@ description: Interactive setup wizard for contract-validator plugin - verifies M
 
 # Contract-Validator Setup Wizard
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ✅ CONTRACT-VALIDATOR · Setup Wizard                             │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the setup.
+
 This command sets up the contract-validator plugin for cross-plugin compatibility validation.
 
 ## Important Context

plugins/contract-validator/commands/list-interfaces.md

@@ -1,5 +1,17 @@
 # /list-interfaces - Show Plugin Interfaces
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ✅ CONTRACT-VALIDATOR · List Interfaces                         │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the interface listing.
+
 Display what each plugin in the marketplace produces and accepts.
 
 ## Usage

plugins/contract-validator/commands/validate-contracts.md

@@ -1,5 +1,17 @@
 # /validate-contracts - Full Contract Validation
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  ✅ CONTRACT-VALIDATOR · Full Validation                         │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the validation.
+
 Run comprehensive cross-plugin compatibility validation for the entire marketplace.
 
 ## Usage

plugins/data-platform/agents/data-analysis.md

@@ -2,6 +2,16 @@
 
 You are a data analysis specialist. Your role is to help users explore, profile, and understand their data.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Data Analysis                                │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Capabilities
 
 - Profile datasets with statistical summaries

plugins/data-platform/agents/data-ingestion.md

@@ -2,6 +2,16 @@
 
 You are a data ingestion specialist. Your role is to help users load, transform, and prepare data for analysis.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Data Ingestion                               │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Capabilities
 
 - Load data from CSV, Parquet, JSON files

plugins/data-platform/commands/data-quality.md

@@ -1,5 +1,17 @@
 # /data-quality - Data Quality Assessment
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Data Quality                                  │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the assessment.
+
 Comprehensive data quality check for DataFrames with pass/warn/fail scoring.
 
 ## Usage

plugins/data-platform/commands/dbt-test.md

@@ -1,5 +1,17 @@
 # /dbt-test - Run dbt Tests
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · dbt Tests                                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the tests.
+
 Execute dbt tests with formatted pass/fail results.
 
 ## Usage

plugins/data-platform/commands/explain.md

@@ -1,5 +1,17 @@
 # /explain - dbt Model Explanation
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Model Explanation                             │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the explanation.
+
 Explain a dbt model's purpose, dependencies, and SQL logic.
 
 ## Usage

plugins/data-platform/commands/ingest.md

@@ -1,5 +1,17 @@
 # /ingest - Data Ingestion
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Ingest                                        │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the ingestion.
+
 Load data from files or database into the data platform.
 
 ## Usage

plugins/data-platform/commands/initial-setup.md

@@ -4,6 +4,18 @@ description: Interactive setup wizard for data-platform plugin - configures MCP
 
 # Data Platform Setup Wizard
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Setup Wizard                                  │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the setup.
+
 This command sets up the data-platform plugin with pandas, PostgreSQL, and dbt integration.
 
 ## Important Context

plugins/data-platform/commands/lineage-viz.md

@@ -1,5 +1,17 @@
 # /lineage-viz - Mermaid Lineage Visualization
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Lineage Visualization                         │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the visualization.
+
 Generate Mermaid flowchart syntax for dbt model lineage.
 
 ## Usage

plugins/data-platform/commands/lineage.md

@@ -1,5 +1,17 @@
 # /lineage - Data Lineage Visualization
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Lineage                                       │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the visualization.
+
 Show data lineage for dbt models or database tables.
 
 ## Usage

plugins/data-platform/commands/profile.md

@@ -1,5 +1,17 @@
 # /profile - Data Profiling
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Data Profile                                  │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the profiling.
+
 Generate statistical profile and quality report for a DataFrame.
 
 ## Usage

plugins/data-platform/commands/run.md

@@ -1,5 +1,17 @@
 # /run - Execute dbt Models
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · dbt Run                                       │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the execution.
+
 Run dbt models with automatic pre-validation.
 
 ## Usage

plugins/data-platform/commands/schema.md

@@ -1,5 +1,17 @@
 # /schema - Schema Exploration
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📊 DATA-PLATFORM · Schema Explorer                               │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the exploration.
+
 Display schema information for database tables or DataFrames.
 
 ## Usage

plugins/doc-guardian/agents/doc-analyzer.md

@@ -6,6 +6,16 @@ description: Specialized agent for documentation analysis and drift detection
 
 You are an expert technical writer and documentation analyst. Your role is to detect discrepancies between code and documentation.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📝 DOC-GUARDIAN · Documentation Analysis                        │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Capabilities
 
 1. **Pattern Recognition**

plugins/doc-guardian/commands/changelog-gen.md

@@ -6,6 +6,18 @@ description: Generate changelog from conventional commits in Keep-a-Changelog fo
 
 Generate a changelog entry from conventional commits.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📝 DOC-GUARDIAN · Changelog Generation                          │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the generation.
+
 ## Process
 
 1. **Identify Commit Range**

plugins/doc-guardian/commands/doc-audit.md

@@ -6,6 +6,18 @@ description: Full documentation audit - scans entire project for doc drift witho
 
 Perform a comprehensive documentation drift analysis.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📝 DOC-GUARDIAN · Documentation Audit                          │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the audit.
+
 ## Process
 
 1. **Inventory Documentation Files**

plugins/doc-guardian/commands/doc-coverage.md

@@ -6,6 +6,18 @@ description: Calculate documentation coverage percentage for functions and class
 
 Analyze codebase to calculate documentation coverage metrics.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📝 DOC-GUARDIAN · Documentation Coverage                        │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the analysis.
+
 ## Process
 
 1. **Scan Source Files**

plugins/doc-guardian/commands/doc-sync.md

@@ -6,6 +6,18 @@ description: Synchronize all pending documentation updates in a single commit
 
 Apply all pending documentation updates detected by doc-guardian hooks.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📝 DOC-GUARDIAN · Documentation Sync                            │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the sync.
+
 ## Process
 
 1. **Review Pending Queue**

plugins/doc-guardian/commands/stale-docs.md

@@ -6,6 +6,18 @@ description: Detect documentation files that are stale relative to their associa
 
 Identify documentation files that may be outdated based on commit history.
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  📝 DOC-GUARDIAN · Stale Documentation Check                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the check.
+
 ## Process
 
 1. **Map Documentation to Code**

plugins/git-flow/agents/git-assistant.md

@@ -1,5 +1,15 @@
 # Git Assistant Agent
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Git Assistant                                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Role
 
 You are a git workflow assistant that helps users navigate complex git operations, resolve conflicts, and maintain clean repository history.

plugins/git-flow/commands/branch-cleanup.md

@@ -1,5 +1,17 @@
 # /branch-cleanup - Clean Merged and Stale Branches
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Branch Cleanup                                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the workflow.
+
 ## Purpose
 
 Remove branches that have been merged OR whose remote tracking branch no longer exists, both locally and optionally on remote.

plugins/git-flow/commands/branch-start.md

@@ -1,5 +1,17 @@
 # /branch-start - Start New Branch
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Branch Start                                      │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the workflow.
+
 ## Purpose
 
 Create a new feature/fix/chore branch with consistent naming conventions.

plugins/git-flow/commands/commit-merge.md

@@ -1,5 +1,17 @@
 # /commit-merge - Commit and Merge
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Commit & Merge                                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the workflow.
+
 ## Purpose
 
 Commit current changes, then merge the current branch into a target branch.

plugins/git-flow/commands/commit-push.md

@@ -1,5 +1,17 @@
 # /commit-push - Commit and Push
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Commit & Push                                      │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the workflow.
+
 ## Purpose
 
 Create a commit and push to the remote repository in one operation.

plugins/git-flow/commands/commit-sync.md

@@ -1,5 +1,17 @@
 # /commit-sync - Commit, Push, and Sync
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Commit Sync                                        │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the workflow.
+
 ## Purpose
 
 Full sync operation: commit local changes, push to remote, sync with upstream/base branch, and clean up stale remote-tracking branches.

plugins/git-flow/commands/commit.md

@@ -1,5 +1,17 @@
 # /commit - Smart Commit
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Smart Commit                                      │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the commit workflow.
+
 ## Purpose
 
 Create a git commit with an auto-generated conventional commit message based on staged changes.

plugins/git-flow/commands/git-config.md

@@ -1,5 +1,17 @@
 # /git-config - Configure git-flow
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Configuration                                      │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the configuration.
+
 ## Purpose
 
 Configure git-flow settings for the current project.

plugins/git-flow/commands/git-status.md

@@ -1,5 +1,17 @@
 # /git-status - Enhanced Status
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔀 GIT-FLOW · Status                                             │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the status display.
+
 ## Purpose
 
 Show comprehensive git status with recommendations and insights.

plugins/pr-review/agents/coordinator.md

@@ -1,5 +1,15 @@
 # Coordinator Agent
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Review Coordinator                               │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Role
 
 You are the review coordinator that orchestrates the multi-agent PR review process. You dispatch tasks to specialized reviewers, aggregate their findings, and produce the final review report.

plugins/pr-review/agents/maintainability-auditor.md

@@ -1,5 +1,15 @@
 # Maintainability Auditor Agent
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Maintainability Audit                            │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Role
 
 You are a code quality reviewer that identifies maintainability issues, code smells, and opportunities to improve code clarity and long-term health.

plugins/pr-review/agents/performance-analyst.md

@@ -1,5 +1,15 @@
 # Performance Analyst Agent
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Performance Analysis                             │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Role
 
 You are a performance-focused code reviewer that identifies performance issues, inefficiencies, and optimization opportunities in pull request changes.

plugins/pr-review/agents/security-reviewer.md

@@ -1,5 +1,15 @@
 # Security Reviewer Agent
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Security Review                                  │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Role
 
 You are a security-focused code reviewer that identifies vulnerabilities, security anti-patterns, and potential exploits in pull request changes.

plugins/pr-review/agents/test-validator.md

@@ -1,5 +1,15 @@
 # Test Validator Agent
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Test Validation                                  │
+└──────────────────────────────────────────────────────────────────┘
+```
+
 ## Role
 
 You are a test quality reviewer that validates test coverage, test quality, and testing practices in pull request changes.

plugins/pr-review/commands/initial-setup.md

@@ -4,6 +4,18 @@ description: Interactive setup wizard for pr-review plugin - configures Gitea MC
 
 # PR Review Setup Wizard
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Setup Wizard                                      │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the setup.
+
 This command sets up the pr-review plugin. It shares the Gitea MCP server with projman, so if you've already run `/initial-setup` for projman, most of the work is done.
 
 ## Important Context

plugins/pr-review/commands/pr-diff.md

@@ -1,5 +1,17 @@
 # /pr-diff - Annotated PR Diff Viewer
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Diff Viewer                                       │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the diff display.
+
 ## Purpose
 
 Display the PR diff with inline annotations from review comments, making it easy to see what feedback has been given alongside the code changes.

plugins/pr-review/commands/pr-findings.md

@@ -1,5 +1,17 @@
 # /pr-findings - Filter Review Findings
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Findings                                          │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the findings display.
+
 ## Purpose
 
 List and filter findings from a previous PR review by category, severity, or confidence level.

plugins/pr-review/commands/pr-review.md

@@ -1,5 +1,17 @@
 # /pr-review - Full Multi-Agent Review
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Full Review                                       │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the review.
+
 ## Purpose
 
 Conduct a comprehensive pull request review using specialized agents for security, performance, maintainability, and test coverage.

plugins/pr-review/commands/pr-summary.md

@@ -1,5 +1,17 @@
 # /pr-summary - Quick PR Summary
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Quick Summary                                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the summary.
+
 ## Purpose
 
 Generate a quick summary of PR changes without conducting a full multi-agent review.

plugins/pr-review/commands/project-init.md

@@ -4,6 +4,18 @@ description: Quick project setup - configures only project-level settings for PR
 
 # Project Initialization (PR Review)
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Project Setup                                     │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the setup.
+
 Fast setup for a new project when system-level configuration is already complete.
 
 **Use this when:**

plugins/pr-review/commands/project-sync.md

@@ -4,6 +4,18 @@ description: Sync project configuration with current git remote - use after chan
 
 # Project Sync (PR Review)
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  🔍 PR-REVIEW · Project Sync                                      │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Then proceed with the synchronization.
+
 Updates project configuration when the git remote URL has changed.
 
 **Use this when:**

plugins/projman/agents/code-reviewer.md

@@ -7,6 +7,35 @@ description: Specialized agent for pre-sprint code quality review
 
 You are a code quality reviewer focused on catching issues before sprint close.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+### Header Format
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🏁 CLOSING                                                      ║
+║  Code Review: [Sprint Name]                                      ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name.
+
+### When to Display Header
+- At the start of every response
+- After completing review of each file group
+- In final review summary
+
+### Nested Plugin Calls
+If invoking another plugin during review, use indented single-line header:
+```
+  ┌──────────────────────────────────────────────────────────────────┐
+  │  [ICON] [PLUGIN-NAME] · [Action] (triggered by: projman)         │
+  └──────────────────────────────────────────────────────────────────┘
+```
+
 ## Your Role
 
 - Identify issues that should be fixed before work is marked complete

plugins/projman/agents/executor.md

@@ -31,6 +31,38 @@ curl -X POST "https://gitea.../api/..."
 
 **If you find yourself about to run a bash command for Gitea, STOP and use the MCP tool instead.**
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+### Header Format
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚡ EXECUTION                                                    ║
+║  [Issue Title]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Issue Title]` with the issue being implemented.
+
+### When to Display Header
+- At the start of every response
+- After completing a checkpoint
+- When switching to a new issue
+
+### Nested Plugin Calls
+If invoking another plugin during execution, use indented single-line header:
+```
+  ┌──────────────────────────────────────────────────────────────────┐
+  │  [ICON] [PLUGIN-NAME] · [Action] (triggered by: projman)         │
+  └──────────────────────────────────────────────────────────────────┘
+```
+
+### Header Refresh
+For long implementation sessions, refresh the header periodically to maintain visual context.
+
 ## Your Personality
 
 **Implementation-Focused:**

plugins/projman/agents/orchestrator.md

@@ -36,6 +36,57 @@ curl -X POST "https://gitea.../api/..."
 
 **If you find yourself about to run a bash command for Gitea, STOP and use the MCP tool instead.**
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+### Header Format
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚡ EXECUTION                                                    ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name.
+
+### Sprint Progress Block
+
+After the header, display a progress block:
+
+```
+┌─ Sprint Progress ────────────────────────────────────────────────┐
+│  [Sprint Name]                                                   │
+│  ████████████░░░░░░░░░░░░░░░░░░ 40% complete                     │
+│  ✅ Done: 4    ⏳ Active: 2    ⬚ Pending: 4                       │
+│  Current:                                                        │
+│    #271 ⏳ Implement header component                            │
+│    #272 ⏳ Update agent instructions                             │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+### Progress Bar Calculation
+- Width: 30 characters
+- Filled: `█` (completed percentage)
+- Empty: `░` (remaining percentage)
+- Calculate: `(closed_issues / total_issues) * 30`
+
+### When to Refresh
+- At the start of every response
+- After completing an issue
+- When user requests status update
+- After major phase transitions
+
+### Nested Plugin Calls
+If invoking another plugin, use indented single-line header:
+```
+  ┌──────────────────────────────────────────────────────────────────┐
+  │  [ICON] [PLUGIN-NAME] · [Action] (triggered by: projman)         │
+  └──────────────────────────────────────────────────────────────────┘
+```
+
 ## Your Personality
 
 **Concise and Action-Oriented:**

plugins/projman/agents/planner.md

@@ -36,6 +36,38 @@ curl -X POST "https://gitea.../api/..."
 
 **If you find yourself about to run a bash command for Gitea, STOP and use the MCP tool instead.**
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+### Header Format
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🎯 PLANNING                                                     ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name.
+
+### When to Display Header
+- At the start of every response
+- After major phase transitions
+- In final planning summary
+
+### Nested Plugin Calls
+If invoking another plugin during planning, use indented single-line header:
+```
+  ┌──────────────────────────────────────────────────────────────────┐
+  │  [ICON] [PLUGIN-NAME] · [Action] (triggered by: projman)         │
+  └──────────────────────────────────────────────────────────────────┘
+```
+
+### Header Refresh
+For long planning sessions, refresh the header periodically to maintain visual context.
+
 ## Your Personality
 
 **Thoughtful and Methodical:**

plugins/projman/commands/debug-report.md

@@ -686,3 +686,16 @@ and select "Report an issue I experienced" to describe it.
 - Verify labels exist in the marketplace repo: `Source/Diagnostic`, `Type/Bug`
 - Check the label fetch output in Step 7.2 for errors
 - If labels don't exist, create them first with `/labels-sync` in the marketplace repo
+
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  Debug Report                                                    ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the diagnostic workflow.

plugins/projman/commands/debug-review.md

@@ -572,3 +572,16 @@ Error Message                    → File to Check
 "labels not found"               → labels.py, gitea_client.py
 "create local.*file"             → Command .md file (DO NOT section)
 ```
+
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  Debug Review                                                    ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the investigation workflow.

plugins/projman/commands/initial-setup.md

@@ -443,6 +443,20 @@ If something isn't working after restart, check:
 
 ---
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚙️ SETUP                                                        ║
+║  Initial Setup Wizard                                            ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the setup workflow.
+
 ## Re-Running This Command
 
 This command is safe to run multiple times:

plugins/projman/commands/labels-sync.md

@@ -158,6 +158,19 @@ When creating missing labels, match the format used by existing labels in the re
 - Ensure you're running in a directory with a git repository
 - Check that the `origin` remote is configured
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  Labels Sync                                                     ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the sync workflow.
+
 ## When to Run
 
 Run `/labels-sync` when:

plugins/projman/commands/project-init.md

@@ -207,6 +207,20 @@ You're ready to use projman commands:
 
 ---
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚙️ SETUP                                                        ║
+║  Project Initialization                                          ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the project setup workflow.
+
 ## Troubleshooting
 
 **MCP tools not working?**

plugins/projman/commands/project-sync.md

@@ -180,6 +180,20 @@ MCP tools will now use the new repository.
 
 ---
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚙️ SETUP                                                        ║
+║  Project Sync                                                    ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the sync workflow.
+
 ## Troubleshooting
 
 **"Repository not found" but it exists:**

plugins/projman/commands/proposal-status.md

@@ -119,3 +119,16 @@ Summary:
 **Lesson Linking:**
 - Search lessons with implementation link in metadata
 - Or search by version/sprint tags
+
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  Proposal Status                                                 ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the status report.

plugins/projman/commands/review.md

@@ -74,6 +74,20 @@ Otherwise, review staged changes or changes in the last 5 commits.
 3. Compile findings into the structured report
 4. Provide recommendation: READY / NEEDS ATTENTION / BLOCK
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🏁 CLOSING                                                      ║
+║  Code Review                                                     ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the review workflow.
+
 ## Do NOT
 
 - Rewrite or refactor code automatically

plugins/projman/commands/sprint-close.md

@@ -54,25 +54,34 @@ The orchestrator agent will guide you through:
    - If partial: Keep status as "In Progress", note completed implementations
    - Add summary of what was accomplished
 
-7. **Update CHANGELOG** (MANDATORY)
+7. **New Command Verification** (if applicable)
+   - Check if this sprint added new commands or skills
+   - **IMPORTANT:** New commands are NOT discoverable until session restart
+   - If new commands were added:
+     - List them in sprint close notes
+     - Remind user: "New commands require session restart to test"
+     - Create verification task in next sprint or backlog
+   - **WHY:** Claude Code discovers skills at session start; commands added during a session won't work until restart
+
+8. **Update CHANGELOG** (MANDATORY)
    - Add all sprint changes to `[Unreleased]` section in CHANGELOG.md
    - Categorize: Added, Changed, Fixed, Removed, Deprecated
    - Include plugin prefix (e.g., `- **projman:** New feature`)
 
-8. **Version Check**
+9. **Version Check**
    - Run `/suggest-version` to analyze changes and recommend version bump
    - If release warranted: run `./scripts/release.sh X.Y.Z`
    - Ensures version numbers stay in sync across files
 
-9. **Git Operations**
-   - Commit any remaining work (including CHANGELOG updates)
-   - Merge feature branches if needed
-   - Clean up merged branches
-   - Tag sprint completion (if release created)
+10. **Git Operations**
+    - Commit any remaining work (including CHANGELOG updates)
+    - Merge feature branches if needed
+    - Clean up merged branches
+    - Tag sprint completion (if release created)
 
-10. **Close Milestone**
-   - Use `update_milestone` to close the sprint milestone
-   - Document final completion status
+11. **Close Milestone**
+    - Use `update_milestone` to close the sprint milestone
+    - Document final completion status
 
 ## MCP Tools Available
 
@@ -275,6 +284,22 @@ Would you like me to handle git operations?
 [Y/n]
 ```
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🏁 CLOSING                                                      ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name.
+
+Then proceed with the sprint close workflow.
+
 ## Getting Started
 
 Simply run `/sprint-close` when your sprint is complete. The orchestrator will guide you through:

plugins/projman/commands/sprint-diagram.md

@@ -178,3 +178,16 @@ flowchart LR
 
 Open: 16 | In Progress: 1 | Completed: 1
 ```
+
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  Sprint Diagram                                                  ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed to generate the diagram.

plugins/projman/commands/sprint-plan.md

@@ -375,6 +375,20 @@ Milestone: Sprint 17 - User Authentication (Due: 2025-02-01)
 Wiki: https://gitea.example.com/org/repo/wiki/Change-V1.2.0%3A-Proposal
 ```
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🎯 PLANNING                                                     ║
+║  Sprint Planning                                                 ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the command workflow.
+
 ## Getting Started
 
 Invoke the planner agent by providing your sprint goals. The agent will guide you through the planning process.

plugins/projman/commands/sprint-start.md

@@ -6,9 +6,13 @@ description: Begin sprint execution with relevant lessons learned from previous
 
 You are initiating sprint execution. The orchestrator agent will coordinate the work, analyze dependencies for parallel execution, search for relevant lessons learned, and guide you through the implementation process.
 
-## Sprint Approval Verification
+## Sprint Approval Verification (Recommended)
 
-**CRITICAL: Sprint must be approved before execution.**
+**RECOMMENDED: Sprint should be approved before execution.**
+
+> **Note:** This is a recommended workflow practice, not code-enforced. The orchestrator
+> SHOULD check for approval, but execution will proceed if approval is missing. For
+> critical projects, consider making approval mandatory in your workflow.
 
 The orchestrator checks for approval in the milestone description:
 
@@ -19,16 +23,15 @@ get_milestone(milestone_id=17)
 
 **If Approval Missing:**
 ```
-⚠️ SPRINT NOT APPROVED
+⚠️ SPRINT APPROVAL NOT FOUND (Warning)
 
-Sprint 17 has not been approved for execution.
-The milestone description does not contain an approval record.
+Sprint 17 milestone does not contain an approval record.
 
-Please run /sprint-plan to:
+Recommended: Run /sprint-plan first to:
 1. Review the sprint scope
-2. Approve the execution plan
+2. Document the approved execution plan
 
-Then run /sprint-start again.
+Proceeding anyway - consider adding approval for audit trail.
 ```
 
 **If Approval Found:**
@@ -42,10 +45,10 @@ Then run /sprint-start again.
 Proceeding with execution within approved scope...
 ```
 
-**Scope Enforcement:**
-- Agents can ONLY create branches matching approved patterns
-- Agents can ONLY modify files within approved paths
-- Operations outside scope require re-approval via `/sprint-plan`
+**Scope Enforcement (when approval exists):**
+- Agents SHOULD only create branches matching approved patterns
+- Agents SHOULD only modify files within approved paths
+- Operations outside scope should trigger re-approval via `/sprint-plan`
 
 ## Branch Detection
 
@@ -66,11 +69,11 @@ If you are on a production or staging branch, you MUST stop and ask the user to
 
 The orchestrator agent will:
 
-1. **Verify Sprint Approval**
+1. **Verify Sprint Approval** (Recommended)
    - Check milestone description for `## Sprint Approval` section
-   - If no approval found, STOP and direct user to `/sprint-plan`
+   - If no approval found, WARN user and suggest `/sprint-plan` first
    - If approval found, extract scope (branches, files)
-   - Agents operate ONLY within approved scope
+   - Agents SHOULD operate within approved scope when available
 
 2. **Detect Checkpoints (Resume Support)**
    - Check each open issue for `## Checkpoint` comments
@@ -407,6 +410,22 @@ Executors save checkpoints after major steps:
 - [ ] Step 4
 ```
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚡ EXECUTION                                                    ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name from Gitea.
+
+Then proceed with the command workflow.
+
 ## Getting Started
 
 Simply invoke `/sprint-start` and the orchestrator will:

plugins/projman/commands/sprint-status.md

@@ -206,6 +206,28 @@ Run `/sprint-status` when you want to:
 - Use `/sprint-close` when all issues are completed
 - Use `/sprint-plan` to adjust scope if blocked items can't be unblocked
 
+## Visual Output
+
+When executing this command, display the plugin header followed by a progress block:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚡ EXECUTION                                                    ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+
+┌─ Sprint Progress ────────────────────────────────────────────────┐
+│  [Sprint Name]                                                   │
+│  ████████████░░░░░░░░░░░░░░░░░░ 40% complete                     │
+│  ✅ Done: 4    ⏳ Active: 2    ⬚ Pending: 4                       │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name. Calculate percentage from completed vs total issues.
+
+Then proceed with the full status report.
+
 ## Example Usage
 
 ```

plugins/projman/commands/suggest-version.md

@@ -70,6 +70,19 @@ Analyze CHANGELOG.md and suggest appropriate semantic version bump.
 **Recommendation:** No release needed
 ```
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  Version Analysis                                                ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the version analysis.
+
 ## Integration
 
 This command helps maintain proper versioning workflow:

plugins/projman/commands/test-check.md

@@ -161,3 +161,17 @@ If framework not detected:
 1. List what was checked
 2. Ask user to specify the test command
 3. Offer common suggestions based on file types found
+
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🏁 CLOSING                                                      ║
+║  Test Verification                                               ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the test check workflow.

plugins/projman/commands/test-gen.md

@@ -111,6 +111,19 @@ pytest tests/test_orders.py -v
 | Cargo.toml | cargo test |
 | mix.exs | ExUnit |
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  Test Generation                                                 ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Then proceed with the test generation workflow.
+
 ## Integration with /test-check
 
 - `/test-gen` creates new tests