give-plan

What problem does it solve?

Projects and teams often start coding before a clear, reviewable specification exists, which leads to rework, inconsistent implementations, hidden assumptions, and missed validation criteria. This Skill ensures work is paused to produce an inspectable plan that documents scope, tradeoffs, and validation before any code is written.

Core Features & Use Cases

• Clarify goals with focused questions: Ask only what materially changes the plan so the artifact is precise and reviewable.
• Ground recommendations in the repository: Read relevant files, separate confirmed facts from inferences, and call out unknowns.
• Choose the right artifact size: Produce inline prose for tiny changes, timestamped plan files for medium work, or phased directories for large rollouts.
• Provide validation and rollout guidance: List affected files/systems, dependencies, sequencing, validation checkpoints, rollback steps, risks, and mitigations.
• Use Cases: drafting a migration rollout, proposing an architecture decision for team review, phasing a multi-file feature, or writing a spec before an assigned implementation.

Quick Start

Create a phased implementation plan that summarizes the problem, recommended approach, affected files, phases, validation steps, risks and mitigations, and explicit approvals needed.