BD work-backlog-item
Use when creating, grooming, planning, or closing a backlog item. Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend. Activates on interactive browsing with no arguments, loading an item by issue reference or title match to run grooming and SAM planning, autonomous unattended runs that substitute evidence-derived decisions for clarifying questions, a quick path for one-file fixes where full grooming is disproportionate, dismissing an item without completion under a required reason (duplicate, out of scope, superseded, wontfix, blocked), marking an item done with an evidence trail and required summary, or initializing GitHub tracking infrastructure for a project. Stops when the item already has a plan or is blocked on missing information.
Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend.
As a process D 36/100 · Unfinished process — References files that are not bundled: ../../docs/backlog-lifecycle.md, references/workflows/*.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/workflows/close/start.md:90High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)2. Use the plan address from the matched item (the full filename stem, e.g., `Pe9f…aps`). Do not extract or truncate — the full stem IS the address. Call:
detector
Files scanned: 44. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../docs/backlog-lifecycle.md - warning
missing-refreference to a missing file: references/workflows/*.md
Process rating: all ten parameters 36/100
- 0Tools and files. 2 referenced file(s) missing: ../../docs/backlog-lifecycle.md, references/workflows/*.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 5 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4236 tokens
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 809: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 6 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.