closer

Move a completed backlog feature folder to the completed directory and update references.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ianphil/prism --skill closer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: closer
Source: https://github.com/ianphil/prism/tree/main/.claude/skills/closer
Command: npx skills add https://github.com/ianphil/prism --skill closer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the routine and error-prone process of closing a completed feature and moving its folder from backlog/plans to backlog/plans/_completed, ensuring documentation and references stay consistent.

Core Features & Use Cases

  • Validation & Safety: checks backlog/plans/{NNN}-{slug}/tasks.md for incomplete tasks and prevents closures until resolved or confirms user intent to close anyway.
  • Folder Reorganization: moves the feature folder to backlog/plans/_completed/{NNN}-{slug} and ensures the completed state is preserved.
  • Documentation Hygiene: scans and updates references to the old path in relevant docs.
  • Audit Trail: commits changes with a descriptive message for traceability.

Quick Start

Close a feature by providing its identifier (e.g., 003 or 003-my-feature). The skill will locate the feature, verify completion, move it to the completed directory, and update references automatically.

Frequently Asked Questions about closer

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

FAQPage Schema
How do I archive a completed feature folder and update documentation references automatically?

The skill validates completion by checking tasks.md in the feature folder for incomplete tasks. It prevents closures until tasks are resolved, or prompts to confirm intent to close the feature with incomplete items anyway.

Can I close a feature by inferring its ID from the current Git branch?

Yes, you can close a feature by inferring its ID from the current Git branch. When no identifier is supplied, the skill automatically detects the target feature from the branch name.

What is the best way to move a backlog feature to a completed directory while keeping an audit trail?

The best way to move a backlog feature is using a single command that relocates the folder, ensures completion validation, updates references, and creates a Git commit log for a reliable audit trail.

Does the feature closure process work with standard Git commit logs?

Yes, the feature closure process works with Git by committing changes with a descriptive message. This ensures the folder reorganization and reference updates are tracked in the standard commit log.

Why does the feature archive process check tasks.md before moving the folder?

The feature archive process checks tasks.md to validate completion and prevent premature closures. It ensures no incomplete tasks remain before moving the folder to the completed directory.

Do I need to provide a feature identifier like NNN-slug to close a backlog item?

You do not need to provide a feature identifier like NNN-slug if you are on the corresponding Git branch. The skill can infer the target feature automatically, though supplying the ID ensures exact matching.