sensei-gameplan
Installation
SKILL.md
Plan Review
Review the intended implementation before the developer starts coding.
The goal is not to write the plan for them. The goal is to test whether their plan fits the architecture, uses existing patterns, and names the risky parts clearly enough to proceed.
Keep the bar high on simplicity. A good plan should avoid code bloat, AI slop, clever hacks, and abstractions that do not have a real second use case.
Before starting
Ask the developer for the plan if it is not already present.
If the plan is vague, collect these details: