print-next
Skill1 starsChanged 2 months agoMITView on GitHub
Print the current paste-ready NEXT fence from disk after updating living handover/roadmap. Use ok next (or Read the handover) — never paste from memory or an open tab. Required on every closeout that touches those docs.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/build-verification-required.mdcCursor rule
- .cursor/rules/check-ok-thinking.mdcCursor rule
- .cursor/rules/governance-sync.mdcCursor rule
- .cursor/rules/l1-checkpoints-consumer-owned.mdcCursor rule
- .cursor/rules/no-docs-only-pr-to-main.mdcCursor rule
- .cursor/rules/orchestrator.mdcCursor rule
- .cursor/rules/print-next-closeout.mdcCursor rule
- .cursor/rules/tier-authority.mdcCursor rule
- .cursor/rules/workspace-authority.mdcCursor rule
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- freeze-reviewSkill
- governance-syncSkill
- print-nextSkill
- workspace-statusSkill
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- freeze-reviewSkill
- governance-syncSkill
- knowtationSkill
- workspace-statusSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
After any update to the living handover and/or roadmap, the agent’s FINAL reply MUST include the full paste-ready fence under heading ## …
- Very specific: line 12
MUST include the full paste-ready fence under heading ## CURRENT NEXT — paste this.
- Very specific: line 17
Prefer native editor tools (Cursor StrReplace/Write.
- Distinctive: line 33
Never whatever the open tab happens to show
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Print NEXT (closeout)
After any update to the living handover and/or roadmap, the agent’s FINAL reply
MUST include the full paste-ready fence under heading ## CURRENT NEXT — paste this.
Bytes MUST come from read from disk after write (run ok next, or Read the
handover file and extract the ### Paste-ready prompt fence). Do not paste from
memory, from an earlier chat, or from an unsaved editor buffer. Session incomplete without it.
Prefer native editor tools (Cursor StrReplace/Write; Claude Code Edit) for
handover/roadmap so the host is more likely to refresh an open tab. That preference is
best-effort and does not replace ok next. Host niceties do not guarantee an accurate open tab.
Fast path
ok next
# synonym:
ok governance-sync --print-nextSource of truth order
ok next/ the printed CURRENT NEXT fence (this session, after the write)- The handover file on disk at the config-driven path
- Never whatever the open tab happens to show
Not this command
ok workspace check-next is constellation relay freshness (exit 35). Do not alias
it to ok next.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

