Implementation Plan Authoring

What problem does it solve?

Captures the current problem statement, constraints, and phased execution strategy in a durable plan file so decisions survive context compression and future agents can resume without prior chat history.

Core Features & Use Cases

• Structured plan template: Requires the canonical sections (purpose, required reading commands, problem statement, scope, context, end state, strategy, contracts, testing plan, rollout checklist, risks, non-goals, definition of done) so nothing is left implicit.
• Guardrail enforcement: Emphasizes the required reading commands, explicit constraints such as greenfield-only demands, and command evidence or assumptions, supporting predictable handoffs.
• Delivery scenarios: Trigger when the context window is tight, the user requests a plan artifact, or multi-component work needs phased ordering with acceptance criteria that future agents can verify independently.

Quick Start

Ask for an implementation plan that records the concrete problem, constraints, required reading commands, phased strategy, acceptance criteria, and rollout checkpoints before history compacts.