lmiranda
035cd00f4b
All projman command names now start with 'projman' prefix to match git-flow behavior and avoid forced plugin namespace in autocomplete. Before: /projman:sprint-plan, /projman:project-status After: /projman sprint plan, /projman project status This matches git-flow which shows /gitflow commit, /gitflow status. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
name, description
| name | description |
|---|---|
| projman sprint | Sprint lifecycle management — type /projman sprint <action> for commands |
/sprint
Sprint lifecycle management for projman.
When invoked without a sub-command or with $ARGUMENTS, handle as follows:
Available Commands
| Action | Command to Invoke | Description |
|---|---|---|
plan |
/projman:sprint-plan |
Analyze requirements, create issues, request approval |
start |
/projman:sprint-start |
Begin execution, load context, dispatch tasks |
status |
/projman:sprint-status |
Check progress, blockers, completion percentage |
close |
/projman:sprint-close |
Capture lessons learned, close milestone |
review |
/projman:sprint-review |
Pre-close code quality review |
test |
/projman:sprint-test |
Run/generate tests for sprint scope |
Routing
If $ARGUMENTS is provided (e.g., user typed /sprint plan):
- Match the first word of
$ARGUMENTSagainst the Action column above - Invoke the corresponding command from the "Command to Invoke" column using the Skill tool
- Pass any remaining arguments to the invoked command
If no arguments provided:
- Display the Available Commands table
- Ask: "Which action would you like to run?"
- When the user responds, invoke the matching command using the Skill tool
Note: Commands can also be invoked directly using their plugin-prefixed names (e.g., /projman:sprint-plan)