Repository navigation
docs: explain how ~go works through a plan and where the modes live - #77
Merged
Merged
Conversation
The README quick start now says what ~go does: it works through the plan one task at a time (implement, verify, review, then check it off), pauses for missing facts or your decisions, and after an interruption or handover continues with the next unfinished task that can proceed. The command cheat sheet drops routing jargon, and the pages follow. How Sopify Works gains a short "Task loop and modes" section covering the retry and blocking rules, when receipts are written, and the four separate mode dimensions (request intent, workflow.mode, plan level, interaction). The example config lists the current plan levels instead of the retired background/design/tasks and "full" layouts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs-only follow-up to #76 (no release needed).
~godoes: it works through the plan one task at a time (implement, verify, review, then check it off), pauses for missing facts or your decisions, and after an interruption or handover continues with the next unfinished task that can proceed. The cheat sheet drops routing jargon; the pages follow.workflow.mode, plan level, interaction).Facts were checked by Codex against the code and protocol; wording was reviewed by Gemini. 422 tests pass locally.
🤖 Generated with Claude Code