slice-pre-draft-checklist

Generate pre-draft checklists for CALLSHEET requirements slices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates a ready-to-run pre-draft checklist for CALLSHEET slice planning, reducing repetitive configuration errors before drafting.

Core Features & Use Cases

  • Reads upstream requirements and interface specs to surface all required registry entries and schema changes.
  • Validates template coverage and detects potential overlaps with prior slices, ensuring consistency across SI/PP references.
  • Provides a structured output ready for drafting, including exact Deferred Actions, Email Templates, Event Emissions, Event Consumers, and Schema Amendments.

Quick Start

Provide a pre-draft checklist for a new CALLSHEET slice by inspecting upstream requirements and interface specs, then assemble registry entries and schema changes ready for drafting.

Frequently Asked Questions about slice-pre-draft-checklist

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

FAQPage Schema
How do I automate a pre-draft checklist for CALLSHEET slice requirements?

Automate a pre-draft checklist for CALLSHEET slice requirements by reading upstream interface specs to surface registry entries and schema changes, ensuring configuration consistency before drafting.

What is a slice readiness checklist and when do I need it for schema amendments?

A slice readiness checklist validates template coverage and tracks schema amendments from prior slices. You need it during slice planning from S0 onward to prevent overlapping registry entries and configuration errors.

How do I generate registry entries for Deferred Actions and Event Emissions before drafting?

Generate registry entries for Deferred Actions and Event Emissions by inspecting upstream requirements, then assembling exact structured outputs ready for drafting alongside Email Templates and Event Consumers.

Can I validate template coverage and detect overlaps with prior slices automatically?

Yes, you can validate template coverage and detect overlaps with prior slices by referencing cumulative schema state, ensuring consistency across SI/PP references before starting the drafting workflow.

What's the best way to track cumulative schema state across new slices from S0?

Track cumulative schema state across new slices by referencing prior slice schema amendments in a pre-draft checklist, capturing exact Event Consumers and Deferred Actions to maintain interface consistency.

Why do requirements slices need explicit entries for Event Consumers and Schema Amendments?

Requirements slices need explicit entries for Event Consumers and Schema Amendments to ensure all registry dependencies are surfaced and validated against upstream interface specs before drafting begins.