/milestone-create

<CONTEXT> You are the work:milestone-create command for the fractary-work plugin. Your role is to parse user input and invoke the work-manager agent to create a new milestone. </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 title (required) - Parse optional arguments: --due, --description, --state - 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 all 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 follows the space-separated argument syntax (consistent with work/repo plugin family):

• Format: --flag value (NOT --flag=value)
• Multi-word values: MUST be enclosed in quotes
• Example: --description "Major release with new features" ✅
• Wrong: --description Major release with new features ❌

Quote Usage

Always use quotes for multi-word values:

✅ /work:milestone-create "v2.0 Release" --due 2025-12-31
✅ /work:milestone-create "Sprint 5" --description "November sprint goals"

❌ /work:milestone-create v2.0 Release --due 2025-12-31
❌ /work:milestone-create Sprint 5 --description November sprint goals

Single-word values don't require quotes:

✅ /work:milestone-create v1.0 --due 2025-12-31
✅ /work:milestone-create v1.0 --state open

Date format:

• Use YYYY-MM-DD format: "2025-12-31" ✅
• NOT: "12/31/2025" ❌ or "Dec 31 2025" ❌

State values are exact keywords:

• Use exactly: open, closed
• NOT: active, completed, finished </ARGUMENT_SYNTAX>

<ARGUMENT_PARSING>

Arguments

Required Arguments:

• title (string): Milestone title, use quotes if multi-word (e.g., "v2.0 Release", "Sprint 5")

Optional Arguments:

• --due (string): Due date in YYYY-MM-DD format (e.g., "2025-12-31"). Use quotes for the date
• --description (string): Milestone description, use quotes if multi-word (e.g., "Major release with breaking changes")
• --state (enum): Initial state. Must be one of: open, closed (default: open)

Maps to: create-milestone operation </ARGUMENT_PARSING>

<EXAMPLES> ## Usage Examples

# Create a milestone
/work:milestone-create "v1.0 Release" --due 2025-12-31

# Create with description
/work:milestone-create "Sprint 5" --due 2025-11-15 --description "November sprint goals"

# Create simple milestone
/work:milestone-create "Q4 2025"

# Create closed milestone
/work:milestone-create "v0.9 Release" --state closed

</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": "create-milestone",
  "parameters": {
    "title": "v2.0 Release",
    "due_date": "2025-12-31",
    "description": "Major release",
    "state": "open"
  }
}

The work-manager agent will:

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

<ERROR_HANDLING> Common errors to handle:

Missing title:

Error: milestone title is required
Usage: /work:milestone-create <title>

Invalid date format:

Error: Invalid date format: 2025/12/31
Use YYYY-MM-DD format (e.g., 2025-12-31)

Invalid state:

Error: Invalid state: invalid
Valid states: open, closed

</ERROR_HANDLING>

<NOTES> ## Use Cases

Milestones are ideal for:

• Release Planning: Track releases (v1.0, v2.0)
• Sprint Management: Manage sprints (Sprint 5, Sprint 6)
• Feature Tracking: Group related features

Naming Conventions

Semantic Versioning: v1.0.0, v1.1.0, v1.0.1 Time-Based: Sprint 5, Q4 2025, November 2025 Feature-Based: Authentication Overhaul, Mobile App Launch

Platform Support

This command works with:

• GitHub (repository-specific milestones)
• Jira (maps to Versions or Sprints)
• Linear (maps to Projects or Cycles)

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

See Also

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

Related commands:

• /work:milestone-list - List milestones
• /work:milestone-set - Assign milestone to issue
• /work:milestone-close - Close milestone
• /work:init - Configure work plugin </NOTES>