<skill_overview> <purpose>Produce consistently useful plans: short, verifiable, with a clear starting point and session breakdown.</purpose> <triggers> <trigger>You need to assemble the final plan document</trigger> <trigger>You want stable, easily scannable output</trigger> </triggers> </skill_overview>

<formatting_rules> <rule>Be concise: 1-2 sentences per bullet, no theory.</rule> <rule>Use clear section headings and lists.</rule> <rule>Use explicit yes/no checks where appropriate.</rule> </formatting_rules>

<plan_template> <template>

Project Plan: [Name]

Project Summary

What: ... For: ... Success metric: Project works if ...

Scope

In Scope: ... Out of Scope: ... Parking Lot: ...

Minimal Stack

1. •Tool 1: ...
2. •Tool 2: ... (if needed)

Session Breakdown

Session 1: ...

Objective: ... Steps: 1) ... 2) ... 3) ... Checkpoint: ...

Session 2: ...

...

Session 3: ...

...

Session 4 (Optional): ...

...

Validation Plan

• •Smoke: ...
• •Negative: ...

Critical Dropout Point

Most people quit when: ... How to push through: ...

Getting Started Right Now

First 15 minutes:

1. •...
2. •...
3. •...

Future Improvements (After V1)

• •... </template> </plan_template>

<quality_checklist> <item>Can the user start right now (First 15 minutes exists)?</item> <item>Is the success metric binary and verifiable?</item> <item>Do we have In/Out/Parking Lot?</item> <item>Does each session have a deliverable and checkpoint?</item> <item>Is the stack minimal (1-2 tools where possible)?</item> <item>Is there a critical dropout point + a push-through plan?</item> </quality_checklist>