backlog — community backlog, avaris-ai, community, ide skills

v1.0.0

About this Skill

Ideal for Project Management Agents requiring structured backlog organization and prioritization capabilities. Creates and manages product backlog markdown files with epics, user stories, technical stories, bugs, and spikes. Use when creating backlogs, adding epics/stories/tasks, updating story status, or when

Emz1998 Emz1998
[0]
[0]
Updated: 3/5/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
38
Canonical Locale
en
Detected Body Locale
en

Ideal for Project Management Agents requiring structured backlog organization and prioritization capabilities. Creates and manages product backlog markdown files with epics, user stories, technical stories, bugs, and spikes. Use when creating backlogs, adding epics/stories/tasks, updating story status, or when

Core Value

Empowers agents to create and maintain a hierarchical backlog using Markdown files, leveraging epics, stories, and tasks with global sequential IDs, and implementing priority levels such as Must have, Should have, and Nice to have, all within a structured `backlog.md` file.

Ideal Agent Persona

Ideal for Project Management Agents requiring structured backlog organization and prioritization capabilities.

Capabilities Granted for backlog

Organizing project tasks into epics and stories
Prioritizing features using Must have, Should have, and Nice to have levels
Generating and maintaining a structured `backlog.md` file for efficient project management

! Prerequisites & Limits

  • Requires access to project specifications for context
  • Tasks must be created at sprint level, not in the backlog
  • Global sequential IDs must be maintained within each prefix

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is backlog?

Ideal for Project Management Agents requiring structured backlog organization and prioritization capabilities. Creates and manages product backlog markdown files with epics, user stories, technical stories, bugs, and spikes. Use when creating backlogs, adding epics/stories/tasks, updating story status, or when

How do I install backlog?

Run the command: npx killer-skills add Emz1998/avaris-ai/backlog. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for backlog?

Key use cases include: Organizing project tasks into epics and stories, Prioritizing features using Must have, Should have, and Nice to have levels, Generating and maintaining a structured `backlog.md` file for efficient project management.

Which IDEs are compatible with backlog?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for backlog?

Requires access to project specifications for context. Tasks must be created at sprint level, not in the backlog. Global sequential IDs must be maintained within each prefix.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Emz1998/avaris-ai/backlog. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use backlog immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

backlog

Install backlog, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Goal: Create and maintain a structured backlog.md file at project/workflow/backlog.md using the template at template/backlog.md.

Instructions

  • Read project specs for context before creating or modifying the backlog
  • Hierarchy: Epics (EP-NNN) contain stories (US-NNN, TS-NNN, BG-NNN, SK-NNN). Tasks (T-NNN) are created at sprint level, not in the backlog
  • All IDs are global and sequential within their prefix
  • Use priority levels: Must have, Should have, Nice to have
  • Spikes reference which story they unblock
  • Bugs reference the story they were found in (if known)
  • A story can only belong to one epic
  • Stories that don't fit an epic go in Tech Debt / Infrastructure or Bug Backlog sections

Workflow

  1. Read project specs for context:

    • Product Brief: project/docs/product/product-brief.md
    • Architecture: project/docs/architecture/architecture.md
    • Coding Standards: project/docs/architecture/coding-standards.md
    • Definition of Done: project/docs/governance/definition-of-done.md
    • Decisions: project/docs/architecture/decisions.md
  2. Read the backlog template: template/backlog.md

  3. Check if backlog.md exists at project/workflow/backlog.md. If not, create it from the template.

  4. Create or update the backlog following the template structure:

    • Fill the Epics Overview table with all epics and their priorities
    • Fill Epic Details sections with stories for each epic
    • Populate Tech Debt / Infrastructure and Bug Backlog as needed
    • Move completed stories to the Completed table
  5. Provide summary report to the user

Rules

  • Most stories should be independent per INVEST principles
  • Avoid dependencies between stories as much as possible
  • Do not add task-level detail to the backlog; that belongs in sprint planning
  • Must have bugs take priority over Should have stories in the next sprint
  • Reprioritize at every sprint close based on Scrum Master recommendations
  • Stories use their type-specific format (US/TS/BG/SK) matching sprint.md conventions

Acceptance Criteria

  • Backlog follows the exact structure from template/backlog.md
  • All IDs follow correct patterns (EP-NNN, US-NNN, TS-NNN, BG-NNN, SK-NNN)
  • Each epic has a description, priority, and status
  • Stories use the correct format: "As a [user], I want [what] so that [why]"
  • Priority legend, status values, and ID conventions match the template
  • Epics Overview table accurately reflects current counts and statuses
  • File written to correct path: project/workflow/backlog.md

Related Skills

Looking for an alternative to backlog or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer