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.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| projman project | Project lifecycle management — type /projman project <action> for commands |
/project
Project lifecycle management from concept to MVP.
When invoked without a sub-command, display available actions and ask which to run.
Available Commands
| Action | Command to Invoke | Description |
|---|---|---|
initiation |
/projman:project-initiation |
Analyze source, create charter, decompose into epics |
plan |
/projman:project-plan |
Create WBS, risk register, sprint roadmap |
status |
/projman:project-status |
Full project hierarchy view |
close |
/projman:project-close |
Retrospective, lessons learned, archive |
Usage
/project initiation <source-path-or-description>
/project plan <project-name>
/project status <project-name>
/project close <project-name>
Routing
If $ARGUMENTS is provided (e.g., user typed /project initiation):
- 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:project-initiation)