← ClaudeAtlas

recursive-spine-nudgelisted

Use after a recursive-spine-digest sweep to select and deliver system-initiated nudges — 0–3 conversation-starters pushed to the owner about what is unblocked, aging, stalled, or newly connected. Every nudge ends in a question; the skill proposes conversations, never executes work.
slopstopper/recursive-spine · ★ 1 · Code & Development · score 57
Install: claude install-skill slopstopper/recursive-spine
# recursive-spine: nudge The digest reports; the nudge starts a conversation. This skill is the initiative organ of the collaborative loop (#47): it may only propose, shaped so that autonomy is structurally impossible — a nudge that cannot end in a question to a human is dropped, whatever its rank. ## Configuration (read, never assume) From the invoking context or the private hive's `nudges/config.md`: delivery destination (Slack DM, issue comment, or file), tracking issue, ledger location, age thresholds. From the dialect note of the invoking repo: board owner, repo set. Never hardcode any of these. Nudge state is private-scope: ledger and config live in the private hive, never in a public repo. ## Inputs 1. **The sweep** — run or receive a recursive-spine-digest sweep (aging deferrals, stalled milestones, in-flight by lane, assigned-but-untouched, honest denominators). 2. **Dependency reading** (new sensing) — per repo, find items that became unblocked, by two readings: - **Query (preferred):** for issues with sub-issues (mechanics in `${CLAUDE_PLUGIN_ROOT}/reference/sub-issues.md`, Read a tree), the sequence head is the first open child in sub-issue order whose earlier siblings are all closed. Verifiable structure. - **Prose (fallback):** issues whose recorded sequencing ("sequenced after…", "blocked by…", milestone ordering, lane position) names predecessors that are now all closed — for sequences not yet converted to sub-