lightweight-task-workflow

Manage multi-session tasks with three state files in .claude.

334|43|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/NTCoding/claude-skillz --skill lightweight-task-workflow-ntcoding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lightweight-task-workflow
Source: https://github.com/NTCoding/claude-skillz/tree/main/lightweight-task-workflow
Command: npx skills add https://github.com/NTCoding/claude-skillz --skill lightweight-task-workflow-ntcoding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to manage multi-session tasks with a persistent, three-file state machine, ensuring tasks are paused between sessions until user permission.

Core Features & Use Cases

  • Stateful task tracking across sessions using .claude/tasks.md, .claude/requirements.md, .claude/session.md
  • NO auto-advancement or automatic commits; user controls pacing
  • Supports continuity across sessions and recovery after interruptions

Quick Start

Describe your tasks, outline requirements, and I will initialize .claude/tasks.md, .claude/requirements.md, and .claude/session.md in your project root. Then say "continue" to resume and the system will read .claude/session.md and route based on Status.

Frequently Asked Questions about lightweight-task-workflow

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

FAQPage Schema
How do I maintain task management state across multiple Claude sessions?

Multi-session task management requires a persistent state machine using files like .claude/tasks.md, .claude/requirements.md, and .claude/session.md to save checklists, specs, and routing data for recovery.

How do I set up persistent checklists for project workflow in Claude?

To set up persistent checklists, describe your tasks and outline requirements to initialize .claude/tasks.md and .claude/requirements.md in your project root, then use a session file to track execution status.

Can I pause task execution between sessions and resume later?

Yes, session persistence pauses task execution between sessions without auto-advancement, requiring explicit user permission to advance so you maintain full control over the project workflow pacing.

What is the best way to recover an interrupted multi-session project workflow?

Recovering an interrupted project workflow involves reading the .claude/session.md file to route the state machine back to the correct phase, ensuring task continuity after unexpected interruptions.

Does this task management state machine automatically commit my progress?

No, the task management workflow enforces strict rules with no auto-advancement and no automatic commits, ensuring tasks are paused between sessions until explicit user permission is granted.

When should I not use a state-driven multi-session task workflow?

A state-driven task workflow is unnecessary for single-session tasks or simple projects that do not require strict execution verification, session recovery, or persistent requirement tracking across interruptions.