Add next-tasks skill (backlog assessment + NEXT_TASKS.md maintenance)#234
Merged
Conversation
Codifies the workflow for answering "what's next?" accurately: reconcile NEXT_TASKS.md against what actually shipped (merged PRs, git log, open issues/PRs) before relaying it, classify each item as done / pending- actionable / in-progress / upstream-blocked, surface a short prioritized menu with a recommendation, and keep NEXT_TASKS.md honest (mark done items with PR + date, log new threads, bump the reconcile date, flag cross-Mech sync). Invocable as /next-tasks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
next-tasksskill (invocable as/next-tasks) that codifies thebacklog-assessment workflow run repeatedly this session.
Why
Answering "next tasks" well means reconciling
NEXT_TASKS.mdagainst realityfirst — the file drifts: pending items get shipped in PRs, whole new threads
(e.g. the causal-graph curation capability) never get logged, and some items are
upstream-blocked and will never be actionable here. Reading the file verbatim
gives a stale, misleading answer.
What the skill does
log, and open PRs/issues — and spot-check that referenced slots/recipes still
exist.
(has an open PR/branch), or UPSTREAM-BLOCKED (keep, but never recommend).
NEXT_TASKS.mdevery invocation — mark done items with PR +date, log new threads with cold-start context, bump
Last reconciled:, flagcross-Mech divergence.
Notes
category: workflow; no script, no network, no DB — pure read + reason +maintain.
via
git add -flike the sibling skills (.claude/is otherwise gitignored).Most skills invoke directly as
/<name>, so no.claude/commands/wrapper isneeded.
🤖 Generated with Claude Code