work-item-done

Update a CALLSHEET work item's status across WORK.md, trackers, and completion log.

Updated Feb 13, 2026

Search Tags:#work-item #status-update #artifact-verification #tracker #WORK.md #completion-log

Ready to run

npx skills add https://github.com/Rwb3n/callsheet --skill work-item-done

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-item-done
Source: https://github.com/Rwb3n/callsheet/tree/main/.claude/skills/work-item-done
Command: npx skills add https://github.com/Rwb3n/callsheet --skill work-item-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close out a single CALLSHEET work item. This skill updates the work item's status in WORK.md, refreshes all relevant tracker locations, and records a completion log entry. It is a lighter, per-item close-out designed to be used after implementing and validating a single item, without touching session-wide closures.

Core Features & Use Cases

Update the WORK.md status for the specified work item (for example CS-WORK-069) to done with a closed timestamp.
Update all tracker locations (slice progress, AC verification, and blocked/enables relationships) for the single item.
Verify artifacts and append a concise completion log entry documenting key outputs and test status for the item.

Quick Start

Provide the work item ID (for example CS-WORK-069) to close and confirm the item is implemented and ready for verification.

Frequently Asked Questions about work-item-done

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

FAQPage Schema

How do I update a CALLSHEET work item status to done in WORK.md?▼

To update a CALLSHEET work item status, provide the work item ID such as CS-WORK-069 and the skill sets its WORK.md status to done with a closed timestamp, refreshing all tracker locations and appending a completion log entry.

What's the best way to close out a single work item without affecting the whole session?▼

Closing a single work item is best handled per-item by normalizing the ID like CS-WORK-069, then propagating status updates across WORK.md, tracker locations, and the completion log without touching session-wide closures.

How does artifact verification work when completing a work item?▼

Artifact verification during work item completion guides you through checking key outputs and test status, then appends a concise completion log entry documenting those artifacts for the individual item being closed.

Do I need to run tests before closing a work item in the tracker?▼

Yes, tests must pass before closing a work item. The skill assumes validation is complete and focuses solely on status propagation, artifact tracking, and completion logging without executing tests itself.

Can I close multiple CALLSHEET work items at the same time?▼

No, this skill operates on one item at a time. It is a lighter, per-item close-out designed to be used after implementing and validating a single work item rather than batch processing.