# create-plan (Unified Skill)

## Core Instructions (SKILL.md)

# Create Implementation Plan

Create a detailed implementation plan for the requested feature.

## Procedure

1. Read any provided spec or task description fully.
2. Research the codebase and existing patterns.
3. If multiple approaches are viable, present options and get alignment before finalizing.
4. Write the plan using `references/plan-template.md`.
5. If needed, use `references/scenarios.md` for example interaction patterns.

## Rules

- Be specific: include actual file paths and concrete changes.
- Plan tests before implementation for each phase.
- Keep phases independently verifiable.
- Resolve open questions with normal user clarification, not tool-specific assumptions.
- Prefer realistic plans over exhaustive but unusable plans.


---

## Reference: plan-template.md

```markdown
# [Feature Name] Implementation Plan

Date: YYYY-MM-DD

## Overview

[Brief description of what is being implemented]

## Related

- Spec: `specs/...` [if applicable]
- Research: `research/...` [if applicable]
- Related issues or tickets: [references]

## Current State

[What exists now and what is missing]

## Desired End State

[What will exist after implementation]

How to verify:
- [Specific verification step]
- [Expected behavior]

## Out of Scope

[What is explicitly excluded]

## Risks & Mitigations

[Key risks and mitigations]

## Phase 1: [Name]

### Changes Required

File: `path/to/file.ext`
- Changes: [Specific modifications needed]
- Tests: [What to write first]

### Implementation Approach

[How this phase should be implemented]

### Success Criteria

Automated:
- [ ] Tests pass
- [ ] Type checking passes [if applicable]
- [ ] Linting passes [if applicable]
- [ ] Build succeeds [if applicable]

Manual:
- [ ] [Manual verification step]

### Dependencies

[Dependencies or blockers]

---

## Testing Strategy

Following TDD:
1. Write tests first.
2. Confirm they fail.
3. Implement the minimum to pass.
4. Refactor while staying green.

Test types needed:
- Unit tests: [What to cover]
- Integration tests: [What to cover]
- E2E tests: [If applicable]

## Rollback Strategy

[How to back out safely]

## Related Links

- [Documentation]
- [Similar implementation]
- [External resource]
```


---

## Reference: scenarios.md

## Example Scenarios

### Feature with spec

- Read the spec.
- Research existing patterns.
- Propose a phased plan grounded in the codebase.

### No spec, only feature description

- Research the current implementation.
- Present viable options if there is a meaningful design choice.
- Recommend one approach and then write the detailed plan.

### Complex feature with technical uncertainty

- Research the architectural constraints first.
- Present 2-3 options with tradeoffs.
- Get user alignment before writing the final plan.


---