Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with independent refactoring, delivery, and asynchronous CI repair. Use to…
Dough Land lands everything in one reviewed checkout on the authorized remote trunk: commits all of its changes, reconciles and publishes them without force, and refreshes a supplied default checkout when safe. An owned worktree is retired with its branch…
Clarifies selected stories before execution planning by establishing goal, scope, and key examples in each story's seed, distinguishing promises from rejection constraints. Adds UI or architectural detail only when needed. Continues a ready story into slice…
Refines an executable plan in place into proportionate, proof-owned Behavior/Structure slices. Use during or after dough-slice-planning when boundaries fragment cohesive work, combine independent concerns, accumulate special cases, or overrun. Creates no new…
Plans one understood, bounded story, retrospective correction, or remaining work from an understood instruction as an executable sequence of Behavior/Structure slices with outside-in proof and safe stopping points. Use when a selected story is ready for…
Maintains and reprioritizes a product backlog list of canonical story or bounded-correction references, and records necessary blocking story dependencies in canonical homes. Use to add, take, reorder, or complete backlog items, adopt or repair the done…
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup. Process review is opt-in: it runs only when the project sets…
Apply the latest released Open Dough guidance from this project's recorded source, or from a supplied repository URL on first install. Use when the user asks to update Open Dough or invokes dough-update.
Plans bounded manual or exploratory observation of requested product behavior when the developer explicitly requests manual testing, exploratory testing, or an active plan slice requires it. Covers web, CLI, API, desktop, or combined surfaces. Does not run…
Refactors concepts implicated by the current uncommitted change before commit. Includes untouched representations and orchestration needed for coherence, stops before unapproved cross-subsystem refactoring or disputed plan behavior, and tests only after…
Challenges and decomposes a broad product problem into ordered Valuable/Visible/Vertical stories with rough effort hypotheses. Use when the parent problem, candidate stories, or learning priority are unresolved. Writes one non-executable seed.