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

feat(projman): add visual output requirements to agents and commands

Browse Source 
Add Visual Output sections to all projman files:
- 4 agent files with phase-specific headers (PLANNING, EXECUTION, CLOSING)
- 16 command files with appropriate headers

Headers use double-line box characters for projman branding:
- Planning phase: TARGET PLANNING
- Execution phase: LIGHTNING EXECUTION (+ progress block for orchestrator)
- Closing phase: FLAG CLOSING
- Setup commands: GEAR SETUP

Closes #273, #274

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Leo Miranda
2026-01-28 17:10:49 -05:00
parent d27c440631
commit 3561025dfc
20 changed files with 373 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
plugins/projman/agents/code-reviewer.md
View File

@@ -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

32
plugins/projman/agents/executor.md
View File

@@ -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:**

51
plugins/projman/agents/orchestrator.md
View File

@@ -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:**

32
plugins/projman/agents/planner.md
View File

@@ -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:**