speckit-backlog-reject

To archive backlog items, this skill moves the item to specs/backlog/rejected, updates its status to Rejected with a date, and logs the dismissal reason you provide. It validates the slug and preserves the context for future reference.

The best way to keep an audit trail is to formally reject items by moving them to specs/backlog/rejected with a timestamp and reason. This maintains an auditable record of rejections to inform future prioritization or rework decisions.

You should reject and archive backlog items instead of deleting them to preserve context and maintain an auditable trail. This formal process logs the dismissal reason, which can inform future prioritization or rework decisions without cluttering the active backlog.

Yes, you need access to the specs/backlog directory. The skill locates backlog items under this path, validates the slug you provide, and moves the file to specs/backlog/rejected to complete the archival process.

Yes, you can revisit a backlog item after moving it to the rejected archive. The item is moved with its original context and a logged rationale, specifically preserving the dismissal reason for potential future revisit or rework.