Where are the task files stored?

The files (.claude/tasks.md, .claude/requirements.md, and .claude/session.md) are stored in your project's root directory, not in the skill's installation directory, making them part of your project's context.

How does the 'continue' command work in this skill?

When you say 'continue', Claude triggers a state machine that checks your current working directory, reads your session.md file, and automatically routes itself to the correct state (Working, Verify, or Awaiting Commit).

Why does this skill discourage using Claude's built-in TodoWrite?

Built-in todos are often stored in internal state that can be lost or become inconsistent during long sessions. This skill uses local Markdown files to ensure the plan is always visible, editable, and persistent across context resets.

Can this skill automatically commit my code changes?

No. To maintain developer control and safety, the skill is explicitly programmed to never auto-advance tasks or create git commits without your direct permission.

Lightweight Task Workflow

Name: Lightweight Task Workflow
Author: NTCoding

byNTCoding

•

생산성 및 워크플로

Enforces a strict, state-driven workflow for managing complex programming tasks using persistent local Markdown files.

소개

The Lightweight Task Workflow skill transforms Claude Code into a structured project manager by implementing a rigorous state machine. It moves task tracking out of volatile chat history and into persistent files (.claude/tasks.md, requirements.md, and session.md), ensuring that complex, multi-step coding projects remain organized across sessions. By requiring explicit state announcements and verification phases, it prevents Claude from skipping steps, losing context, or auto-advancing without meeting your specific 'Definition of Done' criteria.

주요 기능

94 GitHub stars
Strict state machine enforcement with mandatory status announcements for every message
Prevention of workflow drift by replacing internal Todo tools with a file-based source of truth
Persistent task tracking via local Markdown files for seamless session recovery
Dedicated verification phase to ensure all requirements and tests pass before completion
Automatic routing based on session status when using the 'continue' command

사용 사례

Providing a clear, human-readable audit trail of project progress within the repository
Managing long-running refactoring projects that span multiple terminal sessions
Enforcing strict testing and linting standards before any task is marked as complete

소개

주요 기능

94 GitHub stars
Strict state machine enforcement with mandatory status announcements for every message
Prevention of workflow drift by replacing internal Todo tools with a file-based source of truth
Persistent task tracking via local Markdown files for seamless session recovery
Dedicated verification phase to ensure all requirements and tests pass before completion
Automatic routing based on session status when using the 'continue' command

사용 사례

Providing a clear, human-readable audit trail of project progress within the repository
Managing long-running refactoring projects that span multiple terminal sessions
Enforcing strict testing and linting standards before any task is marked as complete