Transition issue to a specific workflow state
Transitions issue to specified workflow state with optional comment.
/plugin marketplace add fractary/claude-plugins/plugin install fractary-work@fractary<number> <state> [--comment "<text>"]claude-haiku-4-5<CRITICAL_RULES> YOU MUST:
YOU MUST NOT:
THIS COMMAND IS ONLY A ROUTER. </CRITICAL_RULES>
<WORKFLOW> 1. **Parse user input** - Extract issue number (required) - Extract state (required) - Parse optional arguments: --comment - Validate required arguments are presentCapture working directory context
WORK_CWD="${PWD}"Build structured request
ACTUALLY INVOKE the Task tool
IF THE TASK TOOL INVOCATION FAILS:
Return response
<ARGUMENT_SYNTAX>
This command follows the space-separated argument syntax (consistent with work/repo plugin family):
--flag value (NOT --flag=value)State values are exact keywords (no quotes needed):
✅ /work:state-transition 123 in_progress
✅ /work:state-transition 123 in_review
✅ /work:state-transition 123 done
❌ /work:state-transition 123 "in progress" # Use underscores, not spaces
❌ /work:state-transition 123 in-progress # Use underscores, not hyphens
Always use quotes for multi-word comments:
✅ /work:state-transition 123 in_progress --comment "Starting work on this"
✅ /work:state-transition 123 in_review --comment "Ready for review"
❌ /work:state-transition 123 in_progress --comment Starting work on this
Single-word comments don't require quotes:
✅ /work:state-transition 123 done --comment Completed
State values use underscores:
open, in_progress, in_review, done, closedin-progress, inProgress, in progress
</ARGUMENT_SYNTAX><ARGUMENT_PARSING>
Required Arguments:
number (number): Issue number (e.g., 123, not "#123")state (enum): Target workflow state. Must be one of: open, in_progress, in_review, done, closed (note: use underscores)Optional Arguments:
--comment (string): Comment to post with transition, use quotes if multi-word (e.g., "Moving to in_progress")Maps to: transition-state operation </ARGUMENT_PARSING>
<EXAMPLES> ## Usage Examples# Transition to in_progress
/work:state-transition 123 in_progress
# Transition with comment
/work:state-transition 123 in_progress --comment "Starting work on this"
# Transition to in_review
/work:state-transition 123 in_review --comment "Ready for code review"
# Transition to done
/work:state-transition 123 done --comment "Implementation complete"
# Transition to closed
/work:state-transition 123 closed
</EXAMPLES>
<AGENT_INVOCATION>
After parsing arguments, invoke the work-manager agent with a structured request.
Invoke the fractary-work:work-manager agent with the following request:
{
"operation": "transition-state",
"parameters": {
"issue_number": "123",
"state": "in_progress",
"comment": "Starting work on this"
}
}
The work-manager agent will:
<ERROR_HANDLING> Common errors to handle:
Missing issue number:
Error: issue_number is required
Usage: /work:state-transition <number> <state>
Missing state:
Error: state is required
Usage: /work:state-transition <number> <state>
Invalid state:
Error: Invalid state: invalid_state
Valid states: open, in_progress, in_review, done, closed
Already in target state:
Warning: Issue #123 is already in state: in_progress
No action taken
</ERROR_HANDLING>
<NOTES> ## Universal StatesThe work plugin uses universal states that map to platform-specific states:
This command works with:
Platform is configured via /work:init and stored in .fractary/plugins/work/config.json.
FABER workflows automatically manage state transitions through the workflow phases (Frame → Architect → Build → Evaluate → Release).
For detailed documentation, see: /docs/commands/work-state.md
Related commands:
/work:state-close - Close issue/work:state-reopen - Reopen issue/work:comment-create - Add comment/work:init - Configure work plugin
</NOTES>