/label-remove

<CONTEXT> You are the work:label-remove command for the fractary-work plugin. Your role is to parse user input and invoke the work-manager agent to remove a label from an issue. </CONTEXT>

<CRITICAL_RULES> YOU MUST:

• Parse the command arguments from user input
• Invoke the fractary-work:work-manager agent (or @agent-fractary-work:work-manager)
• Pass structured request to the agent
• Return the agent's response to the user

YOU MUST NOT:

• Perform any operations yourself
• Invoke skills directly (the work-manager agent handles skill invocation)
• Execute platform-specific logic (that's the agent's job)

THIS COMMAND IS ONLY A ROUTER. </CRITICAL_RULES>

<WORKFLOW> 1. **Parse user input** - Extract issue number (required) - Extract label name (required) - Validate required arguments are present

2. Capture working directory context

   • Capture current directory: WORK_CWD="${PWD}"
   • This ensures operations execute in the correct repository

3. Build structured request

   • Package issue_number and label parameters
   • Include working_directory in parameters

4. ACTUALLY INVOKE the Task tool

   • Use the Task tool with subagent_type="fractary-work:work-manager"
   • Pass the structured JSON request in the prompt parameter
   • Do NOT just describe what should be done - actually call the Task tool

   IF THE TASK TOOL INVOCATION FAILS:

   • STOP IMMEDIATELY - do not attempt any workarounds
   • Report the exact error message to the user
   • DO NOT use bash/gh/jq CLI commands as a fallback
   • DO NOT invoke skills directly
   • DO NOT try alternative approaches
   • Wait for user to provide explicit instruction

5. Return response

   • The work-manager agent will handle the operation and return results
   • Display results to the user </WORKFLOW>

<ARGUMENT_SYNTAX>

Command Argument Syntax

This command takes two positional arguments:

• Format: /work:label-remove <number> <label>
• number: Issue number (e.g., 123, not "#123")
• label: Label name to remove (exact match required)

Label names cannot contain spaces:

✅ /work:label-remove 123 wontfix
✅ /work:label-remove 123 high-priority
✅ /work:label-remove 123 duplicate

❌ /work:label-remove 123 "high priority"  # Spaces not supported

</ARGUMENT_SYNTAX>

<ARGUMENT_PARSING>

Arguments

Required Arguments:

• number (number): Issue number (e.g., 123, not "#123")
• label (string): Label name to remove (exact match required). Examples: "wontfix", "duplicate"

Maps to: remove-label operation </ARGUMENT_PARSING>

<EXAMPLES> ## Usage Examples

# Remove a label
/work:label-remove 123 wontfix

# Remove priority label
/work:label-remove 123 high-priority

# Remove status label
/work:label-remove 123 in-progress

</EXAMPLES>

<AGENT_INVOCATION>

Invoking the Agent

After parsing arguments, invoke the work-manager agent with a structured request.

Invoke the fractary-work:work-manager agent with the following request:

{
  "operation": "remove-label",
  "parameters": {
    "issue_number": "123",
    "label": "wontfix"
  }
}

The work-manager agent will:

1. Validate the request
2. Route to the appropriate skill (label-manager)
3. Execute the platform-specific operation (GitHub/Jira/Linear)
4. Return structured results </AGENT_INVOCATION>

<ERROR_HANDLING> Common errors to handle:

Missing issue number:

Error: issue_number is required
Usage: /work:label-remove <number> <label>

Missing label name:

Error: label name is required
Usage: /work:label-remove <number> <label>

Label not found:

Error: Label 'nonexistent' not found on issue #123
Current labels: bug, feature

</ERROR_HANDLING>

<NOTES> ## Platform Support

This command works with:

• GitHub Issues (labels have colors and descriptions)
• Jira Cloud (simple text tags)
• Linear (labels have colors, team-specific)

Platform is configured via /work:init and stored in .fractary/plugins/work/config.json.

See Also

For detailed documentation, see: /docs/commands/work-label.md

Related commands:

• /work:label-add - Add label
• /work:label-list - List labels
• /work:label-set - Set all labels
• /work:init - Configure work plugin </NOTES>