speckit-backlog-dismiss

Reject backlog items and archive them with a recorded reason.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reject backlog items promptly and archive them with a clear reason to preserve history.

Core Features & Use Cases

  • Move a backlog item from specs/backlog to specs/backlog/rejected with status updated to Rejected.
  • Record the rejection date and reason for future reference and auditing.
  • Keep rejected items accessible for reference but excluded from the active backlog listing.

Quick Start

Provide the backlog slug and a reason to reject, and invoke the reject command.

Frequently Asked Questions about speckit-backlog-dismiss

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

FAQPage Schema
How do I reject a backlog item and archive it with a reason?

To reject a backlog item, provide its slug and a reason. The workflow updates the status to Rejected, records the date and reason, and moves the file from specs/backlog to the specs/backlog/rejected folder.

What happens if I try to reject a backlog item without providing a reason?

If you reject a backlog item without a reason, the workflow validates the slug and prompts you to enter a reason before updating the status and moving the file to the rejected folder.

Does rejecting a spec-kit backlog item delete the file?

Rejecting a spec-kit backlog item does not delete the file. It moves the item to specs/backlog/rejected, keeping it accessible for reference and auditing while excluding it from the active backlog.

Why should I archive rejected backlog items instead of deleting them?

Archiving rejected backlog items preserves history by recording the rejection date and reason. This creates an audit trail for future reference and keeps rejected items accessible without cluttering the active backlog listing.

Can I use this workflow to reject multiple backlog items at once?

The workflow operates on individual backlog items by validating a single slug, recording the rejection reason, and moving that specific file to the rejected folder. There is no indication of bulk rejection support.