docs: fix README headline — spec-driven framing, plain language#112
docs: fix README headline — spec-driven framing, plain language#112PatrickSys wants to merge 1 commit into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the README to reframe the project around spec-driven development and persistent markdown files. The feedback identifies an inconsistency in the package.json description that should be addressed to match this new framing and provides a grammatical correction for the updated README text.
| # Workspine | ||
|
|
||
| AI agents forget when the session ends. Workspine writes plans, decisions, and verification to `.planning/` so any agent or runtime can pick up where the last one stopped. | ||
| Spec-driven development for AI-assisted work. The spec, plan, and verification live as markdown files in your repo — so every session starts from the same ground truth instead of a blank chat window. |
There was a problem hiding this comment.
The PR summary mentions removing the "repo-native delivery spine" framing, but this terminology (and the "repo-native" buzzword) still persists in the package.json description. To ensure consistency with the new spec-driven framing, please update the description field in package.json as well.
| ## Where it fits | ||
|
|
||
| Use Workspine when a feature takes more than one session, or when you need to switch between Claude, Codex, and Cursor without losing the thread. Skip it for quick, obvious edits — direct prompting is cheaper when the risk is small. | ||
| Use Workspine when a feature takes more than one session, or when you keep switching between Claude, Codex, and Cursor and losing the thread. Skip it for quick obvious edits — just prompting is faster. |
There was a problem hiding this comment.
The phrasing "and Cursor and losing the thread" is slightly clunky due to the repeated conjunction. Additionally, "quick obvious" should be separated by a comma as they are coordinate adjectives modifying "edits".
| Use Workspine when a feature takes more than one session, or when you keep switching between Claude, Codex, and Cursor and losing the thread. Skip it for quick obvious edits — just prompting is faster. | |
| Use Workspine when a feature takes more than one session, or when switching between Claude, Codex, and Cursor causes you to lose the thread. Skip it for quick, obvious edits — just prompting is faster. |
1 participant
Summary
What changed and why
The previous README still led with corporate-sounding language ("delivery spine", "any agent or runtime") that obscured what the tool actually is: markdown files in the repo that give AI agents a consistent spec to follow across sessions. This rewrite leads with that honestly.