A structured task-planning guide for breaking work into small, verifiable tasks with dependencies and verification criteria, intended for implementing features, refactoring, or any multi-step work.
Tasks
Break down a feature addition into 5-10 specific, one-line tasks, each with a 'Verify: [How to check]' criterion
Create a plan file named from the task slug (e.g., 'add auth' becomes auth-feature.md) saved in the project root
Write a plan for a complex bug fix identifying root cause, file/line to change, and how to test the fix
Inputs
A description of the work to be done (new project, feature addition, bug fix, or refactoring)
Knowledge of the project type (frontend, backend/API, mobile, database, or full-stack) so relevant verification scripts can be chosen
Outputs
A markdown plan file ({task-slug}.md) in the project root containing a Goal, a task checklist with verification criteria per task, a Done When section, and optional Notes
Limitations and checks
Provides a planning framework only; it does not execute tasks or run scripts itself
Allowed tools are limited to Read, Glob, and Grep
The verification scripts named in the guide (e.g., ux_audit.py, api_validator.py) are project-specific examples and must not be copy-pasted into every plan
Confirm every task line follows the pattern 'Task N: [Specific action] → Verify: [How to check]'
Confirm the plan file is named from the task slug and located in the project root, not in .claude/, docs/, or a temp folder
Confirm the plan has 10 or fewer tasks and fits within about one page
Confirm verification is the final phase and each Done When criterion is concrete (e.g., 'curl localhost:3000/api/users returns 200') rather than generic
Search
Find projects, verify facts, compare options, and filter by your requirements
Try a searchA click only fills the search box; you stay in control