Maintains the agent half of NEXT.md session handoff briefings across solo and team modes.
npx skills add https://github.com/astroville/sprout --skill next-md-astroville
Please help me install this Agent Skill. Skill: next-md Source: https://github.com/astroville/sprout/tree/main/.claude/skills/next-md Command: npx skills add https://github.com/astroville/sprout --skill next-md-astroville
.hero/NEXT.md or per-user briefings under .hero/next/<user>.md with a shared team roster and updates section. - Update discipline rules: Specifies exactly when to overwrite the agent half (intent shifts, blockers, rejected approaches) versus leaving it alone, with a 15-40 line target and 60-line hard cap. - Use Case: After a long debugging session, the agent updates NEXT.md with the real error message, the two approaches that failed, and a runnable next step, so tomorrow's session resumes productively in one read. ## Quick Start Ask the agent to read the current NEXT.md via hero next path and update the handoff briefing with what was just finished and what comes next.High-intent search queries and answers about installing and using this skill.
Write a NEXT.md briefing with sections for the last user ask, what just finished, the next step with a runnable pointer, blockers, and failed approaches. A fresh session reads this file first and resumes without asking what you were doing.
Include the user's last request in their own words, what shipped with commit references, a concrete next step, actual error messages for blockers, and one line per rejected approach. Keep it between 15 and 40 lines and point at artifacts instead of pasting code.
Update only when a fresh session could no longer pick up correctly from the current file: the user's intent shifted, work shipped, a blocker appeared or resolved, or an approach was rejected. Conversational turns and new commits alone do not require an update.
No. The block between the BEGIN and END HERO MACHINE STATE markers is rewritten by the Stop hook on every turn, and any hand-written content there is wiped. The same applies to the per-machine .hero/next/<user>.local.md file.
In team mode each user writes a personal briefing at .hero/next/<user>.md instead of the shared .hero/NEXT.md. The shared file becomes a roster where you update your one-liner status, plus occasional updates only when something affects teammates.
When next.projected is true, NEXT.md is graph-projected and anything hand-written to it is wiped on the next Stop hook. Use the next-handoff-emit skill instead of this legacy workflow.
uzumaki-incInstall the gbrain CLI, initialize a local brain, and register MCP.
nhouseholderResume paused tasks at the exact point of interruption without re-reading context.
mst-software-vnSearch, create, and organize Markdown notes in an Obsidian vault using wikilinks and index notes.
sylvandingBuild type-safe LLM applications in Ruby with Sorbet signatures.