7. Plan the work
Now you write the tasks, in one sitting. Milestones are made here. Allow an hour or two.
You start with: a locked direction, and explorations at done.
You finish with: milestones and change tasks on the board, and all other work in the inbox.
#The steps
#Press New, and paste the plan prompt
Change the ids to your explorations.
Plan the work
The session shows you the list before it writes a file.
Turn [E-001, E-002] into change tasks and milestones. The first milestone gives one person one path through the product, from start to end. Each later milestone adds one thing that a person can do. Each task fits in one pull request, and gives its milestone and depends_on. Show me the milestones and the list of tasks first, and change them with me. Then write the files. Work that is not in a milestone goes to the inbox.#Check the list
Do not accept the first list. Check these things:
Check Why Can one person use the product at the end of the first milestone? You see it work early, even if it is small. Does each milestone add something that a person can do? "Set up the database" is not a milestone. Does each task fit in one pull request? A large pull request is hard to review. Does anything go past the non-goals? The agent tells you. You choose. Is each dependency real? A false one blocks work for no reason. Cut. Each task that you move to the inbox is a task that you can still do later.
#Let it write the files
Say yes when the list is right. Type
/exitwhen it is done.You should see: a progress bar above the board for each milestone, and cards in Draft.
#Probe the first milestone
Click a progress bar to show only that milestone. Press Probe on each card, in order, and answer its questions. Do not probe later milestones yet, because what you learn will change them.
#You are done when
- The first milestone has its tasks at
ready. - The inbox holds what you cut.