implement-task

Implement Task: $ARGUMENTS

Implement a specific task by ID, or find and implement the next available task.

Step 0: Parse and Validate Arguments

Parse $ARGUMENTS to extract:

1. feature-dir (required): The first word/argument
2. task-id (optional): The second word/argument, if provided

Normalize task-id format:

• If task-id is just a number (e.g., 3), convert to TASK-003 format (zero-padded to 3 digits)
• If task-id is already in TASK-XXX format, use as-is
• Store the normalized task-id for later use

If feature-dir is empty or missing:

"Error: Feature directory is required.

Usage: /implement-task <feature-dir> [task-id]

Examples:

• /implement-task my-feature - implement next available task
• /implement-task my-feature 3 - implement TASK-003 specifically
• /implement-task my-feature TASK-003 - same as above

To see available features:

ls .shipspec/planning/
```"

Stop here - do not proceed without a feature directory.

Step 1: Locate Feature Directory

Check that the feature directory exists:

ls -d .shipspec/planning/[feature-dir] 2>/dev/null || echo "NOT_FOUND"

If NOT_FOUND:

"No directory found for '[feature-dir]' at .shipspec/planning/[feature-dir].

Please run /feature-planning first to create the planning artifacts."

Check for TASKS.json:

ls -la .shipspec/planning/[feature-dir]/TASKS.json 2>/dev/null || echo "TASKS.json NOT FOUND"

If TASKS.json not found:

"No TASKS.json found in .shipspec/planning/[feature-dir]/.

Run /feature-planning to complete the planning workflow and generate tasks."

Step 2: Load, Parse, and Validate Tasks

Delegate to the task-manager agent with:

• Feature name: [feature-dir]
• Operation: parse

If error (TASKS.json not found or empty): Show the error message from task-manager and stop.

If successful: Use the task map and statistics from the response.

Next, validate the task structure by delegating to task-manager with:

• Feature name: [feature-dir]
• Operation: validate