Skip to content
Skills Library
Management & product · Planning

backlog

/backlog

Add a new feature idea to the product backlog. Use when the user wants to log a new idea, feature request, or improvement.

Repository
claude-kit ↗
Licence
MIT
Last repository change
07.09.2026

Assessment and security

96/ 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.
Content31 / 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
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Add a new feature idea to the product backlog. Use when the user wants to log a new idea, feature request, or improvement.

Original author description

Add a new feature idea to the product backlog. Use when the user wants to log a new idea, feature request, or improvement.

How it works

  1. Guidelines
Original SKILL.md headings · 36 lines, 276 words
SKILL.md preview
---
name: backlog
description: Add a new feature idea to the product backlog. Use when the user wants to log a new idea, feature request, or improvement.
---

Add a new idea to the backlog. The user will describe the idea as: the invocation request

Follow these steps:

1. **Read the unsorted file**: Read `docs/backlog/unsorted.md` to find the next item number (listed at the top as "Next item number: N").

2. **Read the README**: Read `docs/backlog/README.md` to understand the current horizons, prioritization factors, and existing items — so you can suggest the right placement.

3. **Write the new item**: Append the item to `docs/backlog/unsorted.md` (before the closing note if the file is empty, or at the end). Use the format in [item-template.md](item-template.md).

4. **Increment the counter**: Update the "Next item number" in `unsorted.md` to N+1.

5. **Suggest horizon placement**: Based on the prioritization factors in the README, suggest which horizon this item likely belongs to and why. Format as:

   ```
   **Suggested horizon**: {now / next / later} — {one-line reason}
   ```

   Don't move it there yet — the user will do that during triage.

6. **Commit**: Stage `docs/backlog/unsorted.md` and commit with message: `backlog: add #N — {Title}`

7. **Summarize**: Tell the user:
   - Item #{N} added to `docs/backlog/unsorted.md`
   - Your suggested horizon placement
   - Remind them to run `$triage N` to move it into the right horizon file

## Guidelines

- Keep the description concise but specific — enough context for `$scope` to work with later
- Infer priority from urgency cues in the user's description
- If the user gives a very brief description, expand it into something actionable but don't over-engineer
- If the idea is clearly related to existing items, mention them in "Related items"
- Don't modify any horizon files — unsorted items stay in unsorted.md until the user triages
Files in this package (3)
  • SKILL.md 2 KB
  • item-template.md 1 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · ajyadav013/claude-kit96MIT
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 ac17bf789785 (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

  • 100jira-feature-request
    Create Jira feature request tickets (Stories) in the CI project using Dimagi's form 134 format. Use this skill whenever a user wants to submit, log, or create a feature request, new feature idea, product enhancement, or user story in Jira. Triggers on phrases like "create a…
  • 100dex-improve
    Workshop one improvement idea into an implementation plan. Use when the user says 'let's flesh out idea-X', 'turn this into a plan', 'improve Dex's Y'. Not for ranking the whole backlog; use `dex-backlog`. Not for a PRD for the user's own product; use `product-brief`.
  • 100capture
    Use whenever the user wants to dump an idea, bug, or feature into the backlog FAST — no conversation, no questions, no refinement. This is the quick-jot entry point: the user is offloading a thought and wants to keep moving, not think it through. Triggers on phrases like…
  • 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.
  • 100shape-it
    Turn a product idea, MVP, or new feature into a scoped plan and an implementable backlog of vertical slices with acceptance criteria. Use this whenever the user wants to design, scope, shape, plan or "think through" an MVP, a new product, a new feature, an epic, or says things…
  • 81task_create
    Create exactly one new task file for one upcoming work item. Use when the user asks to make, add, file, write, or capture a single task or todo. Use task for listing, querying, updating, archiving, linting, or multi task backlog work.

Feedback and reports

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