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

Reviewed-on: #311

.claude-plugin/marketplace.json

@@ -6,12 +6,12 @@
   },
   "metadata": {
     "description": "Project management plugins with Gitea and NetBox integrations",
-    "version": "5.2.0"
+    "version": "5.4.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,6 +4,96 @@ 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/).
 
+## [5.4.0] - 2026-01-28
+
+### Added
+
+#### Sprint 7: Multi-Model Agent Support
+Configurable model selection for agents with inheritance chain.
+
+**Model Configuration:**
+- Agent-level `model` field in YAML frontmatter (opus|sonnet|haiku)
+- Plugin-level `defaultModel` in plugin.json
+- Inheritance: Agent → Plugin → System default (sonnet)
+
+**Recommended Model Assignments:**
+| Model | Use Case | Agents |
+|-------|----------|--------|
+| **Opus** | Complex reasoning, security analysis | planner, code-reviewer, security-reviewer, data-analysis |
+| **Sonnet** | Implementation, coordination | orchestrator, executor, layout-builder, data-ingestion |
+| **Haiku** | Quick validation | component-check, agent-check |
+
+**Documentation:**
+- `docs/MODEL-RECOMMENDATIONS.md` - Central model selection guide
+- `docs/CONFIGURATION.md` - Added agent model configuration section
+- `CLAUDE.md` - Added model config quick reference
+
+**Agent Updates (7 files):**
+- Opus: planner, code-reviewer (projman), security-reviewer (pr-review, code-sentinel), data-analysis
+- Haiku: component-check (viz-platform), agent-check (contract-validator)
+
+**Plugin Manifest Updates (6 files):**
+- All plugins with agents now have `defaultModel: sonnet`
+- Version bumps: projman 3.3.0, pr-review 1.1.0, data-platform 1.1.0, viz-platform 1.1.0, code-sentinel 1.0.1, contract-validator 1.1.0
+
+**Validation:**
+- `scripts/validate-marketplace.sh` - Added model field validation (v5.4.0+)
+
+**Sprint Completed:**
+- Milestone: Sprint 7 - Multi-Model Agent Support
+- Issues: #302, #303, #304, #305, #306
+- PRs: #307, #308
+- Wiki: [Change V5.4.0: Multi-Model Support (Sprint 7 Implementation)](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/Change-V5.4.0%3A-Multi-Model-Support-%28Sprint-7-Implementation%29)
+
+---
+
+## [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

CLAUDE.md

@@ -1,48 +1,44 @@
 # CLAUDE.md
 
 This file provides guidance to Claude Code when working with code in this repository.
-## ⛔ MANDATORY BEHAVIOR RULES - READ FIRST
 
-**These rules are NON-NEGOTIABLE. Violating them wastes the user's time and money.**
+## ⛔ RULES - READ FIRST
 
-### 1. WHEN USER ASKS YOU TO CHECK SOMETHING - CHECK EVERYTHING
+### Behavioral Rules
-- Search ALL locations, not just where you think it is
-- Check cache directories: `~/.claude/plugins/cache/`
-- Check installed: `~/.claude/plugins/marketplaces/`
-- Check source: `~/claude-plugins-work/`
-- **NEVER say "no" or "that's not the issue" without exhaustive verification**
 
-### 2. WHEN USER SAYS SOMETHING IS WRONG - BELIEVE THEM
+| Rule | Summary |
-- The user knows their system better than you
+|------|---------|
-- Investigate thoroughly before disagreeing
+| **Check everything** | Search cache (`~/.claude/plugins/cache/`), installed (`~/.claude/plugins/marketplaces/`), and source (`~/claude-plugins-work/`) |
-- If user suspects cache, CHECK THE CACHE
+| **Believe the user** | User knows their system. Investigate before disagreeing. |
-- If user suspects a file, READ THE FILE
+| **Verify before "done"** | Run commands, show output, check all locations. "Done" = verified working. |
-- **Your confidence is often wrong. User's instincts are often right.**
+| **Show what's asked** | Don't interpret or summarize unless asked. |
 
-### 3. NEVER SAY "DONE" WITHOUT VERIFICATION
+### After Plugin Updates
-- Run the actual command/script to verify
-- Show the output to the user
-- Check ALL affected locations
-- **"Done" means VERIFIED WORKING, not "I made changes"**
 
-### 4. SHOW EXACTLY WHAT USER ASKS FOR
+Run `./scripts/verify-hooks.sh`. If changes affect MCP servers or hooks, inform user to restart session.
-- If user asks for messages, show the MESSAGES
+**DO NOT clear cache mid-session** - breaks loaded MCP tools.
-- If user asks for code, show the CODE
-- If user asks for output, show the OUTPUT
-- **Don't interpret or summarize unless asked**
 
-### 5. AFTER PLUGIN UPDATES - VERIFY AND RESTART
+### NEVER USE CLI TOOLS FOR EXTERNAL SERVICES
+- **FORBIDDEN:** `gh`, `tea`, `curl` to APIs, any CLI that talks to Gitea/GitHub/external services
+- **REQUIRED:** Use MCP tools exclusively (`mcp__plugin_projman_gitea__*`, `mcp__plugin_pr-review_gitea__*`)
+- **NO EXCEPTIONS.** Don't try CLI first. Don't fall back to CLI. MCP ONLY.
 
-**⚠️ DO NOT clear cache mid-session** - this breaks MCP tools that are already loaded.
+### NEVER PUSH DIRECTLY TO PROTECTED BRANCHES
+- **FORBIDDEN:** `git push origin development`, `git push origin main`, `git push origin master`
+- **REQUIRED:** Create feature branch → push feature branch → create PR via MCP
+- If you accidentally commit to a protected branch locally: `git checkout -b fix/branch-name` then reset the protected branch
 
-1. Run `./scripts/verify-hooks.sh` to check hook types
+### Repository Rules
-2. If changes affect MCP servers or hooks, inform the user:
-   > "Plugin changes require a session restart to take effect. Please restart Claude Code."
-3. Cache clearing is ONLY safe **before** starting a new session (not during)
 
-See `docs/DEBUGGING-CHECKLIST.md` for details on cache timing.
+| Rule | Details |
+|------|---------|
+| **File creation** | Only in allowed paths. Use `.scratch/` for temp work. Verify against `docs/CANONICAL-PATHS.md` |
+| **plugin.json location** | Must be in `.claude-plugin/` directory |
+| **Hooks** | Use `hooks/hooks.json` (auto-discovered). Never inline in plugin.json |
+| **MCP servers** | Shared at root with symlinks. Use MCP tools, never CLI (`tea`, `gh`) |
+| **Allowed root files** | `CLAUDE.md`, `README.md`, `LICENSE`, `CHANGELOG.md`, `.gitignore`, `.env.example` |
 
-**FAILURE TO FOLLOW THESE RULES = WASTED USER TIME = UNACCEPTABLE**
+**Valid hook events:** `PreToolUse`, `PostToolUse`, `UserPromptSubmit`, `SessionStart`, `SessionEnd`, `Notification`, `Stop`, `SubagentStop`, `PreCompact`
 
 ---
 
@@ -50,24 +46,24 @@ See `docs/DEBUGGING-CHECKLIST.md` for details on cache timing.
 ## Project Overview
 
 **Repository:** leo-claude-mktplace
-**Version:** 5.1.0
+**Version:** 5.4.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 |
+| `projman` | Sprint planning and project management with Gitea integration | 3.3.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 |
+| `pr-review` | Multi-agent PR review with confidence scoring | 1.1.0 |
 | `clarity-assist` | Prompt optimization with ND-friendly accommodations | 1.0.0 |
 | `doc-guardian` | Automatic documentation drift detection and synchronization | 1.0.0 |
-| `code-sentinel` | Security scanning and code refactoring tools | 1.0.0 |
+| `code-sentinel` | Security scanning and code refactoring tools | 1.0.1 |
 | `claude-config-maintainer` | CLAUDE.md optimization and maintenance | 1.0.0 |
-| `cmdb-assistant` | NetBox CMDB integration for infrastructure management | 1.0.0 |
+| `cmdb-assistant` | NetBox CMDB integration for infrastructure management | 1.2.0 |
-| `data-platform` | pandas, PostgreSQL, and dbt integration for data engineering | 1.0.0 |
+| `data-platform` | pandas, PostgreSQL, and dbt integration for data engineering | 1.1.0 |
-| `viz-platform` | DMC validation, Plotly charts, and theming for dashboards | 1.0.0 |
+| `viz-platform` | DMC validation, Plotly charts, and theming for dashboards | 1.1.0 |
-| `contract-validator` | Cross-plugin compatibility validation and agent verification | 1.0.0 |
+| `contract-validator` | Cross-plugin compatibility validation and agent verification | 1.1.0 |
 | `project-hygiene` | Post-task cleanup automation via hooks | 0.1.0 |
 
 ## Quick Start
@@ -85,16 +81,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` |
+| **PR Review** | `/pr-review`, `/pr-summary`, `/pr-findings`, `/pr-diff` |
-| **Docs** | `/doc-audit`, `/doc-sync` |
+| **Docs** | `/doc-audit`, `/doc-sync`, `/changelog-gen`, `/doc-coverage`, `/stale-docs` |
 | **Security** | `/security-scan`, `/refactor`, `/refactor-dry` |
-| **Config** | `/config-analyze`, `/config-optimize` |
+| **Config** | `/config-analyze`, `/config-optimize`, `/config-diff`, `/config-lint` |
-| **Data** | `/ingest`, `/profile`, `/schema`, `/explain`, `/lineage`, `/run` |
+| **Data** | `/ingest`, `/profile`, `/schema`, `/explain`, `/lineage`, `/lineage-viz`, `/run`, `/dbt-test`, `/data-quality` |
-| **Visualization** | `/component`, `/chart`, `/dashboard`, `/theme`, `/theme-new`, `/theme-css` |
+| **Visualization** | `/component`, `/chart`, `/chart-export`, `/dashboard`, `/theme`, `/theme-new`, `/theme-css`, `/accessibility-check`, `/breakpoints` |
-| **Validation** | `/validate-contracts`, `/check-agent`, `/list-interfaces` |
+| **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
@@ -161,40 +158,6 @@ leo-claude-mktplace/
     └── CONFIGURATION.md          # Centralized configuration guide
 ```
 
-## CRITICAL: Rules You MUST Follow
-
-### File Operations
-- **NEVER** create files in repository root unless listed in "Allowed Root Files"
-- **NEVER** modify `.gitignore` without explicit permission
-- **ALWAYS** use `.scratch/` for temporary/exploratory work
-- **ALWAYS** verify paths against `docs/CANONICAL-PATHS.md` before creating files
-
-### Plugin Development
-- **plugin.json MUST be in `.claude-plugin/` directory** (not plugin root)
-- **Every plugin MUST be listed in marketplace.json**
-- **MCP servers are SHARED at root** with symlinks from plugins
-- **MCP server venv path**: `${CLAUDE_PLUGIN_ROOT}/mcp-servers/{name}/.venv/bin/python`
-- **CLI tools forbidden** - Use MCP tools exclusively (never `tea`, `gh`, etc.)
-
-#### ⚠️ plugin.json Format Rules (CRITICAL)
-- **Hooks in separate file** - Use `hooks/hooks.json` (auto-discovered), NOT inline in plugin.json
-- **NEVER reference hooks** - Don't add `"hooks": "..."` field to plugin.json at all
-- **Agents auto-discover** - NEVER add `"agents": ["./agents/"]` - .md files found automatically
-- **Always validate** - Run `./scripts/validate-marketplace.sh` before committing
-- **Working examples:** projman, pr-review, claude-config-maintainer all use `hooks/hooks.json`
-- See lesson: `lessons/patterns/plugin-manifest-validation---hooks-and-agents-format-requirements`
-
-### Hooks (Valid Events Only)
-`PreToolUse`, `PostToolUse`, `UserPromptSubmit`, `SessionStart`, `SessionEnd`, `Notification`, `Stop`, `SubagentStop`, `PreCompact`
-
-**INVALID:** `task-completed`, `file-changed`, `git-commit-msg-needed`
-
-### Allowed Root Files
-`CLAUDE.md`, `README.md`, `LICENSE`, `CHANGELOG.md`, `.gitignore`, `.env.example`
-
-### Allowed Root Directories
-`.claude/`, `.claude-plugin/`, `.claude-plugins/`, `.scratch/`, `docs/`, `hooks/`, `mcp-servers/`, `plugins/`, `scripts/`
-
 ## Architecture
 
 ### Four-Agent Model (projman)
@@ -227,6 +190,21 @@ leo-claude-mktplace/
 
 **Note:** `GITEA_ORG` is at project level since different projects may belong to different organizations.
 
+### Agent Model Configuration
+
+Agents can specify preferred Claude models for cost/performance optimization:
+
+| Model | Use For | Agents |
+|-------|---------|--------|
+| `opus` | Complex reasoning, security | planner, code-reviewer, security-reviewer |
+| `sonnet` | Implementation, coordination | orchestrator, executor, most agents |
+| `haiku` | Simple validation | component-check, agent-check |
+
+**Configuration:** Add `model: opus|sonnet|haiku` to agent frontmatter, or `defaultModel` to plugin.json.
+**Inheritance:** Agent → Plugin default → System default (sonnet)
+
+See `docs/MODEL-RECOMMENDATIONS.md` for detailed guidance.
+
 ### Branch-Aware Security
 
 | Branch Pattern | Mode | Capabilities |
@@ -376,4 +354,4 @@ The script will:
 
 ---
 
-**Last Updated:** 2026-01-24
+**Last Updated:** 2026-01-28

README.md

@@ -1,4 +1,4 @@
-# Leo Claude Marketplace - v5.2.0
+# Leo Claude Marketplace - v5.4.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*

docs/CONFIGURATION.md

@@ -522,6 +522,56 @@ cat .env
 
 ---
 
+## Agent Model Configuration
+
+Agents can specify which Claude model to use for optimal cost/performance.
+
+### Model Options
+
+| Model | Use For | Cost |
+|-------|---------|------|
+| `opus` | Complex reasoning, security analysis | Highest |
+| `sonnet` | Implementation, coordination (default) | Medium |
+| `haiku` | Simple validation, quick checks | Lowest |
+
+### Configuration Levels
+
+**1. Agent-Level (highest priority)**
+
+Add to agent frontmatter in `agents/*.md`:
+
+```yaml
+---
+name: planner
+description: Sprint planning agent
+model: opus
+---
+```
+
+**2. Plugin-Level (fallback)**
+
+Add to `plugin.json`:
+
+```json
+{
+  "defaultModel": "sonnet"
+}
+```
+
+**3. System Default**
+
+If neither is specified, agents use `sonnet`.
+
+### Inheritance Chain
+
+```
+Agent model → Plugin defaultModel → System default (sonnet)
+```
+
+See [Model Recommendations](MODEL-RECOMMENDATIONS.md) for detailed guidance on model selection by task type.
+
+---
+
 ## Security Best Practices
 
 1. **Never commit tokens**

docs/MODEL-RECOMMENDATIONS.md

@@ -0,0 +1,149 @@
+# Model Recommendations
+
+Guidelines for selecting Claude models (opus, sonnet, haiku) for plugin agents.
+
+---
+
+## Model Overview
+
+| Model | Best For | Cost | Speed |
+|-------|----------|------|-------|
+| **Opus** | Complex reasoning, architecture decisions, security analysis | Highest | Slower |
+| **Sonnet** | Implementation, coordination, standard tasks | Medium | Balanced |
+| **Haiku** | Simple validation, quick checks, status queries | Lowest | Fastest |
+
+---
+
+## Task-Type Recommendations
+
+| Task Type | Model | Rationale |
+|-----------|-------|-----------|
+| Architecture decisions | Opus | Requires deep reasoning, trade-off analysis |
+| Security analysis | Opus | Critical thinking, vulnerability pattern recognition |
+| Code review (quality) | Opus | Thorough analysis, edge case detection |
+| Sprint planning | Opus | Strategic thinking, dependency analysis |
+| Complex data analysis | Opus | Multi-step reasoning, insight generation |
+| Code implementation | Sonnet | Fast, capable code generation |
+| Coordination/dispatch | Sonnet | Task management, status tracking |
+| Data transformation | Sonnet | ETL operations, query building |
+| Documentation | Sonnet | Clear writing, structure |
+| Simple validation | Haiku | Fast prop checks, schema validation |
+| Status checks | Haiku | Quick queries, cost-effective |
+| Quick verification | Haiku | Simple pass/fail checks |
+
+---
+
+## Agent Model Assignments
+
+### projman (Sprint Management)
+
+| Agent | Model | Rationale |
+|-------|-------|-----------|
+| `planner` | opus | Architecture decisions, issue structuring |
+| `orchestrator` | sonnet | Coordination, parallel execution |
+| `executor` | sonnet | Code implementation |
+| `code-reviewer` | opus | Quality review, security analysis |
+
+### pr-review (PR Analysis)
+
+| Agent | Model | Rationale |
+|-------|-------|-----------|
+| `coordinator` | sonnet | Task dispatch, result aggregation |
+| `security-reviewer` | opus | Security vulnerability detection |
+| `performance-analyst` | sonnet | Pattern recognition |
+| `maintainability-auditor` | sonnet | Code quality checks |
+| `test-validator` | sonnet | Test coverage analysis |
+
+### code-sentinel (Security & Refactoring)
+
+| Agent | Model | Rationale |
+|-------|-------|-----------|
+| `security-reviewer` | opus | Security scanning |
+| `refactor-advisor` | sonnet | Refactoring suggestions |
+
+### data-platform (Data Engineering)
+
+| Agent | Model | Rationale |
+|-------|-------|-----------|
+| `data-analysis` | opus | Complex data insights |
+| `data-ingestion` | sonnet | ETL operations |
+
+### viz-platform (Visualization)
+
+| Agent | Model | Rationale |
+|-------|-------|-----------|
+| `component-check` | haiku | Simple prop validation |
+| `layout-builder` | sonnet | UI construction |
+| `theme-setup` | sonnet | Design configuration |
+
+### contract-validator (Compatibility)
+
+| Agent | Model | Rationale |
+|-------|-------|-----------|
+| `full-validation` | sonnet | Contract checking |
+| `agent-check` | haiku | Quick verification |
+
+---
+
+## Configuration Schema
+
+### Agent-Level (Frontmatter)
+
+Add `model` field to agent YAML frontmatter:
+
+```yaml
+---
+name: planner
+description: Sprint planning agent
+model: opus
+---
+```
+
+**Valid values:** `opus`, `sonnet`, `haiku`
+
+### Plugin-Level (plugin.json)
+
+Add `defaultModel` for plugin-wide fallback:
+
+```json
+{
+  "name": "projman",
+  "version": "3.4.0",
+  "defaultModel": "sonnet"
+}
+```
+
+---
+
+## Inheritance Chain
+
+Model selection follows this precedence:
+
+```
+1. Agent model field (highest priority)
+      ↓ if not specified
+2. Plugin defaultModel (plugin.json)
+      ↓ if not specified
+3. System default: sonnet
+```
+
+**Example:**
+- Agent has `model: opus` → Uses opus
+- Agent has no model, plugin has `defaultModel: sonnet` → Uses sonnet
+- Neither specified → Uses sonnet (system default)
+
+---
+
+## Cost Optimization Tips
+
+1. **Default to Sonnet** - Good balance for most tasks
+2. **Reserve Opus** for critical decisions (security, architecture)
+3. **Use Haiku** for validation and quick checks
+4. **Batch simple tasks** - Use haiku for parallel validation
+
+---
+
+## See Also
+
+- [Configuration Guide](CONFIGURATION.md) - Full configuration reference
+- [Plugin Development](../README.md) - Adding new plugins

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/.claude-plugin/plugin.json

@@ -1,7 +1,8 @@
 {
   "name": "code-sentinel",
   "description": "Security scanning and code refactoring tools",
-  "version": "1.0.0",
+  "version": "1.0.1",
+  "defaultModel": "sonnet",
   "author": {
     "name": "Leo Miranda",
     "email": "leobmiranda@gmail.com"

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

@@ -1,11 +1,23 @@
 ---
+name: security-reviewer
 description: Security-focused code review agent
+model: opus
 ---
 
 # Security Reviewer 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/.claude-plugin/plugin.json

@@ -1,6 +1,7 @@
 {
   "name": "contract-validator",
-  "version": "1.0.0",
+  "version": "1.1.0",
+  "defaultModel": "sonnet",
   "description": "Cross-plugin compatibility validation and Claude.md agent verification",
   "author": {
     "name": "Leo Miranda",

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

@@ -1,7 +1,23 @@
+---
+name: agent-check
+description: Agent definition validator for quick verification
+model: haiku
+---
+
 # Agent Check Agent
 
 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/.claude-plugin/plugin.json

@@ -1,6 +1,7 @@
 {
   "name": "data-platform",
-  "version": "1.0.0",
+  "version": "1.1.0",
+  "defaultModel": "sonnet",
   "description": "Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration",
   "author": {
     "name": "Leo Miranda",

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

@@ -1,7 +1,23 @@
+---
+name: data-analysis
+description: Data analysis specialist for exploration and profiling
+model: opus
+---
+
 # Data Analysis Agent
 
 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**
@@ -40,7 +52,13 @@ Apply all pending documentation updates detected by doc-guardian hooks.
    - Single commit: `docs: sync documentation with code changes`
    - Include summary of what was updated in commit body
 
-5. **Output**
+5. **Clear Queue**
+   After successful sync, clear the queue file:
+   ```bash
+   echo "# Doc Guardian Queue - cleared after sync on $(date +%Y-%m-%d)" > .doc-guardian-queue
+   ```
+
+6. **Output**
 ```
 ## Documentation Sync Complete
 

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/doc-guardian/hooks/notify.sh

@@ -2,6 +2,10 @@
 # doc-guardian notification hook
 # Tracks documentation dependencies and queues updates
 # This is a command hook - guaranteed not to block workflow
+#
+# IMPORTANT: Output is purely informational - uses passive language
+# to avoid triggering Claude to seek user confirmation.
+# Run /doc-sync to process the queue when ready.
 
 # Read tool input from stdin (JSON with file_path)
 INPUT=$(cat)
@@ -44,6 +48,30 @@ DEPENDENT_DOCS="${DOC_DEPS[$MODIFIED_TYPE]}"
 # Queue file for tracking pending updates
 QUEUE_FILE="${CLAUDE_PROJECT_ROOT:-.}/.doc-guardian-queue"
 
+# Debounce: skip notification if same type was logged in last 5 seconds
+# This prevents 4+ rapid notifications during batch edits
+DEBOUNCE_SECONDS=5
+if [ -f "$QUEUE_FILE" ]; then
+    LAST_ENTRY=$(tail -1 "$QUEUE_FILE" 2>/dev/null || true)
+    LAST_TYPE=$(echo "$LAST_ENTRY" | cut -d'|' -f2 | tr -d ' ')
+    LAST_TIME=$(echo "$LAST_ENTRY" | cut -d'|' -f1 | tr -d ' ')
+
+    if [ "$LAST_TYPE" = "$MODIFIED_TYPE" ] && [ -n "$LAST_TIME" ]; then
+        # Convert timestamps to seconds for comparison
+        LAST_EPOCH=$(date -d "$LAST_TIME" +%s 2>/dev/null || echo "0")
+        NOW_EPOCH=$(date +%s)
+        DIFF=$((NOW_EPOCH - LAST_EPOCH))
+
+        if [ "$DIFF" -lt "$DEBOUNCE_SECONDS" ]; then
+            # Still add to queue, but skip notification
+            {
+                echo "$(date +%Y-%m-%dT%H:%M:%S) | $MODIFIED_TYPE | $FILE_PATH | $DEPENDENT_DOCS"
+            } >> "$QUEUE_FILE" 2>/dev/null || true
+            exit 0
+        fi
+    fi
+fi
+
 # Add to queue (create if doesn't exist, append if does)
 {
     echo "$(date +%Y-%m-%dT%H:%M:%S) | $MODIFIED_TYPE | $FILE_PATH | $DEPENDENT_DOCS"
@@ -52,7 +80,8 @@ QUEUE_FILE="${CLAUDE_PROJECT_ROOT:-.}/.doc-guardian-queue"
 # Count pending updates
 PENDING_COUNT=$(wc -l < "$QUEUE_FILE" 2>/dev/null | tr -d ' ' || echo "1")
 
-# Output notification with specific docs that need updating
+# Output passive notification (no action implied)
-echo "[doc-guardian] $MODIFIED_TYPE changed → update needed: $DEPENDENT_DOCS (${PENDING_COUNT} pending)"
+# Uses "queued" instead of "update needed" to avoid triggering Claude to ask about it
+echo "[doc-guardian] drift queued: $MODIFIED_TYPE → $DEPENDENT_DOCS ($PENDING_COUNT total)"
 
 exit 0

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/git-flow/hooks/hooks.json

@@ -1,19 +1,16 @@
 {
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Bash",
   "hooks": [
     {
+      "event": "PreToolUse",
+      "matcher": "Bash",
       "type": "command",
       "command": "${CLAUDE_PLUGIN_ROOT}/hooks/branch-check.sh"
     },
     {
+      "event": "PreToolUse",
+      "matcher": "Bash",
       "type": "command",
       "command": "${CLAUDE_PLUGIN_ROOT}/hooks/commit-msg-check.sh"
     }
   ]
 }
-    ]
-  }
-}

plugins/pr-review/.claude-plugin/plugin.json

@@ -1,6 +1,7 @@
 {
   "name": "pr-review",
-  "version": "1.0.0",
+  "version": "1.1.0",
+  "defaultModel": "sonnet",
   "description": "Multi-agent pull request review with confidence scoring and actionable feedback",
   "author": {
     "name": "Leo Miranda",

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,21 @@
+---
+name: security-reviewer
+description: Security-focused code reviewer for PR analysis
+model: opus
+---
+
 # 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/.claude-plugin/plugin.json

@@ -1,6 +1,7 @@
 {
   "name": "projman",
-  "version": "3.2.0",
+  "version": "3.3.0",
+  "defaultModel": "sonnet",
   "description": "Sprint planning and project management with Gitea integration",
   "author": {
     "name": "Leo Miranda",

plugins/projman/agents/code-reviewer.md

@@ -1,12 +1,42 @@
 ---
 name: code-reviewer
 description: Specialized agent for pre-sprint code quality review
+model: opus
 ---
 
 # Code Reviewer Agent
 
 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

@@ -1,6 +1,7 @@
 ---
 name: planner
 description: Sprint planning agent - thoughtful architecture analysis and issue creation
+model: opus
 ---
 
 # Sprint Planner Agent
@@ -36,6 +37,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

@@ -385,6 +385,13 @@ git push -u origin fix/issue-[NUMBER]-[brief-description]
 git checkout development
 ```
 
+**⚠️ IMPORTANT: Issue will NOT auto-close**
+
+PRs merged to `development` do NOT trigger Gitea's auto-close feature.
+Auto-close only works when merging to the default branch (`main`).
+
+You MUST manually close the issue in Step 15 after the PR is merged.
+
 5. Add comment to original issue:
 ```
 mcp__plugin_projman_gitea__add_comment(
@@ -417,9 +424,14 @@ Next Steps:
 
 **This step runs AFTER the user has verified the fix works.**
 
+**⚠️ MANDATORY: You MUST manually close the issue.**
+
+PRs merged to `development` do NOT auto-close issues (Gitea only auto-closes
+on merges to the default branch `main`). Always close manually after merge.
+
 When user returns and confirms the fix is working:
 
-**1. Close the issue:**
+**1. Close the issue (REQUIRED - won't auto-close):**
 
 ```
 mcp__plugin_projman_gitea__update_issue(
@@ -572,3 +584,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.