تشغيل أي مهارة في Manus بنقرة واحدة

recursive-spine-bootstrap

النجوم١

التفرعات٠

آخر تحديث١١ يوليو ٢٠٢٦ في ١٢:٢٩

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.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

slopstopper

slopstopper/recursive-spine

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

المهن الحاسوبية الأخرىمهن الحاسوب والرياضيات·SOC 15-1299

SKILL.md

readonly

name	recursive-spine-bootstrap
description	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.

recursive-spine: bootstrap

Stamp the convention onto the current repo. Read ${CLAUDE_PLUGIN_ROOT}/reference/principles.md first. If the user hasn't seen the convention before, offer the recursive-spine-method skill before stamping.

1. Preflight (fail loud, not silent)

gh auth status — must be authenticated.
gh repo view --json nameWithOwner — must be a GitHub repo.
Board membership needs project scope: run gh auth status and check for project scope. If absent: DO NOT silently skip. Tell the user exactly what's missing (gh auth refresh -s project) and file a repo issue titled "spine: board membership pending (missing gh project scope)" so the gap is a record, not a memory.

2. Interview (one question at a time)

Which modules? Deferral is mandatory (offer alias naming, default deferred). Offer gap / debt / lane with one-line failure-mode pitches. If lane is chosen: ask the builder to NAME their own tiers — offering the tier names found in the repo's tokenomics playbook when one exists. Ship no default lane names — tokenomics' rule; the tiers are the builder's own words.
Dialect: what does this repo call a unit of work? Any existing label conventions to respect?
Board: add this repo to the user-level "Spine" Projects board? (Needs the scope from preflight.)
If the plumb-line plugin is installed (check for a plumb-line-bootstrap skill): offer it for epistemic enforcement — separate concern, their choice. If a tokenomics playbook exists in the repo: offer to point the tracking section at it for lane semantics. Offers only.

3. Stamp (idempotent — re-runs must not duplicate)

Labels via gh label create <name> --description "<desc>" --color <hex> --force (--force updates existing — this is the idempotency mechanism):
- deferral label (chosen name), color D93F0B, desc "Postponed with a record — principle 3".
- if gap module: gap, B60205, "Finding from an assessment".
- if debt module: inherited-debt, FBCA04, "Known-incomplete edge handed over from a closed unit".
- if lane module: lane:<tier> for exactly the tier names the builder named in the interview (never shipped defaults). Color by rank: top tier 1D76DB, mid tier(s) 5319E7, smallest tier C5DEF5 — desc "Model-routing lane". If more than three tiers, note the extra tiers' colors sensibly (e.g. reuse 5319E7 for all middle tiers) rather than inventing new hex values ad hoc.
Copy templates from ${CLAUDE_PLUGIN_ROOT}/reference/templates/: work-item.md and deferral.md → .github/ISSUE_TEMPLATE/ (substitute the chosen deferral label into deferral.md's labels: line); pull_request_template.md → .github/. If a PR template already exists, show a merged proposal — never overwrite silently.
Tracking section: append tracking-section.md (with <DEFERRAL_LABEL> and <DIALECT_NOTE_LINK> substituted) to CLAUDE.md or AGENTS.md — ask which, show the diff, get approval before writing.
Dialect note: write the interview answers to docs/tracking-dialect.md (or the repo's docs convention).
Board: read the board owner and SPINE_BOARD_NUMBER from the target repo's docs/tracking-dialect.md (or equivalent dialect note) if present. If this is the first repo being stamped and no dialect note yet records a board owner, ask the user which account/org owns their cross-project board and record the answer in the dialect note before proceeding. With owner and number known, gh project item-add <SPINE_BOARD_NUMBER> --owner <BOARD_OWNER> --url <repo issue URL> is per-item; for whole-repo aggregation prefer the board's built-in auto-add workflow — open the board settings URL for the user and confirm they enabled it for this repo.

4. Report

End with: modules stamped, labels created/updated (names), files written, board status (added / pending-scope issue #N), and the exact queries the repo now answers (gh issue list --label <deferral> etc.). List anything skipped and why — honest denominator.

If the repo now wants the rest of its spine — rules codex, ADRs, CI gates, session memory — offer recursive-spine-scaffold as the natural next step (offer, not upsell: one line, their choice).

المزيد من هذا المستودع

نفس المستودع

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-digest

slopstopper/recursive-spine

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.

2026-07-171

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-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