speckit-backlog-graduate

Promote backlog items into active specs using speckit.specify.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

backlog items languish in specs/backlog; this skill automates promoting a backlog item to an active spec by converting its content into the full spec workflow via speckit.specify.

Core Features & Use Cases

  • Backlog-to-spec promotion: converts a backlog markdown into a production-ready spec via speckit.specify.
  • End-to-end workflow integration: validates backlog presence, reads the backlog content, runs inline speckit-specify instructions, and promotes to active specs.
  • Safe cleanup: removes the backlog item after successful promotion and optionally prompts when backlog is empty.

Quick Start

Promote a backlog item to an active spec by providing its slug with /speckit.backlog.promote.

Frequently Asked Questions about speckit-backlog-graduate

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

FAQPage Schema
How do I convert a backlog item into an active spec?

To convert a backlog item into an active spec, the skill reads your backlog markdown content and runs inline speckit-specify instructions to generate a fully documented, production-ready specification.

How does automated backlog promotion maintain a clean specs directory?

Automated backlog promotion maintains a clean directory by reading the target item, converting it to an active spec via speckit.specify, and then safely removing the original backlog file after a successful promotion.

Do I need an existing backlog file to generate a feature specification?

Yes, you need an existing backlog markdown file under the specs/backlog directory to serve as the feature description input for generating a fully documented specification.

What happens to my backlog directory when all items are promoted to active specs?

When all items are promoted to active specs, the backlog directory reaches a clean empty state, and the skill can optionally prompt you to indicate that no remaining backlog items exist.

What is the best way to manage feature generation from a markdown backlog?

The best way to manage feature generation from a markdown backlog is using an end-to-end workflow that validates the item's presence, converts the content into a spec, and cleans up the source file automatically.