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

feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]

Browse Source 
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Leo Miranda
2026-02-06 14:52:11 -05:00
parent 5098422858
commit 2d51df7a42
321 changed files with 13582 additions and 1019 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
plugins/projman/skills/branch-security.md
View File

@@ -14,7 +14,7 @@ Defines branch detection, classification, and branch-aware authorization rules.
- **Planner agent**: Before planning any sprint work
- **Orchestrator agent**: Before executing any sprint tasks
- **Executor agent**: Before modifying any files
- **Commands**: `/sprint-plan`, `/sprint-start`, `/sprint-close`
- **Commands**: `/sprint plan`, `/sprint start`, `/sprint close`
---

2
plugins/projman/skills/dependency-management.md
View File

@@ -12,7 +12,7 @@ Defines how to analyze dependencies, plan parallel execution, and prevent file c
## When to Use
- **Orchestrator agent**: When starting sprint execution
- **Commands**: `/sprint-start`, `/sprint-diagram`
- **Commands**: `/sprint start`, `/sprint-diagram`
---

2
plugins/projman/skills/git-workflow.md
View File

@@ -13,7 +13,7 @@ Defines branch naming conventions, merge protocols, and git operations.
- **Orchestrator agent**: When coordinating git operations
- **Executor agent**: When creating branches and commits
- **Commands**: `/sprint-start`, `/sprint-close`
- **Commands**: `/sprint start`, `/sprint close`
---

2
plugins/projman/skills/input-detection.md
View File

@@ -12,7 +12,7 @@ Defines how to detect where planning input is coming from and how to handle each
## When to Use
- **Planner agent**: At start of sprint planning
- **Commands**: `/sprint-plan`
- **Commands**: `/sprint plan`
---

2
plugins/projman/skills/issue-conventions.md
View File

@@ -12,7 +12,7 @@ Defines standard formats for issue titles, bodies, and wiki references.
## When to Use
- **Planner agent**: When creating issues during sprint planning
- **Commands**: `/sprint-plan`
- **Commands**: `/sprint plan`
---

10
plugins/projman/skills/label-taxonomy/labels-reference.md
View File

@@ -317,21 +317,21 @@ Most issues should have multiple labels from different categories:
This skill is loaded when agents need to suggest labels:
**In /sprint-plan:**
**In /sprint plan:**
The planner agent uses this reference along with `suggest_labels` MCP tool to recommend appropriate labels for newly created issues.
**In /labels-sync:**
**In /labels sync:**
The command updates this file with the latest taxonomy from Gitea.
## Keeping This Updated
**IMPORTANT:** Run `/labels-sync` to:
**IMPORTANT:** Run `/labels sync` to:
1. Fetch actual labels from Gitea
2. Update this reference file
3. Ensure suggestion logic matches current taxonomy
**Update frequency:**
- First time setup: Run `/labels-sync` immediately
- First time setup: Run `/labels sync` immediately
- Regular updates: Monthly or when taxonomy changes
- Team notification: When new labels are added to Gitea
@@ -341,6 +341,6 @@ The command updates this file with the latest taxonomy from Gitea.
1. Fetch labels dynamically using `get_labels` MCP tool
2. Use `suggest_labels` for intelligent suggestions
3. Reference this skill for context and patterns
4. Update this file via `/labels-sync` when taxonomy changes
4. Update this file via `/labels sync` when taxonomy changes
This ensures the plugin adapts to taxonomy evolution without code changes.

2
plugins/projman/skills/lessons-learned.md
View File

@@ -13,7 +13,7 @@ Defines the workflow for capturing lessons at sprint close and searching them at
- **Planner agent**: Search lessons at sprint start
- **Orchestrator agent**: Capture lessons at sprint close
- **Commands**: `/sprint-plan`, `/sprint-start`, `/sprint-close`
- **Commands**: `/sprint plan`, `/sprint start`, `/sprint close`
---

4
plugins/projman/skills/planning-workflow.md
View File

@@ -11,8 +11,8 @@ Defines the complete 11-step planning workflow from validation through approval.
## When to Use
- **Planner agent**: When executing `/sprint-plan`
- **Commands**: `/sprint-plan`
- **Planner agent**: When executing `/sprint plan`
- **Commands**: `/sprint plan`
---

2
plugins/projman/skills/progress-tracking.md
View File

@@ -13,7 +13,7 @@ Defines structured progress comment format and status label management.
- **Orchestrator agent**: When tracking sprint execution
- **Executor agent**: When posting progress updates
- **Commands**: `/sprint-start`, `/sprint-status`
- **Commands**: `/sprint start`, `/sprint status`
---

