Skip to content

The Machine: Writing the plan rather than presenting it slows the machine #787

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stack72 merged 1 commit into from
Mar 20, 2026
Merged

The Machine: Writing the plan rather than presenting it slows the machine #787

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,15 +100,6 @@ imports before they can run. See `src/cli/commands/data_get_test.ts` for the
pattern (`await initializeLogging({})` and
`import "../../domain/models/models.ts"`).

## Output Conventions

- When asked to produce a plan, design, or analysis, persist it to
`plans/<descriptive-name>.md` — the file is the source of truth.
- When asked for a plan or design only, produce only that artifact. Do not write
production code or make implementation changes unless explicitly asked.
- When exploring a codebase, produce a first draft of output within 3-4 tool
calls. Refine iteratively rather than front-loading all exploration.

## Session Learnings

If you hit a non-obvious problem during a session — something that wasted time,
Expand Down
Loading