speckit-backlog-add

Create standardized Markdown backlog items with slug generation and conflict checks.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-backlog-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-backlog-add
Source: https://github.com/ericstiles/spec-kit-backlog/tree/main/.claude/skills/speckit-backlog-add
Command: npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-backlog-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backlog creation in spec-driven projects is often manual, inconsistent, and hard to track; this skill automates the creation of backlog items in specs/backlog with a standardized template to improve consistency and routing.

Core Features & Use Cases

  • Standardized templates: generates a Markdown file at specs/backlog/{slug}.md with Overview, Problem Statement, and Acceptance Criteria.
  • Slug generation & conflict detection: converts the backlog title into a safe filename and checks for existing items to prevent overwrites.
  • Promote workflow readiness: items can be promoted to specs/ via the speckit.backlog.promote command for active development.

Quick Start

Provide the backlog item title (and optional description) to create a new entry in specs/backlog.

Frequently Asked Questions about speckit-backlog-add

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create structured backlog items in markdown for spec-driven projects?

You can create structured backlog items by generating a standardized markdown file at specs/backlog/{slug}.md containing Overview, Problem Statement, and Acceptance Criteria sections to ensure consistent organization.

What is the best way to automate slug generation and prevent file conflicts in a specs backlog?

Automating slug generation converts your backlog title into a safe filename and performs conflict checking against existing items in the specs/backlog directory to prevent accidental overwrites of active work.

How do I promote a backlog item to active development specs?

To promote a backlog item to active development, use the speckit.backlog.promote command which transitions the generated markdown entry from specs/backlog into the specs/ directory for implementation.

Does this backlog creation workflow require any external dependencies or components?

This backlog creation workflow requires no external dependencies or components to operate, allowing teams to capture and organize upcoming work immediately without installing additional packages.

What information do I need to provide to generate a new spec backlog entry?

To generate a new spec backlog entry, you need to provide the backlog item title and an optional description, which the system uses to generate the slug and populate the standardized markdown template.