feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]
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:
@@ -1,4 +1,5 @@
|
||||
---
|
||||
name: labels sync
|
||||
description: Fetch and validate label taxonomy from Gitea, create missing required labels
|
||||
---
|
||||
|
||||
@@ -16,7 +17,7 @@ Fetch current label taxonomy from Gitea, validate required labels exist, and cre
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/labels-sync` when setting up the plugin or after taxonomy updates.
|
||||
Run `/labels sync` when setting up the plugin or after taxonomy updates.
|
||||
|
||||
## Workflow
|
||||
|
||||
|
||||
13
plugins/projman/commands/labels.md
Normal file
13
plugins/projman/commands/labels.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: Label management
|
||||
---
|
||||
|
||||
# /labels
|
||||
|
||||
Label management for projman.
|
||||
|
||||
## Sub-commands
|
||||
|
||||
| Sub-command | Description |
|
||||
|-------------|-------------|
|
||||
| `/labels sync` | Sync label taxonomy to Gitea repository |
|
||||
@@ -46,7 +46,7 @@ Show the charter to the user. Wait for approval before proceeding to `/project p
|
||||
|
||||
## DO NOT
|
||||
|
||||
- Create sprint issues — that's `/sprint-plan`
|
||||
- Create sprint issues — that's `/sprint plan`
|
||||
- Create WBS or roadmap — that's `/project plan`
|
||||
- Make architecture decisions — suggest ADRs via `/adr create`
|
||||
- Skip user approval of the charter
|
||||
|
||||
@@ -44,7 +44,7 @@ Update `Project: {Name}` wiki page:
|
||||
- Change status: `Initiating` → `Planning`
|
||||
|
||||
### Step 6: Present and Confirm
|
||||
Show all artifacts to user. Approval transitions to `Executing` (ready for first `/sprint-plan`).
|
||||
Show all artifacts to user. Approval transitions to `Executing` (ready for first `/sprint plan`).
|
||||
|
||||
## Output
|
||||
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
---
|
||||
name: projman setup
|
||||
description: Configure projman - full setup, quick project init, or sync after repo move
|
||||
---
|
||||
|
||||
# PM Setup
|
||||
# Projman Setup
|
||||
|
||||
## Skills Required
|
||||
|
||||
@@ -22,11 +23,11 @@ Unified setup command for all configuration needs.
|
||||
## Invocation
|
||||
|
||||
```
|
||||
/pm-setup # Auto-detect appropriate mode
|
||||
/pm-setup --full # Full wizard (MCP + system + project)
|
||||
/pm-setup --quick # Project-only setup
|
||||
/pm-setup --sync # Update after repo move
|
||||
/pm-setup --clear-cache # Clear plugin cache (between sessions only)
|
||||
/projman setup # Auto-detect appropriate mode
|
||||
/projman setup --full # Full wizard (MCP + system + project)
|
||||
/projman setup --quick # Project-only setup
|
||||
/projman setup --sync # Update after repo move
|
||||
/projman setup --clear-cache # Clear plugin cache (between sessions only)
|
||||
```
|
||||
|
||||
## Mode Detection
|
||||
13
plugins/projman/commands/projman.md
Normal file
13
plugins/projman/commands/projman.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: projman plugin management
|
||||
---
|
||||
|
||||
# /projman
|
||||
|
||||
Plugin-level management commands for projman.
|
||||
|
||||
## Sub-commands
|
||||
|
||||
| Sub-command | Description |
|
||||
|-------------|-------------|
|
||||
| `/projman setup` | Configure projman for a project |
|
||||
@@ -38,14 +38,14 @@ Manage the full RFC lifecycle through sub-commands. RFCs provide a structured wa
|
||||
Create a new RFC wiki page to track a feature idea through the review lifecycle.
|
||||
|
||||
**Workflow:**
|
||||
1. Check if conversation has clarified specification (from `/clarify`)
|
||||
1. Check if conversation has clarified specification (from `/clarity clarify`)
|
||||
2. If no context: prompt for Summary, Motivation, and initial Design
|
||||
3. Call `allocate_rfc_number` MCP tool for next sequential number
|
||||
4. Create RFC page using template from `skills/rfc-templates.md`
|
||||
5. Update RFC-Index wiki page (create if doesn't exist)
|
||||
6. Display RFC number, wiki link, and next steps
|
||||
|
||||
**Input Mapping (from /clarify):**
|
||||
**Input Mapping (from /clarity clarify):**
|
||||
|
||||
| Clarify Section | RFC Section |
|
||||
|-----------------|-------------|
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
---
|
||||
name: sprint close
|
||||
description: Complete sprint and capture lessons learned to Gitea Wiki
|
||||
agent: orchestrator
|
||||
---
|
||||
@@ -21,7 +22,7 @@ Complete the sprint, capture lessons learned to Gitea Wiki, and update documenta
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/sprint-close` when sprint work is complete.
|
||||
Run `/sprint close` when sprint work is complete.
|
||||
|
||||
## Workflow
|
||||
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
---
|
||||
name: sprint plan
|
||||
description: Start sprint planning with AI-guided architecture analysis and issue creation
|
||||
agent: planner
|
||||
---
|
||||
|
||||
@@ -1,9 +1,10 @@
|
||||
---
|
||||
name: sprint review
|
||||
description: Pre-sprint-close code quality review
|
||||
agent: code-reviewer
|
||||
---
|
||||
|
||||
# PM Review - Code Review for Sprint Close
|
||||
# Sprint Review - Code Review for Sprint Close
|
||||
|
||||
## Skills Required
|
||||
|
||||
@@ -16,7 +17,7 @@ Review recent code changes for quality issues before closing the sprint.
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/pm-review` before `/sprint-close` to catch issues.
|
||||
Run `/sprint review` before `/sprint close` to catch issues.
|
||||
|
||||
## Workflow
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
---
|
||||
name: sprint start
|
||||
description: Begin sprint execution with relevant lessons learned from previous sprints
|
||||
agent: orchestrator
|
||||
---
|
||||
@@ -24,7 +25,7 @@ Initiate sprint execution. The orchestrator agent verifies approval, analyzes de
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/sprint-start` when ready to begin executing a planned sprint.
|
||||
Run `/sprint start` when ready to begin executing a planned sprint.
|
||||
|
||||
**Flags:**
|
||||
- `--force` — Bypass approval gate (emergency only, logged to milestone)
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
---
|
||||
name: sprint status
|
||||
description: Check current sprint progress, identify blockers, optionally generate dependency diagram or token budget report
|
||||
---
|
||||
|
||||
@@ -22,9 +23,9 @@ Check current sprint progress, identify blockers, and show execution status. Opt
|
||||
## Invocation
|
||||
|
||||
```
|
||||
/sprint-status # Text-based status report
|
||||
/sprint-status --diagram # Include Mermaid dependency diagram
|
||||
/sprint-status --tokens # Show token budget estimation report
|
||||
/sprint status # Text-based status report
|
||||
/sprint status --diagram # Include Mermaid dependency diagram
|
||||
/sprint status --tokens # Show token budget estimation report
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
---
|
||||
name: sprint test
|
||||
description: Run tests with coverage or generate tests for specified code
|
||||
---
|
||||
|
||||
# PM Test
|
||||
# Sprint Test
|
||||
|
||||
## Skills Required
|
||||
|
||||
@@ -15,13 +16,13 @@ Unified testing command for running tests and generating new tests.
|
||||
## Invocation
|
||||
|
||||
```
|
||||
/pm-test # Default: run tests
|
||||
/pm-test run # Run tests, check coverage
|
||||
/pm-test run --coverage # Run with coverage report
|
||||
/pm-test run --verbose # Verbose output
|
||||
/pm-test gen <target> # Generate tests for target
|
||||
/pm-test gen <target> --type=unit # Specific test type
|
||||
/pm-test gen <target> --framework=jest # Specific framework
|
||||
/sprint test # Default: run tests
|
||||
/sprint test run # Run tests, check coverage
|
||||
/sprint test run --coverage # Run with coverage report
|
||||
/sprint test run --verbose # Verbose output
|
||||
/sprint test gen <target> # Generate tests for target
|
||||
/sprint test gen <target> --type=unit # Specific test type
|
||||
/sprint test gen <target> --framework=jest # Specific framework
|
||||
```
|
||||
|
||||
## Mode Selection
|
||||
@@ -104,15 +105,15 @@ See `skills/test-standards.md` for test patterns and structure.
|
||||
|
||||
## Sprint Integration
|
||||
|
||||
The `/pm-test` command plays a critical role in the sprint close workflow:
|
||||
The `/sprint test` command plays a critical role in the sprint close workflow:
|
||||
|
||||
1. After `/pm-review` identifies code quality issues
|
||||
2. Before `/sprint-close` finalizes the sprint
|
||||
1. After `/sprint review` identifies code quality issues
|
||||
2. Before `/sprint close` finalizes the sprint
|
||||
3. The code reviewer and orchestrator reference test results when deciding if a sprint is ready to close
|
||||
|
||||
### Pre-Close Verification
|
||||
|
||||
When running `/pm-test run` before sprint close:
|
||||
When running `/sprint test run` before sprint close:
|
||||
|
||||
1. **Identify sprint files** - Files changed in the current sprint (via git diff against development)
|
||||
2. **Check test coverage** - Report which sprint files have tests and which don't
|
||||
@@ -125,31 +126,31 @@ When running `/pm-test run` before sprint close:
|
||||
|
||||
### Run all tests
|
||||
```
|
||||
/pm-test run
|
||||
/sprint test run
|
||||
```
|
||||
Detects framework, runs full test suite, reports results.
|
||||
|
||||
### Run with coverage
|
||||
```
|
||||
/pm-test run --coverage
|
||||
/sprint test run --coverage
|
||||
```
|
||||
Same as above plus coverage percentage per file.
|
||||
|
||||
### Generate tests for a specific file
|
||||
```
|
||||
/pm-test gen src/auth/jwt_service.py
|
||||
/sprint test gen src/auth/jwt_service.py
|
||||
```
|
||||
Analyzes the file, generates a test file at `tests/test_jwt_service.py`.
|
||||
|
||||
### Generate specific test type
|
||||
```
|
||||
/pm-test gen src/api/routes/auth.py --type=integration
|
||||
/sprint test gen src/api/routes/auth.py --type=integration
|
||||
```
|
||||
Generates integration tests (request/response patterns) instead of unit tests.
|
||||
|
||||
### Generate with specific framework
|
||||
```
|
||||
/pm-test gen src/components/Card.jsx --framework=vitest
|
||||
/sprint test gen src/components/Card.jsx --framework=vitest
|
||||
```
|
||||
Uses Vitest instead of auto-detected framework.
|
||||
|
||||
@@ -161,7 +162,7 @@ Uses Vitest instead of auto-detected framework.
|
||||
|----------|----------|
|
||||
| No test framework detected | List what was checked, ask user to specify test command |
|
||||
| Tests fail | Report failures clearly, recommend "TESTS MUST PASS before sprint close" |
|
||||
| No tests exist for sprint files | Warn with file list, offer to generate with `/pm-test gen` |
|
||||
| No tests exist for sprint files | Warn with file list, offer to generate with `/sprint test gen` |
|
||||
| External services required | Ask for confirmation before running tests that need database/API |
|
||||
| Mixed framework project | Detect all frameworks, ask which to run or run all |
|
||||
|
||||
18
plugins/projman/commands/sprint.md
Normal file
18
plugins/projman/commands/sprint.md
Normal file
@@ -0,0 +1,18 @@
|
||||
---
|
||||
description: Sprint lifecycle management
|
||||
---
|
||||
|
||||
# /sprint
|
||||
|
||||
Sprint lifecycle management for projman.
|
||||
|
||||
## Sub-commands
|
||||
|
||||
| Sub-command | Description |
|
||||
|-------------|-------------|
|
||||
| `/sprint plan` | Analyze requirements, create issues, request approval |
|
||||
| `/sprint start` | Begin execution, load context, dispatch tasks |
|
||||
| `/sprint status` | Check progress, blockers, completion percentage |
|
||||
| `/sprint close` | Capture lessons learned, close milestone |
|
||||
| `/sprint review` | Pre-close code quality review |
|
||||
| `/sprint test` | Run/generate tests for sprint scope |
|
||||
Reference in New Issue
Block a user