Back to corpus
research noteexperiment writeup candidatescore 18
Executing Plans
For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed
Full HTML reader
Read the full artifact
Extracted abstract or opening context
--- name: executing-plans description: Use when you have a written implementation plan to execute in a separate session with review checkpoints ---
Load plan, review critically, execute tasks in batches, report for review between batches.
**Announce at start:** "I'm using the executing-plans skill to implement this plan."
### Step 1: Load and Review Plan 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: Create TodoWrite and proceed
For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.