Point the working loop at the skill's prose-only path and scope its goals exception to the first write
This commit was merged in pull request #5.
This commit is contained in:
@@ -43,7 +43,7 @@ How work proceeds in any repo, unless that repo's `AGENTS.md` says otherwise.
|
||||
- **A release is the human's, and a finished one stops the session.** The version bump and the publishing credentials are the human's whatever any other rule says; prepare everything around it so the release is one decision. Open every session with one line: the last version cut, what is unreleased (`CHANGELOG.md`'s `## Unreleased`, else the log since the last tag), and the release this chunk ships into; a repo that publishes nothing says so once. Where the earliest unreleased release has no items left and work has shipped toward it, that is the terminal state: report what it holds and that it is ready to cut, and stop. A security fix still lands, into the waiting release. Never roll forward into a later release's items, and never plan a new release, while a finished one waits — the bump is the next decision. Under `/loop`, that stop ends the loop.
|
||||
- **One chunk per session**, the smallest PR-able unit; split a milestone into sub-items in `todo.md` before starting it. A finding inside the chunk is fixed in the chunk; outside it, it becomes a `todo.md` item under a release.
|
||||
- **A done item leaves `todo.md`; its release heading stays until the version is cut.** Where the repo publishes something a consumer takes — a package, an image, an API — the line is reworded for that consumer and moves to `CHANGELOG.md` under `## Unreleased`; a CHANGELOG is written for the public, never for the next agent. Everywhere else the line is simply deleted, because git history is already the record.
|
||||
- **Ship every chunk with `/larv-review`**, which carries the review pipeline through to a merged PR. A chunk touching only prose — markdown, docs, comments — skips the reviewer loops: branch, PR, green gate, merge.
|
||||
- **Ship every chunk with `/larv-review`**, which carries the review pipeline through to a merged PR. A chunk touching only prose takes the skill's prose-only path, which keeps the product-owner and prose passes for anything public: a goal change, a README, a CHANGELOG.
|
||||
- **Ask, don't guess — and fix the goals rather than the question.** Before asking, check whether the goals already settle it; where they nearly do, propose the goal change and show what falls out of it for the instance, because one answered question settles one instance and a goal settles the class. Every answer lands where its kind belongs, and nowhere else: a goal in `README.md`, a working rule in `AGENTS.md`, a standing choice in `docs/decisions.md`. Where an answer is more than one of these, the goal wins — write the goal, and record a decision only for what it still leaves open. Never in chat alone.
|
||||
|
||||
## Working with the codebase
|
||||
|
||||
@@ -15,7 +15,7 @@ Verdicts, severities, round caps, declining a finding and where decisions are re
|
||||
|
||||
- Not a git repo → say so and stop.
|
||||
- Someone else's PR, or the user asked for opinions only → single stability pass, report findings, done (skip shipping, fixing, the loops and the merge).
|
||||
- Prose only — markdown, docs, comments, no code — → the reviewer loops add nothing: ship the branch (§1), the prose pass (§7), green gate (§8), merge (§10). Say so in the summary. Prose an outside reader lands on — public API docs, README, error or deprecation text — still takes §6's product-owner pass. The goals-and-audience chunk is the exception: the human's approval is its whole review, since a reviewer's findings on it could only be declined by citing the goals it exists to write.
|
||||
- Prose only — markdown, docs, comments, no code — → the reviewer loops add nothing: ship the branch (§1), the prose pass (§7), green gate (§8), merge (§10). Say so in the summary. Prose an outside reader lands on — public API docs, README, error or deprecation text — still takes §6's product-owner pass. The chunk that first writes the goals and audience is the exception — a later change to a goal is not: the human's approval is its whole review, since a reviewer's findings on it could only be declined by citing the goals it exists to write.
|
||||
- Issue trackers are project-specific — the project's own docs say whether it has one. When it does and the work has a ticket, follow that tracker's conventions for assignment and status.
|
||||
- The repo states its goals and audience under literal `## Goals` and `## Audience` headings in `README.md` — the global working loop gates all planned work on it. Neither heading present, or a version too vague to settle a decision → this chunk cannot be judged against them: stop, say so, and write them with the user as the chunk instead. The same content in `AGENTS.md`, in `docs/` or in a decision log does not satisfy it, and neither does an earlier session having passed it; nothing merges and nothing is reported done while it is unmet. Only what the global working loop lets past that gate reaches review without them.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user