work-item-impl

Generate implementation plans for CALLSHEET work items from WORK.md and spec sources.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Rwb3n/callsheet --skill work-item-impl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-item-impl
Source: https://github.com/Rwb3n/callsheet/tree/main/.claude/skills/work-item-impl
Command: npx skills add https://github.com/Rwb3n/callsheet --skill work-item-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initial planning ceremony for CALLSHEET work items, translating user intents like "implement 067" into a concrete implementation plan by pre-reading WORK.md, spec sources, and existing code patterns.

Core Features & Use Cases

  • Reads WORK.md to extract acceptance criteria, blockers, source files, and deliverables, establishing a baseline for planning.
  • Reads chapter metadata to understand dependency graphs and cross-cutting notes that influence implementation sequencing.
  • Pre-reads spec sources to map requirements to code patterns, types, events, and router signatures, enabling a complete plan before coding.
  • Generates a structured implementation plan saved to 4-work-management/work/CS-WORK-{NNN}/plans/impl-plan.md and presents it to the user for review.
  • Performs AC pre-satisfaction analysis to identify which criteria are already satisfied and which require new work.

Quick Start

Load the current work item and run the planning ceremony to generate an implementation plan.

Frequently Asked Questions about work-item-impl

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

FAQPage Schema
How do I automate work item planning and generate an implementation plan from scratch?

Automate work item planning by reading WORK.md, spec sources, and existing code patterns to generate a structured implementation plan. This process extracts deliverables, acceptance criteria, and dependencies to establish a complete baseline before coding begins.

What is AC pre-satisfaction analysis and how does it map requirements to code patterns?

AC pre-satisfaction analysis identifies which acceptance criteria are already satisfied and which require new work. It maps spec sources to existing code patterns, types, events, and router signatures to evaluate implementation readiness before generating the final plan.

How do I start a CALLSHEET work item using a normalized item ID?

Start a CALLSHEET work item by normalizing the item ID from commands like 'implement 067' or 'begin 068'. The system reads chapter metadata to understand dependency graphs and extracts deliverables, blockers, and cross-cutting notes to sequence the implementation.

Does the implementation plan generator handle dependency graphs and cross-cutting notes?

Yes, the implementation plan generator reads chapter metadata to understand dependency graphs and cross-cutting notes. This ensures proper implementation sequencing by mapping source files and dependencies before saving the structured plan to the designated work management directory.

What's the best way to translate user intents like 'implement 067' into a concrete implementation plan?

Translate intents like 'implement 067' into concrete plans by normalizing item IDs, reading WORK.md for acceptance criteria and blockers, and pre-reading spec sources. The generated plan satisfies frontmatter metadata and is saved as a structured markdown file for review.

Can I pre-read spec sources to map requirements to code patterns before coding begins?

Yes, you can pre-read spec sources to map requirements to code patterns, types, events, and router signatures. This enables a complete implementation plan generation by identifying which acceptance criteria need new work and establishing a solid baseline before development starts.