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

Reviewed-on: #289

.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Project management plugins with Gitea and NetBox integrations",
-    "version": "5.2.0"
+    "version": "5.3.0"
   },
   "plugins": [
     {

CHANGELOG.md

@@ -4,6 +4,53 @@ 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.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

@@ -50,7 +50,7 @@ See `docs/DEBUGGING-CHECKLIST.md` for details on cache timing.
 ## Project Overview
 
 **Repository:** leo-claude-mktplace
-**Version:** 5.2.0
+**Version:** 5.3.0
 **Status:** Production Ready
 
 A plugin marketplace for Claude Code containing:
@@ -377,4 +377,4 @@ The script will:
 
 ---
 
-**Last Updated:** 2026-01-24
+**Last Updated:** 2026-01-28

README.md

@@ -1,4 +1,4 @@
-# Leo Claude Marketplace - v5.2.0
+# Leo Claude Marketplace - v5.3.0
 
 A collection of Claude Code plugins for project management, infrastructure automation, and development workflows.
 

plugins/projman/agents/code-reviewer.md

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

plugins/projman/agents/executor.md

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

plugins/projman/agents/orchestrator.md

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

plugins/projman/agents/planner.md

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

plugins/projman/commands/debug-report.md

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

plugins/projman/commands/debug-review.md

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

plugins/projman/commands/initial-setup.md

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

plugins/projman/commands/labels-sync.md

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

plugins/projman/commands/project-init.md

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

plugins/projman/commands/project-sync.md

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

plugins/projman/commands/proposal-status.md

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

plugins/projman/commands/review.md

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

plugins/projman/commands/sprint-close.md

@@ -284,6 +284,22 @@ Would you like me to handle git operations?
 [Y/n]
 ```
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🏁 CLOSING                                                      ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name.
+
+Then proceed with the sprint close workflow.
+
 ## Getting Started
 
 Simply run `/sprint-close` when your sprint is complete. The orchestrator will guide you through:

plugins/projman/commands/sprint-diagram.md

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

plugins/projman/commands/sprint-plan.md

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

plugins/projman/commands/sprint-start.md

@@ -410,6 +410,22 @@ Executors save checkpoints after major steps:
 - [ ] Step 4
 ```
 
+## Visual Output
+
+When executing this command, display the plugin header:
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  ⚡ EXECUTION                                                    ║
+║  [Sprint Name]                                                   ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name from Gitea.
+
+Then proceed with the command workflow.
+
 ## Getting Started
 
 Simply invoke `/sprint-start` and the orchestrator will:

plugins/projman/commands/sprint-status.md

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

plugins/projman/commands/suggest-version.md

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

plugins/projman/commands/test-check.md

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

plugins/projman/commands/test-gen.md

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