Please make Claude Code follow and mark off tasks on task lists step by step, one by one.

Resolved 💬 11 comments Opened Apr 17, 2025 by swombat Closed May 8, 2025

As per this Discord comment:

My most desired feature by far that would solve all the other issues is if there was a way that Claude Code could ensure it actually goes through the task list task by task, one by one, without grouping/skipping tasks.

Cause that's where it always ends up going wonky, And almost ALL the other problems with Claude Code would be fixed if it just did the tasks one by one, because then I can just make sure that every other task is clobbering it over the head with claude.md so the instructions there are always fresh in its mind.

But since it frequently (50+% of the time) fails to follow the clear and repeated instructions to do tasks one by one and mark them as complete one by one... it also quite frequently goes off the rails.

So PLEASE find a way to tweak Claude Code's thinking so it actually goes through the (editable) task list, one task at a time!...

I believe this would be a "50% reliable to 95% reliable" jump in value if it can just do that one thing... of doing one thing at a time and following the task list.

As it is, even when I give it task lists like this:

## Test Plan Tasks

- [x] **1. Create the basic test file structure**

Complete tasks step by step, marking them as done one by one.

   - [x] 1.0. Re-read CLAUDE.md to ensure compliance with project requirements
   - [x] 1.1. Create `/test/integration/loa_aml_identity_integration_test.rb`
   - [x] 1.2. Set up the test class with proper inheritance from ActionDispatch::IntegrationTest
   - [x] 1.3. Create setup method to log in as an admin and prepare test data
   - [x] 1.4. Re-read CLAUDE.md and verify the instructions have been applied correctly

- [x] **2. Test initialization and document creation**

Complete tasks step by step, marking them as done one by one.

   - [x] 2.0. Re-read CLAUDE.md to ensure compliance with project requirements
   - [x] 2.1. Create test for navigating to a client/claim page
   - [x] 2.2. Create test for filling out and submitting the LOA/AML form with recipient details
   - [x] 2.3. Re-read CLAUDE.md to ensure compliance with project requirements
   - [x] 2.4. Verify the DocuSeal API is called to create a document template
   - [x] 2.5. Verify a DocusealDoc record is created with the correct status
   - [x] 2.6. Verify a WorkflowEvent is created for the document creation
   - [x] 2.7. Run the test with `rails test /path/to/test.rb:123` to verify it passes
   - [x] 2.8. Re-read CLAUDE.md and verify the instructions have been applied correctly

- [x] **3. Test email submission and workflow state update**

Complete tasks step by step, marking them as done one by one.

   - [x] 3.0. Re-read CLAUDE.md to ensure compliance with project requirements
   - [x] 3.1. Create test for submitting the document to DocuSeal for email delivery
   - [x] 3.2. Re-read CLAUDE.md to ensure compliance with project requirements
   - [x] 3.3. Verify the DocusealDoc record is updated with submission information
   - [x] 3.4. Verify a WorkflowEvent is created for the document submission
   - [x] 3.5. Verify the UI displays the correct status for the document (sent)
   - [x] 3.6. Run the test with `rails test /path/to/test.rb:123` to verify it passes
   - [x] 3.7. Re-read CLAUDE.md and verify the instructions have been applied correctly

- [x] **4. Test webhook handling for document viewing**

Complete tasks step by step, marking them as done one by one.

   - [x] 4.0. Re-read CLAUDE.md to ensure compliance with project requirements
   - [x] 4.1. Create test that simulates the DocuSeal webhook callback for document viewing
   - [x] 4.2. Re-read CLAUDE.md to ensure compliance with project requirements
   - [x] 4.3. Verify the DocusealDoc record is updated with the viewed status
   - [x] 4.4. Verify a WorkflowEvent is created for the document viewing
   - [x] 4.5. Verify the UI displays the correct status for the document (viewed)
   - [x] 4.6. Run the test with `rails test /path/to/test.rb:123` to verify it passes
   - [x] 4.7. Re-read CLAUDE.md and verify the instructions have been applied correctly

It still often fails to go through the steps one by one. And as soon as it starts marking tasks as done in groups, the risk of it going off the rails gets a lot higher, very quickly.

PLEASE: help Claude with his ADHD 😅 Teach him to follow a task list.

View original on GitHub ↗

This issue has 11 comments on GitHub. Read the full discussion on GitHub ↗