Refine proposed Plans and draft tasks

Refine a Building Task Builder Session until its proposed Plans and draft tasks describe the organization and work you want to publish. Changes happen through your local AI conversation and the CLI; the Task Builder website shows the resulting structured plan for review.

Ask your local AI tool to follow the repository guidance for the supported session and draft changes.

1. Ask your local AI tool to select the Building session you want to refine.
2. Ask it to add or revise proposed Plans and draft tasks, assign tasks to Plans or leave them Standalone, then set labels, dependencies, and display order.
3. Open the Building session in Task Builder and inspect the updated Plans, empty Plans, assigned tasks, and Standalone tasks.

Expected result: the session remains Building and contains the proposed Plans and draft tasks you want to review before publication.

Ask your local AI tool to update the session title or summary when the plan’s purpose has changed or needs more context. Keep the session in Building while you revise it.

You can select a different Building session as the active local session, or identify a specific session in a command. If the selected session was published or is no longer available, select a current Building session before asking the AI tool to make changes.

Ask the AI tool to create proposed Plans for useful workstreams or outcomes. A proposed Plan has a stable ID, title, optional Markdown, labels, and zero or more member tasks. Empty Plans are valid, so the AI can establish a grouping before its task breakdown is complete.

Assign or move a draft task with stable task and Plan IDs. Clear the assignment when the task should be Standalone. Plan membership is organization only: it does not order tasks or create dependencies.

Removing a proposed Plan does not remove its tasks. Every former member becomes Standalone, and the remaining Plan display positions compact.

Ask the AI tool to add, remove, or revise draft tasks. A useful draft task has a clear title and Markdown that explains the expected result. Add Mass when it helps size the task using the project’s existing sizing field.

Mark a draft excluded from metrics to record that its eventual published task should be omitted from task-derived metrics. The CLI can set the choice when adding the draft or change it independently later with task-builder task set-metric-exclusion; publication preserves the choice. Current metric reports do not apply the persisted choice yet.

Set labels to make the planned work easier to find after publication. Labels must be available to the project; unavailable, conflicting, or ambiguous labels need to be corrected before publication.

Keep unrelated and related task ideas in the same session when that makes them easier to review together. Their display order is for review, not an execution order.

Add direct dependencies when one draft must be completed before another can start. Dependencies use stable draft IDs, not display positions. A draft cannot depend on itself, duplicate a dependency, refer to an unavailable draft, or create a cycle.

Reorder draft tasks when a different presentation makes the session easier to review. Task positions are session-local and mutable. Reordering does not change dependencies, and it does not create an execution order.

Use the session number when discussing or selecting a Task Builder Session. Use a stable proposed Plan ID when changing Plan content, labels, or task membership. Use a stable draft ID when changing a particular draft task. Save IDs returned when Plans and tasks are added, or get them from the session’s detailed CLI output.

Do not treat a Plan or task position as an ID. Positions are session-local display context, while stable IDs remain the reliable mutation references.

Open the Building session in Task Builder and inspect the updated summary, proposed Plans, empty Plans, assigned and Standalone draft tasks, labels, dependencies, and order. When the complete set looks right, review its readiness and publish it.