workflow-checklist

Run a 4-phase development workflow checklist for pre-work, during-work, post-work, and session health.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill workflow-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-checklist
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/workflow-checklist
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill workflow-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common problem of inconsistent development workflow practices, missed pre-work validation, incomplete post-work verification, and poor session hygiene that lead to defective code, duplicate work, missed quality gates, and wasted engineering time across development sessions.

Core Features & Use Cases

  • 4-Phase Interactive Checklist: Covers pre-work validation (active work item check, correct git branch, existing spec/plan, duplicate work check), during-work reminders (agent delegation guidance, real-time plan updates, gate verification, context usage monitoring), post-work verification (build/test/lint gate checks, completed plan checkboxes, updated CHANGELOG, cleared active work pointer), and session health checks (context usage reporting, MCP status review, next step recommendations).
  • Workflow Integration: Natively integrates with other MAD Council Claw skills like /mad-spec, /mad-implement, and /mad-validate to align with existing project workflows and work item tracking systems.
  • Use Case: A developer starting a new feature implementation can run the pre-work phase to confirm they are on the correct feature branch and have an existing spec, run during-work reminders every 30 minutes to update their plan and verify agent outputs, and run post-work checks before closing to ensure all quality gates pass and documentation is fully updated.

Quick Start

Invoke the workflow-checklist skill at the start of your development session to run the full interactive 4-phase hygiene check, or specify a phase argument like pre, during, post, or health to run only the relevant section for your current needs.

Frequently Asked Questions about workflow-checklist

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

FAQPage Schema
How do I enforce consistent development workflow practices across my git sessions?

You can enforce consistent development workflow practices by running an interactive 4-phase checklist covering pre-work validation, active work reminders, post-work verification, and session health checks to prevent defective code and missed quality gates.

What is a pre-work checklist for software development and when do I need it?

A pre-work checklist validates that you have an active work item, are on the correct git branch, have an existing spec or plan, and have checked for duplicate work before starting a feature implementation to eliminate wasted engineering time.

How do I verify quality gates and update documentation before closing a development session?

Run a post-work verification checklist to confirm build, test, and lint gate checks pass, completed plan checkboxes are updated, the CHANGELOG is modified, and the active work pointer is cleared before ending your development session.

Can I run individual workflow hygiene checks instead of the full development session checklist?

Yes, you can specify a phase argument such as pre, during, post, or health to run only the relevant workflow hygiene section for your current needs instead of executing the full interactive checklist.

Does the workflow checklist integrate with existing spec and implementation tools?

The checklist natively integrates with other MAD Council Claw workflow kit skills including spec, implement, and validate commands to align with existing project workflows and work item tracking systems.

Why does my development workflow suffer from poor session hygiene and missed pre-work validation?

Poor session hygiene and missed pre-work validation occur when there is no standardized workflow discipline, leading to inconsistent practices, duplicate work, defective code, and missed quality gates across development sessions.