Session Artifacts & Planning
Get a plan from December and approve it before December changes your code.
This page helps you get a plan from December and approve it before December changes any files.
Overview
A plan is the main session artifact in the CLI. December writes the plan as text in your session. The plan prompt tells December not to run tools, so no files change while December writes the plan.
Use a plan for large features and for changes that touch many files. You see the proposed changes first, and you decide what happens next.
Make a plan
- Type
/planand your goal:
/plan add rate limiting to the login route
- December writes a step-by-step plan. The plan starts with
### Implementation Planand names the files to create, change, or delete. - December shows the plan approval menu.
Approve, refine, or reject the plan
The plan approval menu has four options. Press the key, or select the option and press Enter.
| Option | Key | What happens |
|---|---|---|
| Approve & Execute | y | December starts to make the changes in the plan, step by step. |
| Refine Plan | r | December puts /plan refine: in the input. Type your feedback. |
| View Full Plan | v | December opens the full plan in a viewer that you can scroll. |
| Reject / Cancel | n | December discards the plan. No files change. |
When you refine a plan, December writes a new plan from your feedback. Then it shows the approval menu again.
You can also type these commands in the input:
/plan refine: use Redis instead of an in-memory map
/plan approve
/plan reject
Where the plan lives
December keeps the plan in the current session only. December does not save the plan to a file. To keep the plan, use /copy to copy the last response, then save it where you want.
If you approve the plan, December edits your files. To undo those edits, see Git Checkpoints.