implement-feature

Implement Feature: $ARGUMENTS

Automatically implement ALL tasks in a feature's TASKS.json file end-to-end. After all tasks are complete, run a comprehensive review against PRD, SDD, and all acceptance criteria.

Step 0: Validate Argument

If $ARGUMENTS is empty or missing:

"Error: Feature name is required.

Usage: /implement-feature <feature-name>

The feature name should match the name used with /feature-planning.

To see available features:

ls .shipspec/planning/
```"

Stop here - do not proceed without an argument.

Step 1: Locate Feature Directory

Check that the feature directory exists:

ls -d .shipspec/planning/$ARGUMENTS 2>/dev/null || echo "NOT_FOUND"

If NOT_FOUND:

"No directory found for '$ARGUMENTS' at .shipspec/planning/$ARGUMENTS.

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

Check for required planning artifacts:

echo "=== Checking planning artifacts ==="
ls .shipspec/planning/$ARGUMENTS/TASKS.json 2>/dev/null || echo "TASKS.json NOT FOUND"
ls .shipspec/planning/$ARGUMENTS/PRD.md 2>/dev/null || echo "PRD.md NOT FOUND"
ls .shipspec/planning/$ARGUMENTS/SDD.md 2>/dev/null || echo "SDD.md NOT FOUND"

If any artifact missing:

"Missing required planning artifacts for '$ARGUMENTS':

• [List missing files]

Run /feature-planning $ARGUMENTS to generate them."

Step 2: Load, Parse, and Validate Tasks

Delegate to the task-manager agent with:

• Feature name: $ARGUMENTS
• 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: $ARGUMENTS
• Operation: validate

If INVALID: Show all issues from the validation result (circular dependencies, multiple in-progress, invalid references) and stop.

If VALID: Tell the user:

"## Feature: $ARGUMENTS

Found X tasks total. Y completed, Z remaining.

Starting automatic implementation..."