spok-create-plan

name	spok-create-plan
description	convert structure outline into a detailed implementation plan

Create Plan

You are in the final Plan Writing phase. Convert the structure outline into a complete, detailed implementation plan.

Steps

1. Read all input files FULLY:

   • Use Read tool WITHOUT limit/offset to read all provided file paths
   • The skill argument is the absolute path to the task directory. Use ls <task-dir> to enumerate all related documents.
   • Read everything in the task directory to build full context

2. Read relevant code files:

   • Read any source files mentioned in the research, design, or structure documents
   • Build context for writing specific code examples

3. Read the plan template:

Read({SKILLBASE}/references/plan_template.md)

4. Write the implementation plan:
   • Before writing, delete any sibling files matching <task-dir>/[0-9]{4}-[0-9]{2}-[0-9]{2}-plan.md (legacy date-prefixed orphans from pre-fork runs).
   • Write to <task-dir>/plan.md (bare filename; the task directory is the absolute path passed as the skill argument and already exists)
   • Convert each phase from the structure outline into detailed implementation steps
   • Include specific code examples for each change
   • Add both automated and manual success criteria

Plan Writing Guidelines

• Each phase should be independently testable
• Include specific code examples, not just descriptions
• Automated verification should be runnable commands
• Manual verification should be specific, actionable steps
• Pause for human confirmation between phases
• If the research documented testing patterns for the components being changed, include test code in the plan (new test files or additions to existing test files). Follow the existing test patterns found in the research.

Document Precedence

When documents conflict, the most recent document wins: plan > structure outline > design discussion > research > ticket

The plan is the final authority. Follow the structure outline and design decisions over the original ticket when they differ.

Output

1. Read the final output template:

Read({SKILLBASE}/references/plan_final_answer.md)

2. Respond with a summary following the template

## Markdown Formatting

When writing markdown files that contain code blocks showing other markdown (like README examples or SKILL.md templates), use 4 backticks (````) for the outer fence so inner 3-backtick code blocks don't prematurely close it:

# Example README
## Installation
```bash
npm install example
```

Validation Design

Not every phase requires manual validation, don't put steps for manual validation just to have them.