Implementation Plan Authoring

To preserve implementation context, capture the problem statement, constraints, and execution strategy in a durable plan file. This ensures decisions survive context compression and future agents can resume work without prior chat history.

A multi-component implementation plan should include purpose, required reading commands, scoped problem statement, context, end state, phased strategy, contracts, testing plan, rollout checklist, risks, non-goals, and definition of done for independent agent verification.

You need a durable plan file when context windows are tight, multi-component work requires phased ordering, or a reusable plan is requested for future agents to execute and validate changes independently.

Document execution strategy by defining phased implementation steps, explicit constraints, and acceptance criteria in a structured plan file. Include required reading commands and rollout validation checklists for predictable agent handoffs.

Generating an implementation plan requires no external dependencies or environment setup. The Skill operates independently to structure your existing problem context, constraints, and testing strategy into a durable file artifact.

The best way to structure a testing plan is to embed testing gates and rollout validation checklists directly within the implementation plan. This ensures future agents can verify acceptance criteria and execute deployment steps independently.