Implement: execute a task from a Breakdown

When the user types /implement and references a task file (e.g., @projects/<domain-name>/<project-name>/tasks/01-add-feature-flag.md), do the following:

1) Understand the task and its context (required)

• Read the task file end-to-end.
• Identify the goal, acceptance criteria, key touch points, and risks.
• Read the parent Plan (plan.md) and Breakdown (tasks/*.md overview file) for broader context.
• Check Dependencies — if a blocking task is incomplete, warn the user before proceeding.
• Search the codebase for the key touch points to understand existing patterns and conventions.

2) Shape Up principles for implementation

Follow the Shape Up "hill climbing" model:

Uphill (figuring it out)

• Explore unknowns first — if there are risks or unclear patterns, investigate before writing code.