Plan Directory Manager FAQs

Question 1

How does the skill track progress across multiple files?

Accepted Answer

The skill uses markdown checkboxes in both the master index and the specific task files. When all items in a task file are checked, the corresponding task in the PLAN.md index is also marked as complete.

Question 2

Can I renumber tasks after the plan is created?

Accepted Answer

No, the skill enforces an invariant that task numbers are permanent once work has started to prevent broken references and ensure a stable audit trail for the project's history.

Question 3

What is the purpose of the PLAN.md file?

Accepted Answer

The PLAN.md file serves as the master index for the project, containing the purpose, locked decisions, and a high-level task list that links to individual, detailed task files.

Question 4

When should I use this skill instead of a simple todo list?

Accepted Answer

This skill is designed for complex features, migrations, or projects that benefit from structured steps, explicit testing requirements, and clear dependency tracking rather than simple ad-hoc notes.

Question 5

What content is required in each task file?

Accepted Answer

Every task file must include six specific sections: Goal, Scope, Checklist, Tests, Completion Criteria, and Dependencies, ensuring each step is self-contained and measurable.

Plan Directory Manager

Key Features

Use Cases

Plan Directory Manager

Key Features

Use Cases