Skip to content
Skills Library
Management & product · Planning

backlog

/backlog

Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.

Licence
Apache-2.0
Last repository change
28.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.

Original author description

Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.

How it works

  1. Contract
  2. Inputs
  3. Procedure
  4. Failure and recovery
  5. Output
Original SKILL.md headings · 38 lines, 644 words
SKILL.md preview
---
name: backlog
description: 'Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.'
disable-model-invocation: true
---

# Backlog

## Contract

| Field | Bound contract |
|---|---|
| Trigger | User wants to park an undecided idea without representing it as decided or active work. |
| Authority | Reversible local: writes only one backlog entry file; rollback is deleting or reverting that file. No remote mutation. No VCS commit or credential use. |
| Side effect | One backlog entry as a reversible local state change with recorded evidence. |
| Done | The idea is parked in the backlog and ready to be promoted when it meets the readiness threshold. |

## Inputs

- Idea statement (required): one or two sentences naming the idea and the problem it would address.
- Undecided reason (required): the specific missing input that blocks a decision now: an unverified assumption, absent evidence, an open question, or a competing alternative.
- Readiness threshold (required): the concrete, falsifiable condition that, when met, would make the idea promotable (a measurement, a resolved question, or a confirmed constraint that yields a yes/no).
- Existing evidence (optional): links, measurements, or notes already in hand that bear on the idea.
- Backlog location (optional): path to the backlog file or directory; default is a `backlog.md` file in the current workspace.

## Procedure

1. Validate the inputs: confirm the idea statement is a single coherent proposal, the undecided reason names a concrete missing input, and the readiness threshold is falsifiable. A human or tool must be able to test it and get a yes/no result. Done when: all three required inputs are validated as coherent, concrete, and falsifiable.
2. Bound scope: this skill only parks the idea. Do not evaluate, rank, or promote it. Do not create tasks, requirements, or tickets. Done when: scope is bounded to parking only with no evaluation, ranking, or promotion.
3. Locate or create the backlog store. If a backlog file exists, append to it; otherwise create one with a header marking it as undecided-parking only. Done when: the backlog store is located or created.
4. Write one entry with the idea statement, undecided reason, readiness threshold, any supplied evidence, timestamp, and a stable identifier. Derive the identifier from the idea statement as a kebab-case slug (lowercase words joined by hyphens, with non-alphanumerics dropped); on collision with an existing identifier, append `-2`, `-3`, and so on. Mark the entry status `parked`. Done when: the entry is written with all fields and marked `parked`.
5. Record the entry as a reversible local state change: the file write is the only mutation. No commit, push, or remote call occurs. Done when: the entry is recorded as the only mutation with no commit, push, or remote call.
6. Confirm the done predicate: the entry exists, is marked `parked`, and carries its readiness threshold so a later promotion step can test it. Done when: the entry is confirmed present, parked, and threshold-carrying.

## Failure and recovery
- Non-falsifiable threshold: if the readiness threshold cannot be checked with a yes/no outcome, stop and ask the user to restate it as a testable condition. Do not park an entry whose promotion trigger is subjective.
- Idea already decided or active: if the idea is already represented as a task, requirement, or in-progress work, stop. The backlog is for undecided ideas only; parking a decided item duplicates state.
- Write failure: if the backlog file cannot be written, do not mutate any other file. Report the write error and the intended entry content so the user can retry or relocate.
- Partial result: no partial state is valid. Either the full entry is written or nothing is written. A failed write leaves the backlog unchanged.

## Output
One backlog entry in the local backlog store, marked `parked`, carrying its idea statement, undecided reason, readiness threshold, evidence, and timestamp, ready to be promoted by a later decision step that tests the threshold.
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · OutlineDriven/outline-driven-development90Apache-2.0
Ovid/paad100MIT
Ovid/paad100MIT
Ovid/paad100MIT
gtlpanda/PandaStack100MIT
SergioLizana/Dynamo100MIT
bitIO/wheelhouse100MIT
Archont561/qgis-agent-harness100MIT
umputun/cc-thingz100MIT

Database snapshot: 13.11.2026 · package version 6517b3548918 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Backlog Management
    This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md.
  • 100idea-sparkbox
    Use when the user asks to park ideas or inspiration for later. Not for code, backlog, or divergence-class cards, or remote, credential, publish, deploy, or irreversible changes.
  • 100backlog-routing-by-topic
    Route a stray idea that surfaces mid-task to the §Backlog of the right living doc in a spec-phase-orchestration repo (design.md, foundations.md, plan.md, methodology.md, or today's meeting log) as a single line, without derailing the current work. Use when a…
  • 81task_select
    Select and rank eligible live tasks from the project backlog. Use when the user asks what task to work on next, asks the agent to pick or prioritize backlog work, rank open tasks, choose from tasks/, or recommend the next task/action without editing task files.
  • 100backlog-reconcile
    Use to audit a repo's `_meta/BACKLOG.md` Active queue against reality, "audit the backlog", "reconcile the board", "is the board still true", "dọn backlog", "rà soát backlog", or a scheduled backlog-reconcile run. NOT for filing new items onto the board, NOT for a single…
  • 85Backlog.md
    Expert guidance for Backlog.md CLI project management tool including task creation, editing, status management, acceptance criteria, search, and board visualization. Use this when managing project tasks, creating task lists, updating task status, or organizing project work.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.