Technical Planning FAQs

Question 1

What sizing method does this skill use for tasks?

Accepted Answer

The skill uses relative sizing (Small, Medium, Large) based on complexity and uncertainty rather than strict hours, encouraging more realistic planning and easier task decomposition.

Question 2

Does this skill actually write the code?

Accepted Answer

No, this skill is dedicated to the planning phase. It creates the blueprint that you or Claude will follow to ensure implementation is organized and thorough.

Question 3

How does this differ from the Architecture Design skill?

Accepted Answer

Technical Planning focuses on tactical execution—how to build a specific feature over days or weeks—whereas Architecture Design focuses on long-term system structure and high-level decisions.

Question 4

How does it help with testing?

Accepted Answer

The skill mandates a predefined testing strategy for every plan, covering unit, integration, and manual testing steps to ensure success criteria are met before a task is considered complete.

Question 5

Can I use this for bug fixes as well as new features?

Accepted Answer

Yes, it is highly effective for planning non-trivial bug fixes, ensuring that the current state is analyzed and all necessary tests are defined before the fix is applied.

Technical Planning

Key Features

Use Cases

Technical Planning

Key Features

Use Cases