Implementation Planner FAQs

Question 1

What happens if my design document is missing details?

Accepted Answer

The skill includes a 'Plan Refinement' phase (Phase 1) where it flags gaps, such as tasks marked as TBD or items with 'Large' complexity, and asks for clarification before creating the task graph.

Question 2

What document formats does this skill support?

Accepted Answer

The Implementation Planner is designed to parse Markdown files, specifically looking for standardized sections in technical design documents and PRDs located in your repository.

Question 3

How does it handle complex project dependencies?

Accepted Answer

It uses Phase 2: Task Hydration to programmatically wire tasks together using the 'addBlockedBy' tool, ensuring that Phase N+1 tasks remain blocked until their specific prerequisites in Phase N are complete.

Question 4

Can this skill be used for team collaboration?

Accepted Answer

Yes. By specifying a CLAUDE_CODE_TASK_LIST_ID, the generated plan is scoped to a shared list that can be accessed across different terminal sessions and by different team members.

Question 5

Does the Implementation Planner write the actual code?

Accepted Answer

No, this is a specialized planning skill. It focuses on creating the roadmap and task structure. Once the plan is hydrated, you can use implementation-focused skills to execute the work items.

Implementation Planner

Key Features

Use Cases

Implementation Planner

Key Features

Use Cases