Skip to content

Huruikagi/pc-build-planner / .agents/skills/sb-discovery

sb-discovery

Verified

Turn a change request or Source Collection into confirmed Spec and milestone boundaries.

FileKindSize
SKILL.mdskill md2.0 KB
agents/openai.yamlconfig202 B
references/github-milestone.mdmarkdown7.3 KB
references/local-files.mdmarkdown3.1 KB
references/ordinary.mdmarkdown24.9 KB

references/github-milestone.md

View on GitHub
# GitHub Milestone Source Collection

Use this procedure only when the maintainer explicitly supplies canonical
`OWNER/REPO` and a Milestone number, or exactly
`https://github.com/OWNER/REPO/milestone/NUMBER`, as Discovery input. The URL
form is a complete explicit selector: parse its owner, repository, and decimal
Milestone number before acquisition, then use them exactly as if they had been
stated separately.

Accept no other URL shape. A different host, missing component, extra path,
query, fragment, percent-encoded path component, or non-decimal number stops
for clarification. Do not search, normalize, redirect, or infer identities from
a near match or a similarly named Milestone.

Read the shared semantic contract once before acquisition:

```sh
specbind protocol read source-material
```

## Acquire one complete, read-only snapshot

Prefer an available authenticated GitHub integration. Use it only to read the
selected repository, numbered Milestone, and every entry assigned to that
Milestone. If no such integration is available, use authenticated `gh` as the
fallback. Verify authentication first and stop on failure:

```sh
gh auth status
gh api repos/OWNER/REPO
gh api repos/OWNER/REPO/milestones/MILESTONE_NUMBER
gh api --paginate --slurp 'repos/OWNER/REPO/issues?milestone=MILESTONE_NUMBER&state=all&per_page=100'
```

Replace only the explicit identities parsed from the separate input or exact
URL; do not turn these read commands into a write. The `--paginate --slurp`
result is one logical inventory: retain every
page and stop if any page is unavailable or cannot be accounted for. Confirm
that the returned canonical repository and numbered Milestone match the request.
A missing, inaccessible, or ambiguous identity is partial acquisition, not an
empty collection.

Before reading content, inventory every returned entry. For each record:

- retain stable repository identity and URL, Milestone number, title, and URL;
- retain entry number and URL, title, state, and observed update time;
- identify an entry with `pull_request` metadata as a non-Issue item; and
- read an Issue body only when it is an actual Issue and needed for
  classification.

Do not read comments or timeline events. Labels, state, author, assignees, and
Milestone metadata are routing evidence, never automatic ownership or
specification authority. Do not issue any GitHub mutation command.

Report every known inaccessible, unsupported, duplicate, excluded, non-Issue,
or unresolved entry together. An inaccessible Issue, incomplete pagination, or
other partial acquisition stops before classification, Gate invalidation,
milestone mutation, or Brief authoring. Do not continue with the entries that
happened to work.

## Classify with complete Issue coverage

Treat each actual Issue as request context and apply the entry and ownership
rules from [ordinary change Discovery](ordinary.md). Several Issues may inform
one work item; one Issue may inform several Specs. Do not create a Spec per
Issue. A pull request or another non-Issue entry remains visible as excluded
with its reason.

The confirmation payload keeps the ordinary four fields and adds:

```text
Source coverage: <OWNER/REPO; Milestone number/title/URL; every Issue and
non-Issue entry; observed update time; included, excluded, duplicate, or
unresolved disposition; relevant work items; and one-line reason>
```

An unresolved item means the proposal is not approvable. Ask the maintainer to
settle it before changing state.

## Bind a version-shaped Milestone title

Use the acquired title as the default release label when the **whole title**
matches both the portable label grammar (1–64 ASCII characters,
`^[A-Za-z0-9][A-Za-z0-9._+-]{0,63}$`) and this conservative version shape:

```regex
^v?[0-9]+(?:\.[0-9]+)*(?:-[0-9A-Za-z]+(?:[.-][0-9A-Za-z]+)*)?(?:\+[0-9A-Za-z]+(?:[.-][0-9A-Za-z]+)*)?$
```

Examples include `v1`, `1.4`, `v1.4.0`, `1.4.0-rc.1`, `1.4.0+build.7`,
and `2026-09-06`. This is title recognition, not SemVer validation or ordering.
Preserve the exact title: do not trim it, extract a version from prose, remove
or add `v`, or change case. `Release v1.4.0`, `Backlog`, and `release_42`
do not select a default; continue Discovery without asking for a version or
changing the existing binding. A maintainer-supplied release label takes
precedence over the title default and uses the ordinary portable label grammar.

Include the proposed exact `target_release` and its title provenance in
`Source coverage`, alongside the current binding when one exists. Initial
binding needs no separate version question: the ordinary scope confirmation
also confirms this visible default. An identical existing binding is a no-op.
If a different non-null binding exists, show both values and obtain explicit
agreement to replace it before using `--rebind`; scope approval alone does not
authorize that replacement. Never silently overwrite a conflicting binding.

After the confirmed scope succeeds (including unchanged scope), finish all
Briefs and the ordinary step 8 checkpoint **before binding**. The CLI refuses
to bind a dirty, staged, or untracked Roadmap. The complete scope and Brief
capture is eligible for that checkpoint even while this confirmed binding is
pending. Do not commit a partial capture merely to unblock binding.

Then apply the confirmed label through the CLI:

```sh
specbind milestone bind-release <version>
```

Use `--rebind` only for the explicitly confirmed replacement above. Never write
`target_release` directly or put it in the scope candidate. Stop on a binding
error, preserve the successful scope mutation, and report the outstanding
binding; do not invent another label or claim Discovery is complete. Read
`specbind milestone status` back to verify and report the exact bound value.
After a successful bind or rebind, follow the same Git adapter for a second
narrow checkpoint containing only the Roadmap's binding change. An identical
binding needs no extra checkpoint. "Stop after Discovery" includes both
checkpoints when the adapter directs them; no additional permission is needed.

If the adapter is absent, empty, scaffold-only, or forbids commits, do not
invent checkpoint authority. If the Roadmap is dirty, report the completed
capture and pending binding that needs a project checkpoint, then stop. If the
Roadmap is already clean, binding may proceed; report any resulting uncommitted
binding without claiming a checkpoint. Never commit unrelated changes or bypass
the CLI's clean-target guard.
This binds local release metadata only; it does not publish or mutate GitHub.

## Preserve the capture

When creating the Roadmap, fill the selected body with complete GitHub
provenance and coverage mapping as well as ordinary request, decomposition, and
dependency rationale. With an active milestone, read it with
`specbind milestone scope --include-body` and merge the mapping into complete
current prose.

For each Spec-backed Brief, name only the exact Issue URLs and observed metadata
relevant to that Spec, and state why each matters. A shared Issue appears in
every relevant Brief. Direct items still have no Brief. Do not paste a complete
Issue collection into every Brief.

The Brief is the approved remote request context for later planning. Requirements
and Design promote its captured meaning into canonical artifacts; they do not
silently re-query GitHub or let a later Issue edit reinterpret approved work.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall