Closes shipped-work journal entries in JellyRock progress and backlog markdown files.
npx skills add https://github.com/jellyrock/jellyrock --skill done-jellyrock
Please help me install this Agent Skill. Skill: done Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/done Command: npx skills add https://github.com/jellyrock/jellyrock --skill done-jellyrock
Manually updating journal entries for shipped work leads to inconsistent progress records, missed signal acknowledgments, and broken tracking of upstream dependencies, creating extra audit work for development teams.
Use the done skill to close the followup entry for the Roku OS compatibility fix you just shipped by passing the keyword "roku os fix".
High-intent search queries and answers about installing and using this skill.
To close journal entries for shipped work, you can use this skill to automatically move completed followup entries from the open list to the recently shipped section in your markdown progress files, maintaining a clean separation of active and completed tasks.
Signal lifecycle management enforces strict rules for auto-managed perpetual signals by acknowledging new upstream versions without marking them complete, while one-off manual signals are marked as completed for historical records, preventing watchlist corruption.
Yes, you can promote the in-flight running cursor to shipped when work lands, which clears the active work tracking in the progress journal and prepares the tracking file for new tasks.
No, the done skill performs edit-only operations on markdown files and does not commit changes to the repository, leaving version control actions to the developer.
The limitation of auto-managed perpetual signals is that they cannot be marked as completed to avoid corrupting the upstream watchlist; they can only be acknowledged for new versions, unlike one-off manual signals which support full completion.
jellyrockAppend structured entries to project journal markdown files with lint validation.
MelvynxGenerate conventional commit messages and push changes to the repository.
ericstilesPromote backlog items into active specs via speckit.specify.
SarthakMishraRecord completed implementation phases in a .journal/ directory with file changes.
