How to write a task CodeStilt gets right the first time

CodeStilt reads your project before it plans, but it can't read your mind. The clearer the task, the better the plan, and the fewer credits it uses.

1. Say what should happen, not only what's wrong

"Fix the menu" leaves a lot to guess. "On phones, the menu should close after tapping a link" tells it exactly what done looks like.

2. Name the page, file or feature

If you know where the change belongs, say so: "in the checkout page" or "in src/cart.js". It reads fewer files, so the task costs less.

3. One change per task

Three small tasks are easier to review and undo than one big one. If a task feels like a list, split it.

4. Say what to leave alone

"Don't change the header" is a perfectly good instruction. The files in the approved plan become the scope lock, so anything else is refused.

5. Use Change plan instead of starting over

If the plan is close but not right, click Change plan and say what to change. A new plan is written and nothing on your computer changes until you approve it.

When a task is too unclear to plan, CodeStilt asks a question instead of guessing. That isn't an error: answer it and you'll get a better plan.