2
plugins/projman/skills/repo-validation.md
View File

@@ -12,7 +12,7 @@ Validates that the repository belongs to an organization and has the required la
## When to Use
- **Planner agent**: At start of sprint planning
- **Commands**: `/sprint-plan`, `/labels-sync`, `/project-init`
- **Commands**: `/sprint plan`, `/labels sync`, `/pr init`
---

2
plugins/projman/skills/review-checklist.md
View File

@@ -12,7 +12,7 @@ Defines code review criteria, severity classification, and output format.
## When to Use
- **Code Reviewer agent**: During pre-sprint-close review
- **Commands**: `/pm-review`
- **Commands**: `/sprint review`
---

2
plugins/projman/skills/rfc-templates.md
View File

@@ -369,7 +369,7 @@ For rapid RFC creation from conversation:
## Creating RFC from Clarified Spec
When `/clarify` provides a clarified specification, map sections:
When `/clarity clarify` provides a clarified specification, map sections:
| Clarify Output | RFC Section |
|----------------|-------------|

10
plugins/projman/skills/rfc-workflow.md
View File

@@ -13,7 +13,7 @@ Defines the Request for Comments (RFC) system for capturing, reviewing, and trac
- **Planner agent**: When detecting approved RFCs for sprint planning
- **Commands**: `/rfc create`, `/rfc list`, `/rfc review`, `/rfc approve`, `/rfc reject`
- **Integration**: With `/sprint-plan` to select approved RFCs for implementation
- **Integration**: With `/sprint plan` to select approved RFCs for implementation
---
@@ -78,12 +78,12 @@ Defines the Request for Comments (RFC) system for capturing, reviewing, and trac
- **Action**: Update status, add Decision section with rejection reason
### Approved → Implementing
- **Who can transition**: Planner agent via `/sprint-plan`
- **Who can transition**: Planner agent via `/sprint plan`
- **Requirements**: RFC selected for sprint
- **Action**: Update status, add Sprint reference, update RFC-Index
### Implementing → Implemented
- **Who can transition**: Orchestrator agent via `/sprint-close`
- **Who can transition**: Orchestrator agent via `/sprint close`
- **Requirements**: Sprint completed successfully
- **Action**: Update status, add completion date, link to lessons learned
@@ -303,6 +303,6 @@ When RFC status changes:
| `/rfc review` | Transitions Draft -> Review |
| `/rfc approve` | Transitions Review -> Approved |
| `/rfc reject` | Transitions Review/Draft -> Rejected |
| `/sprint-plan` | Detects Approved RFCs, transitions to Implementing |
| `/sprint-close` | Transitions Implementing -> Implemented |
| `/sprint plan` | Detects Approved RFCs, transitions to Implementing |
| `/sprint close` | Transitions Implementing -> Implemented |
| `clarity-assist` | Suggests `/rfc create` for feature ideas |

2
plugins/projman/skills/risk-register.md
View File

@@ -55,4 +55,4 @@ Page name: `Risk-Register: {Name}` (e.g., `Risk-Register: Driving School SaaS`)
- `/project plan` creates initial risk register
- `/project status` summarizes open risk count and top-3 by score
- `/sprint-close` updates risk statuses in lessons learned
- `/sprint close` updates risk statuses in lessons learned

2
plugins/projman/skills/setup-workflows.md
View File

@@ -1,6 +1,6 @@
# Setup Workflows
Shared workflows for the `/pm-setup` command modes.
Shared workflows for the `/projman setup` command modes.
## Mode Detection Logic

8
plugins/projman/skills/sprint-approval.md
View File

@@ -13,7 +13,7 @@ Defines the approval workflow that gates sprint execution.
- **Planner agent**: After creating issues, request approval
- **Orchestrator agent**: Before execution, verify approval exists
- **Commands**: `/sprint-plan`, `/sprint-start`
- **Commands**: `/sprint plan`, `/sprint start`
---
@@ -89,11 +89,11 @@ get_milestone(repo="org/repo", milestone_id=17)
Sprint 17 milestone does not contain an approval record.
Execution cannot proceed without approval.
Required: Run /sprint-plan first to:
Required: Run /sprint plan first to:
1. Review the sprint scope
2. Get explicit approval for execution
To override (emergency only): /sprint-start --force
To override (emergency only): /sprint start --force
This bypasses the approval gate and logs a warning to the milestone.
```
@@ -125,7 +125,7 @@ Task #48 wants to create: feat/48-api-docs
→ STOP and ask user to approve expanded scope
```
**Operations outside scope should trigger re-approval via `/sprint-plan`.**
**Operations outside scope should trigger re-approval via `/sprint plan`.**
---

