Implementation Plan Writer FAQs

Question 1

What makes this different from standard task descriptions?

Accepted Answer

Standard tasks often use vague checklists; this skill replaces them with definitive, executable steps including actual code, specific file paths, and verification commands verified against the live codebase.

Question 2

Does it support Test-Driven Development (TDD)?

Accepted Answer

Yes, for new features it follows a strict TDD cycle: generating steps to write a failing test, verify the failure, implement the code, and confirm the pass.

Question 3

Can I use this for a whole project at once?

Accepted Answer

Absolutely. You can target a single task, a specific range, or an entire epic. The skill will automatically navigate the dependency tree and process tasks in sequence.

Question 4

Do I need to manually verify my file structure first?

Accepted Answer

No. The skill uses a codebase-investigator agent to report on the actual state of your files, adjusting the implementation plan to match reality instead of relying on outdated assumptions.

Question 5

Why does it forbid placeholders in code?

Accepted Answer

Placeholders like '[insert code here]' require the developer to have context. This skill aims for zero-context execution, meaning the instructions must be complete and copy-paste ready.

Implementation Plan Writer

Key Features

Use Cases

Implementation Plan Writer

Key Features

Use Cases