Sprints.

One object, many names

Teams call this box different things — a focus, a sprint, a cycle, an iteration, a week. In Weft they all mean the same object, and your workspace can display whichever word fits how you work. The MCP tool names always say sprint (create_sprint, get_active_sprint, …) and are frozen on purpose: whatever word your board shows, the tools your AI calls never change.

Lifecycle

A sprint moves through four states. Planning, starting and completing each have an MCP tool; archiving is a tidy-up you do from the app.

• Planned. Created via create_sprint. Has a name, optional goal, optional start and end. Can hold tasks.
• Active. Promoted via start_sprint. One sprint is active at a time — Weft enforces this on every plan. Starting a second one fails and names the running sprint; complete it first, then start the next.
• Completed. Closed via complete_sprint. Finished tasks are archived into the sprint's history — they leave the board's Done column but stay searchable and visible on the sprint's page. Unfinished tasks stay on the board.
• Archived. Archive a completed sprint from its page when the list gets long. Archived sprints hang around for reporting — you rarely touch them directly.

How long should a sprint be?

Short answer: one to two weeks. The Scrum Guide fixes Sprints at one month or less, and notes that shorter Sprints generate more learning cycles and limit the risk of cost and effort to a smaller time frame. Long enough to ship something meaningful, short enough that a blown plan is recoverable by next sprint. For solo founders, shorter (five to seven days) usually works better — your context window is shorter than a team's.

Empty vs focused sprints

An empty sprint (“this week”) is not a sprint — it is a calendar. A focused sprint has one goal that names the outcome: “ship the landing”, “launch on Product Hunt”, “get the first ten paying customers”. Everything else in the sprint serves the goal.

Completing a sprint

Completing is the sweep: everything you finished moves off the board into the sprint's history — archived, not deleted, so search and the sprint's page keep the record (the free plan remembers 30 days of archive; Pro remembers everything). Archived work doesn't count toward the free task cap, so finishing a sprint frees space on the board. Tasks you did not finish stay on the board. Next sprint you can pull them back in with add_task_to_sprint, or leave them in the Backlog if priority moved on. The loom is durable; the sprint is the disposable container.