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:
@@ -5,6 +5,6 @@ See **[docs/CONFIGURATION.md](../../docs/CONFIGURATION.md)** for complete setup
|
||||
## Quick Commands
|
||||
|
||||
```
|
||||
/pm-setup --full # First time on this machine
|
||||
/pm-setup --quick # New project (system already configured)
|
||||
/projman setup --full # First time on this machine
|
||||
/projman setup --quick # New project (system already configured)
|
||||
```
|
||||
|
||||
@@ -6,12 +6,12 @@ This project uses the **projman** plugin for sprint planning and project managem
|
||||
|
||||
| Command | Description |
|
||||
|---------|-------------|
|
||||
| `/sprint-plan` | Start sprint planning with AI-guided architecture analysis |
|
||||
| `/sprint-start` | Begin sprint execution with relevant lessons learned |
|
||||
| `/sprint-status` | Check current sprint progress and identify blockers |
|
||||
| `/sprint-close` | Complete sprint and capture lessons learned to Gitea Wiki |
|
||||
| `/labels-sync` | Synchronize label taxonomy from Gitea |
|
||||
| `/pm-setup` | Run initial setup for projman plugin |
|
||||
| `/sprint plan` | Start sprint planning with AI-guided architecture analysis |
|
||||
| `/sprint start` | Begin sprint execution with relevant lessons learned |
|
||||
| `/sprint status` | Check current sprint progress and identify blockers |
|
||||
| `/sprint close` | Complete sprint and capture lessons learned to Gitea Wiki |
|
||||
| `/labels sync` | Synchronize label taxonomy from Gitea |
|
||||
| `/projman setup` | Run initial setup for projman plugin |
|
||||
| `/rfc create` | Create new RFC from conversation or clarified spec |
|
||||
| `/rfc list` | List all RFCs grouped by status |
|
||||
| `/rfc review` | Submit Draft RFC for review |
|
||||
@@ -56,8 +56,8 @@ The following Gitea MCP tools are available for issue and project management:
|
||||
|
||||
### Usage Guidelines
|
||||
|
||||
- **Always use `/sprint-plan`** when starting new development work
|
||||
- **Check `/sprint-status`** regularly during active sprints
|
||||
- **Run `/sprint-close`** at the end of each sprint to capture lessons learned
|
||||
- **Always use `/sprint plan`** when starting new development work
|
||||
- **Check `/sprint status`** regularly during active sprints
|
||||
- **Run `/sprint close`** at the end of each sprint to capture lessons learned
|
||||
- Use `suggest_labels` when creating issues to ensure proper categorization
|
||||
- Search lessons learned with `search_lessons` before implementing features to avoid repeated mistakes
|
||||
|
||||
@@ -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 |
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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 |
|
||||
|----------------|-------------|
|
||||
|
||||
@@ -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 |
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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`.**
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -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)
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -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] |
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user