22
plugins/projman/skills/sprint-lifecycle.md
View File

@@ -20,17 +20,17 @@ Defines the valid sprint lifecycle states and transitions, enforced via labels o
```
idle -> Sprint/Planning -> Sprint/Executing -> Sprint/Reviewing -> idle
(sprint-plan) (sprint-start) (pm-review) (sprint-close)
(sprint plan) (sprint start) (sprint review) (sprint close)
```
## State Labels
| Label | Set By | Meaning |
|-------|--------|---------|
| *(no Sprint/* label)* | `/sprint-close` or initial state | Idle - no active sprint phase |
| `Sprint/Planning` | `/sprint-plan` | Planning in progress |
| `Sprint/Executing` | `/sprint-start` | Execution in progress |
| `Sprint/Reviewing` | `/pm-review` | Code review in progress |
| *(no Sprint/* label)* | `/sprint close` or initial state | Idle - no active sprint phase |
| `Sprint/Planning` | `/sprint plan` | Planning in progress |
| `Sprint/Executing` | `/sprint start` | Execution in progress |
| `Sprint/Reviewing` | `/sprint review` | Code review in progress |
**Rule:** Only ONE `Sprint/*` label may exist on a milestone at a time. Setting a new one removes the previous one.
@@ -40,11 +40,11 @@ idle -> Sprint/Planning -> Sprint/Executing -> Sprint/Reviewing -> idle
| Command | Expected State | Sets State | On Wrong State |
|---------|---------------|------------|----------------|
| `/sprint-plan` | idle (no Sprint/* label) | `Sprint/Planning` | Warn: "Sprint is in [state]. Run `/sprint-close` first or use `--force` to re-plan." Allow with `--force`. |
| `/sprint-start` | `Sprint/Planning` | `Sprint/Executing` | Warn: "Expected Sprint/Planning state but found [state]. Run `/sprint-plan` first or use `--force`." Allow with `--force`. |
| `/pm-review` | `Sprint/Executing` | `Sprint/Reviewing` | Warn: "Expected Sprint/Executing state but found [state]." Allow with `--force`. |
| `/sprint-close` | `Sprint/Reviewing` | Remove all Sprint/* labels (idle) | Warn: "Expected Sprint/Reviewing state but found [state]. Run `/pm-review` first or use `--force`." Allow with `--force`. |
| `/sprint-status` | Any | No change (read-only) | Display current state in output. |
| `/sprint plan` | idle (no Sprint/* label) | `Sprint/Planning` | Warn: "Sprint is in [state]. Run `/sprint close` first or use `--force` to re-plan." Allow with `--force`. |
| `/sprint start` | `Sprint/Planning` | `Sprint/Executing` | Warn: "Expected Sprint/Planning state but found [state]. Run `/sprint plan` first or use `--force`." Allow with `--force`. |
| `/sprint review` | `Sprint/Executing` | `Sprint/Reviewing` | Warn: "Expected Sprint/Executing state but found [state]." Allow with `--force`. |
| `/sprint close` | `Sprint/Reviewing` | Remove all Sprint/* labels (idle) | Warn: "Expected Sprint/Reviewing state but found [state]. Run `/sprint review` first or use `--force`." Allow with `--force`. |
| `/sprint status` | Any | No change (read-only) | Display current state in output. |
---
@@ -86,7 +86,7 @@ After command completes successfully:
## Displaying State
In `/sprint-status` output, include:
In `/sprint status` output, include:
```
Sprint Phase: Executing (since 2026-02-01)

4
plugins/projman/skills/sprint-roadmap.md
View File

@@ -36,6 +36,6 @@ Page name: `Roadmap: {Name}` (e.g., `Roadmap: Driving School SaaS`)
## Integration
- `/project plan` creates the initial roadmap from epic decomposition + dependency analysis
- `/sprint-plan` references the roadmap to determine sprint scope
- `/sprint-close` updates sprint status in roadmap
- `/sprint plan` references the roadmap to determine sprint scope
- `/sprint close` updates sprint status in roadmap
- `/project status` shows roadmap progress

14
plugins/projman/skills/token-budget-report.md
View File

@@ -10,9 +10,9 @@ Provides directional token consumption estimates at sprint workflow boundaries.
## When to Display
- End of `/sprint-plan` (after all issues created)
- End of `/sprint-close` (after lessons captured)
- On explicit request: `/sprint-status --tokens`
- End of `/sprint plan` (after all issues created)
- End of `/sprint close` (after lessons captured)
- On explicit request: `/sprint status --tokens`
---
@@ -36,10 +36,10 @@ These are loaded once at session start. Update this table if MCP servers change.
| Phase | Typical Skills Loaded | Est. Tokens |
|-------|----------------------|-------------|
| Planning (`/sprint-plan`) | mcp-tools-reference, label-taxonomy, sprint-planning, architecture-analysis, rfc-workflow | ~3,000–5,000 |
| Execution (`/sprint-start`) | mcp-tools-reference, branch-security, plan-then-batch | ~2,000–3,000 |
| Review (`/pm-review`) | mcp-tools-reference, review-checklist | ~1,500–2,500 |
| Close (`/sprint-close`) | mcp-tools-reference, sprint-lifecycle, lessons-learned | ~2,000–3,000 |
| Planning (`/sprint plan`) | mcp-tools-reference, label-taxonomy, sprint-planning, architecture-analysis, rfc-workflow | ~3,000–5,000 |
| Execution (`/sprint start`) | mcp-tools-reference, branch-security, plan-then-batch | ~2,000–3,000 |
| Review (`/sprint review`) | mcp-tools-reference, review-checklist | ~1,500–2,500 |
| Close (`/sprint close`) | mcp-tools-reference, sprint-lifecycle, lessons-learned | ~2,000–3,000 |
To get actual numbers: count characters in each skill file loaded during the phase, divide by 4.

8
plugins/projman/skills/visual-output.md
View File

@@ -40,10 +40,10 @@ For commands that don't invoke a specific agent phase:
| Command | Phase Emoji | Phase Name |
|---------|-------------|------------|
| `/sprint-status` | 📊 Chart | STATUS |
| `/pm-setup` | ⚙️ Gear | SETUP |
| `/labels-sync` | 🏷️ Label | LABELS |
| `/pm-test` | 🧪 Flask | TEST |
| `/sprint status` | 📊 Chart | STATUS |
| `/projman setup` | ⚙️ Gear | SETUP |
| `/labels sync` | 🏷️ Label | LABELS |
| `/sprint test` | 🧪 Flask | TEST |
| `/rfc` | 📄 Document | RFC [Sub-Command] |
| `/project` | 📋 Clipboard | PROJECT [Sub-Command] |
| `/adr` | 📐 Ruler | ADR [Sub-Command] |

8
plugins/projman/skills/wbs.md
View File

@@ -6,7 +6,7 @@ description: Work Breakdown Structure skill for decomposing projects and sprints
## Purpose
Bridges project-level epics and sprint-level issues. Used by `/project plan` to create the initial decomposition and by `/sprint-plan` to refine sprint scope.
Bridges project-level epics and sprint-level issues. Used by `/project plan` to create the initial decomposition and by `/sprint plan` to refine sprint scope.
## Wiki Page
@@ -31,7 +31,7 @@ Page name: `WBS: {Name}` (e.g., `WBS: Driving School SaaS`)
## Sprint Refinement
During `/sprint-plan`, the planner:
During `/sprint plan`, the planner:
1. Loads the WBS
2. Identifies the next unstarted work packages
3. Creates issues from Level 3 tasks
@@ -40,6 +40,6 @@ During `/sprint-plan`, the planner:
## Integration
- `/project plan` creates the initial WBS from epic decomposition
- `/sprint-plan` consumes WBS work packages to create sprint issues
- `/sprint-close` updates WBS with completion status
- `/sprint plan` consumes WBS work packages to create sprint issues
- `/sprint close` updates WBS with completion status
- `/project status` aggregates WBS progress for project-level view

2
plugins/projman/skills/wiki-conventions.md
View File

@@ -12,7 +12,7 @@ Defines naming conventions, dependency headers, and structure for all wiki pages
- **Planner agent**: When creating wiki pages during planning
- **Orchestrator agent**: When updating status at sprint close
- **Commands**: `/sprint-plan`, `/sprint-close`, `/project initiation`, `/project plan`, `/project status`, `/project close`, `/adr create`
- **Commands**: `/sprint plan`, `/sprint close`, `/project initiation`, `/project plan`, `/project status`, `/project close`, `/adr create`
---