checklist-driven-development

Execute the next bounded checklist session and write a state handoff.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Berkay2002/skills --skill checklist-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checklist-driven-development
Source: https://github.com/Berkay2002/skills/tree/main/skills/checklist-driven-development
Command: npx skills add https://github.com/Berkay2002/skills --skill checklist-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a disciplined, one-session-at-a-time execution model for implementing approved plans stored in a repository workflow bundle, avoiding scope creep and ensuring continuity across separate agent runs.

Core Features & Use Cases

  • Enforces a strict session boundary: resolve workflow, lock scope, execute only the selected checklist item, verify, and hand off state.
  • Maintains append-only state and produces a self-contained next-agent prompt to preserve continuity across runs.
  • Use cases: sequential feature implementation from an implementation plan, tightly coupled refactors requiring stepwise verification, and controlled handoffs between agents or sessions.

Quick Start

Using checklist-driven-development, resolve the active docs/workflows bundle, read context.md and checklist.md, perform only the next unchecked session's scope, run required verification, append the outcome to state.md, and write the ready-to-paste next prompt to prompts/next.md.

Frequently Asked Questions about checklist-driven-development

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

FAQPage Schema
How do I maintain state and continuity when executing a multi-session implementation plan across separate agent runs?▼

Checklist-driven development maintains continuity across separate agent runs by resolving an active workflow bundle, executing one bounded checklist session, appending outcomes to an append-only state.md, and writing a self-contained next.md handoff prompt for the subsequent session.

What is the best way to prevent scope creep when sequentially implementing features from an approved plan?▼

Preventing scope creep during sequential feature implementation requires enforcing a strict session boundary that locks execution scope to only the next unchecked checklist item, followed by targeted verification and state handoff before any subsequent work begins.

How do I set up a repository workflow bundle for stateful agent handoffs?▼

Setting up stateful agent handoffs requires creating a docs/workflows bundle containing ACTIVE.md, a date-prefixed folder with context.md, checklist.md, state.md, and a prompts directory to resolve active workflow sessions and store sequential continuity data.

Does checklist-driven development work with test-driven development workflows requiring stepwise verification?▼

Checklist-driven development supports test-driven development workflows by running targeted verification commands after executing each bounded checklist session, ensuring tightly coupled refactors meet stepwise verification requirements before appending results to state.md.