Documentation
README
Generate an implementation spec
Write a spec in specs/ that an engineer can implement without repeating the research. Keep it lean, grounded in the current code, and focused on the requested result.
Research the change
- Read the request and repository instructions.
- Find the entry points, key types, state boundaries, callers, tests, and commands tied to the change. Trace each changed runtime path far enough to show an accurate diff.
- Read external docs only when a dependency or API affects the design. Prefer official docs and record the links used.
- Ask a question only when the answer would change the result and the code cannot answer it. Otherwise, make the narrowest sound assumption and record it.
This is the opening of the README. Read the full README on GitHub.