원클릭으로 Manus에서 모든 스킬 실행

recursive-spine-digest

스타1

포크0

업데이트2026년 7월 17일 17:55

Use when sweeping all recursive-spine-conforming repos for tracking health — aging deferrals (oldest first), stalled milestones, in-flight by lane, assigned-but-untouched issues, and debts named in closing comments but never filed, plus seedling pollen that never transplanted (hive repos). Reports honest denominators; includes the recursive-spine repo itself in every sweep.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

slopstopper

slopstopper/recursive-spine

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

recursive-spine: digest

The board is the live view; this digest is the push signal.

Repo set

Read the board owner and number from the invoking context (or the invoking repo's dialect note — docs/tracking-dialect.md or equivalent), then read the repo list from the Spine board (gh project item-list <N> --owner <BOARD_OWNER>), falling back to the repo set recorded in the dialect note of the repo you were invoked from; the author's founding set (recursive-spine, plumb-line, tokenomics) is the documented default for this installation, with private repos read from the private hive's dialect note rather than named here. recursive-spine ITSELF is always in the sweep — a digest that exempts its own repo is lying about its coverage.

The sweep (per repo, via gh)

Aging deferrals: open issues with the repo's deferral label (deferred or its alias — read the repo's dialect note / tracking section), sorted oldest-first, each with age in days.
Stalled milestones: open milestones with open issues and no issue activity in 21+ days.
In-flight by lane: open assigned issues grouped by lane:* label (omit section if the repo has no lane module).
Assigned-but-untouched: assigned open issues with no events in 14+ days.
Unfiled debts (best effort): recently closed issues whose closing comment contains "debt", "deferred", "follow-up", or "left behind" with no issue reference (#N) in the same comment. Flag for human eyes; do not auto-file.
Seedling pollen (hive repos only): open pollen-labeled issues whose record still says stage: seedling, sorted oldest-first with age in days — pollen that never transplanted is a signal, same as an aging deferral. Omit the section for repos that are not a configured hive.
Stale constraints pins (repos with a constraints file): docs whose constraints-copy: provenance line pins a sha older than the current head of docs/constraints.md, where the doc belongs to a still-open issue — aged like deferrals. (Merged/closed docs stay green by design; recursive-spine-handover pins the constraints sha in each closing record, which is what makes staleness measurable.) Omit for repos without the connective-tissue part.

Spine health (repos that carry the scripts)

If the swept repo has scripts/spine-audit.sh (convention adherence: closed units without handover records, merged PRs citing no issue, branches off the naming convention) and/or scripts/spine-doctor.sh (installation integrity: labels vs the dialect note's record, board membership staleness, stamped parts still present and wired), run them from the repo root and fold their WARN/NOTE lines into that repo's section. Both are report-only and always exit 0 — findings are digest material, never CI failures. If the scripts are absent, say so: "installation predates the health scripts" is a line in the report, not a silent skip.

Depth (macro/micro parents)

When a swept issue has sub-issues (parent/subIssues — mechanics in ${CLAUDE_PLUGIN_ROOT}/reference/sub-issues.md, Read a tree), roll it up and leak by age:

A parent reports as one line with progress and head: #249 Phase 1 — 3/6 children closed, head: #242.
Healthy children stay folded — they do not appear as separate lines.
Any child that individually crosses an aging or stall threshold leaks: it surfaces as its own indented line directly under its parent's, so folding never hides rot.
A child issue encountered in the sweep folds under its parent rather than appearing twice.
If the tree cannot be read, degrade loudly per the reference: report the issues flat and say why.

The report — briefing voice

The report reads like a briefing a colleague wrote: plain language first, evidence after. The data, formats, and honest denominators are unchanged — only the framing is specified here.

Open with "The week at a glance": two to four declarative sentences, in this order — deltas first (newly aging since the last digest, resolved since, crossed a threshold), then the single most attention-worthy item if any, then end with the swept/failed denominator — name the failures if any. A quiet week says so plainly ("Quiet week; nothing newly aging.").

Delta rule: before writing, read the previous digest comment on the tracking issue (one read, no other state). If none exists or it cannot be read as a digest, open with "No previous digest to compare" — never fake a delta.

Every repo section leads with a status from exactly this vocabulary — healthy, aging, needs eyes, sweep failed — in the heading, plus one sentence saying why. A reader who reads only the leads has an accurate picture. The full tables follow each lead as evidence, format unchanged. Then the cross-repo "oldest five deferrals anywhere" table, and the closing honest denominator: repos swept / repos failed (auth, missing label, API error) — a failed repo is a line in the report, never a silent omission. Note that 21/14-day thresholds are defaults, not doctrine. A child issue rolled up under its parent per the Depth section appears only there — never duplicated as a standalone line in the raw lists.

The digest never asks. Question-shaped sentences are the nudge skill's monopoly; every briefing sentence is declarative. Informing is not nudging.

Worked example — delta week:

The week at a glance: #38 aged past a week as a deferral, and #57 resolved since the last digest. One thing needs eyes: Veska_Index_App's Phase-1 milestone has been silent 21 days. Swept 4/4.

plumb-line — healthy

Nothing aging; v0.8.0 has fresh activity. (full deferral/milestone tables follow)

Veska_Index_App — needs eyes

Milestone Phase-1 stalled 21d; #242 assigned but untouched 14d. (tables follow)

Worked example — first run:

The week at a glance: No previous digest to compare. The oldest deferral anywhere is rs#21 (5d); nothing has crossed a stall threshold. Swept 4/4.

Delivery

Channel is configuration, not doctrine: post as an issue comment on a designated tracking issue, write to a file, or send to Slack — whatever the user (or the scheduled runner's config) specifies. Never hardcode.

이 저장소의 다른 Skills

같은 저장소

recursive-spine-scaffold

slopstopper/recursive-spine

Use when a repo has (or is getting) the tracking stamp and needs the rest of its spine — interviews for and stamps up to six parts, each optional: a rules codex with a moments map, an ADR directory, a CI gate skeleton, a session-memory convention, a constraints file with its sha-pinned drift gate, and the loop workflow. Frames + the builder's answers + proven pollen from their hives; nothing invented ships. Offers recursive-spine-bootstrap first when tracking is missing; records every answer, including declines, in the dialect note.

2026-07-221

recursive-spine-handover

slopstopper/recursive-spine

Use when closing a unit of work — an issue is about to close, a PR is about to merge, or a session is ending with its work complete. Assembles the closing record as a comment on the issue: debts filed before the close (principle 4), the pollen question asked, state pointers captured, the down-tier offer made. Previews the comment before posting; degrades loudly when gh or the constraints file is missing.

2026-07-151

recursive-spine-method

slopstopper/recursive-spine

Use when a builder wants to learn or be reminded of the recursive-spine tracking convention — where work state lives (GitHub issues+milestones, never prose ledgers), the five principles, the module system, and how to design a repo's dialect. Pure knowledge; takes no actions.

2026-07-151

recursive-spine-nudge

slopstopper/recursive-spine

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.

2026-07-151

recursive-spine-bootstrap

slopstopper/recursive-spine

Use when installing the recursive-spine tracking convention onto a repo — interviews for modules and dialect, then stamps labels, issue/PR templates, a CLAUDE.md/AGENTS.md tracking section, and cross-project board membership. Idempotent; degrades loudly on missing gh scopes; offers (never forces) plumb-line and tokenomics wiring.

2026-07-111

recursive-spine-pollinate

slopstopper/recursive-spine

Use when something just proved itself in real work and should be carried to other projects — captures it as a pollen record in the builder's hive (registry file + paired issue), or, in pull mode, reads every configured hive and offers relevant transplants into the current repo, recording each transplant back onto the record. Interview-driven hive config; never ships a default hive; routes private-proof pollen to a private hive only.

2026-07-111

name	recursive-spine-digest
description	Use when sweeping all recursive-spine-conforming repos for tracking health — aging deferrals (oldest first), stalled milestones, in-flight by lane, assigned-but-untouched issues, and debts named in closing comments but never filed, plus seedling pollen that never transplanted (hive repos). Reports honest denominators; includes the recursive-spine repo itself in every sweep.