跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

graduate-backlog

Graduate a project's in-repo backlog (roadmap phases, sprint deliverables, ADRs) onto a forge issue tracker at a thin-hybrid default, once the backlog outgrows a single contributor. Use when a team needs to see and claim work that currently lives only in docs/roadmap and docs/sprints, when a repo has a mature in-repo roadmap but an empty tracker, when open-sourcing a project, or when deciding what work should stay in-repo versus live on a GitHub, GitLab, Codeberg/Forgejo, or self-hosted internal tracker.

jrjsmrtn · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add jrjsmrtn/project-orchestration-skills --skill graduate-backlog

技能说明


name: graduate-backlog description: Graduate a project's in-repo backlog (roadmap phases, sprint deliverables, ADRs) onto a forge issue tracker at a thin-hybrid default, once the backlog outgrows a single contributor. Use when a team needs to see and claim work that currently lives only in docs/roadmap and docs/sprints, when a repo has a mature in-repo roadmap but an empty tracker, when open-sourcing a project, or when deciding what work should stay in-repo versus live on a GitHub, GitLab, Codeberg/Forgejo, or self-hosted internal tracker. metadata: author: "Georges Martin jrjsmrtn@gmail.com" version: "0.1.34" license: MIT

Backlog Graduation

Bridge a project's in-repo backlog onto a forge issue tracker at the moment the backlog outgrows a single contributor. The orchestration skills author a rich in-repo backlog — docs/roadmap/roadmap.md (phases → target versions → task lists), docs/sprints/*.md (plans/retrospectives), a Nygard ADR sequence, and a Keep-a-Changelog CHANGELOG.md. Once more than one person needs to see and claim that work, they need a tracker — but that transform is manual and uncodified.

This skill performs it conservatively. The default is thin-hybrid: planning stays in-repo, and the tracker holds only incoming/reactive work plus — at most — the current milestone's tactical items. That is light externalization, not a board build-out. A richer board is opt-in (the roadmap-visible level), justified by a real need for roadmap visibility.

The trigger is team scale, not exposure. Graduation is driven by who needs to see the work — the same signal as the t0→t1 tier bump ("more than one contributor"). It is not gated on the Public distribution profile: a corporate team on an internal GitLab needs a board without ever open-sourcing, and a solo public repo may never need one. Exposure gates compliance controls, not work organization. (Workspace decision records: "Distribution-Profile Axis for Compliance Qualification", "Work-Organization Graduation: Thin-Hybrid Backlog Externalization", "Plugin Taxonomy by Lifecycle, Not Exposure" — cited by title because bare numbers would collide with the target project's own ADR sequence, which Phase 3 writes into.)

Establish vs operate. This skill establishes tracker structure from the backlog; incoming-issue (project-maintenance-skills) operates it afterward. Where that plugin is installed it owns the richer contributor-facing setup — issue templates, good first issue, the full triage taxonomy. This skill creates only the minimal labels it needs, so it works standalone in contexts where the maintenance plugin is absent.

When to Use

  • When a project's backlog outgrows one contributor and the team needs claimable work items
  • When a repo has a mature in-repo roadmap but an empty or default-only tracker
  • When deciding the hybrid boundary — what stays canonical in-repo vs what the tracker owns
  • At the public-release go/no-go gate (project-maintenance-skills), deciding how work is organized publicly
  • Re-running incrementally after new phases or sprints land (the skill is idempotent)

Not for: Solo projects with no collaborators — the backlog stays in-repo; say so and stop. Building a heavy Projects-v2 board unless roadmap visibility is an explicit goal. Re-cutting already-shipped work as issues.

Required Inputs

  1. Repository — the forge and owner/repo, auto-detected from git remotes.
  2. Scope — what to run:
    • plan — Phases 1–2: analyze the in-repo backlog and emit the hybrid-boundary decision; no writes (dry run)
    • milestones — Phase 4: seed milestones from open roadmap phases
    • issues — Phase 5: create labels, then issues from current-sprint open deliverables
    • full — Phases 1–6 in sequence: plan → confirm → record the boundary ADR (Phase 3) → milestones → issues → reconcile (Phase 6). Phases 3 and 6 are what produce the skill's headline output and anti-drift rule, so full is the only scope that satisfies this skill's own Validation.
  3. Externalization level (default thin):
    • thin — milestones for open phases + issues for current-sprint deliverables only (default)
    • roadmap-visible — Phase 5b: additionally mirror open roadmap phases as tracked issues, for team and stakeholder visibility of the longer arc

Workflow

Phase 1: Detect Context & Confirm Eligibility

  1. Detect the forge from remotes:

    git remote -v
    
    • github.com → gh
    • gitlab.com / self-hosted GitLab → glab
    • codeberg.org / self-hosted Forgejo/Gitea → tea (the Gitea/Forgejo CLI), or the Gitea REST API

    The hybrid-boundary decision (Phases 2–3, 6) is forge-independent — only the seeding commands in Phases 4–5 branch by forge. See the Forge Command Reference for the per-forge equivalents. A self-hosted GitLab or Forgejo/Gitea instance is a first-class target: point the CLI at it (glab auth login --hostname gitlab.internal.example, tea login add --url …) — the workflow is identical. An internal corporate forge is a normal case, not an exception.

  2. Confirm the backlog has outgrown one contributor. Graduation is triggered by team scale, not exposure — do not check the distribution profile:

    git shortlog -sn --since="6 months ago" HEAD | head
    

    Proceed if any of these hold: more than one recent committer; the project accepts contributions from beyond the maintainer (an open contributor base is a team, whatever the exposure); or the maintainer states that collaborators need claimable work. If it is a genuinely solo project with no collaborators, stop — a tracker adds ceremony without a reader. Say so plainly rather than seeding an audience-free board.

  3. Locate source artifacts (skip gracefully if absent):

    • docs/roadmap/roadmap.md — ph
阅读完整来源 ↗