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

13
plugins/projman/commands/debug-report.md
View File

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

13
plugins/projman/commands/debug-review.md
View File

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

14
plugins/projman/commands/initial-setup.md
View File

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

13
plugins/projman/commands/labels-sync.md
View File

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

14
plugins/projman/commands/project-init.md
View File

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

14
plugins/projman/commands/project-sync.md
View File

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

13
plugins/projman/commands/proposal-status.md
View File

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

14
plugins/projman/commands/review.md
View File

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

16
plugins/projman/commands/sprint-close.md
View File

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

13
plugins/projman/commands/sprint-diagram.md
View File

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

14
plugins/projman/commands/sprint-plan.md
View File

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

16
plugins/projman/commands/sprint-start.md
View File

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

22
plugins/projman/commands/sprint-status.md
View File

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

13
plugins/projman/commands/suggest-version.md
View File

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

14
plugins/projman/commands/test-check.md
View File

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

13
plugins/projman/commands/test-gen.md
View File

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