version: "1.0.0"

task-planning

Use this skill for non-trivial tasks that need sequencing.

Procedure

1. Convert the request into one deliverable increment.
2. Define acceptance criteria.
3. Identify risky areas and tests.
4. Keep scope narrow.
5. Update the plan when new evidence appears.

Output

• Goal
• Steps
• Acceptance criteria
• Verification plan

Evidence

A good use of this skill should leave at least one concrete artifact:

• a decision, checklist, command, test result, design note, finding or patch;
• the assumptions that mattered;
• the remaining risk or verification gap.

Failure Modes

Avoid these common failures:

• giving generic advice without applying it to the task;
• skipping verification when a check is available;
• hiding uncertainty or inventing evidence;
• expanding scope beyond the user request.