Constitution not being honored during development workflow

[hpinsley]

I started on a project a few days ago and have been implementing tasks either one by one, or allowing Claude to do small ranges with prompts such as this:

/speckit.implement Implement the tasks in section Mobile Implementation for User Story 2 and then stop.

I had noticed that when I asked Claude to do the implementation, that it would commit only at the very end. I decided to amend the constitution to instruct Claude to commit the changes for each task as they were completed. Since this was an amendment to the constitution, I updated it with the prompt:

/speckit.constitution Update the constitution to indicate that when you implement multiple tasks, that you commit your
work for each task independently. Include, in the commit, an update to tasks.md to indicate that the task is
complete.

This is what it added:

Task-Based Commit Discipline

When implementing multiple tasks from tasks.md, MUST follow atomic commit practices:

• One Commit Per Task: Each completed task MUST result in exactly one commit
  • Do NOT batch multiple tasks into a single commit
  • Do NOT split a single task across multiple commits (unless task is legitimately large and justifies subdivision)
• tasks.md Update Required: Every task commit MUST include an update to the relevant tasks.md file
  • Mark the task as complete using the checkbox syntax: - [x] T### [Tags] Description
  • Include this tasks.md change in the same commit as the task implementation
  • Task ID (T###) must be referenced in the commit message

Why then when I logged out of Claude (process stopped), authenticated again, would Claude, after implementing the tasks in response to this prompt:

/speckit.implement Implement the tasks in section Mobile Implementation for User Story 2 and then stop

fail to commit anything? The changes for all the tasks were made to the files but no commit.

[hpinsley]

Well I was wrong. I returned to the project after posting this and told Claude to commit. It REREAD the constitution and is indeed committing one-by-one as instructed. :-) See below...

commit your work 
  ⎿  ⧉ Selected 11 lines from ../.specify/memory/constitution.md in Visual Studio Code

● I need to commit my work following the task-based commit discipline. Let me check the current git status and create separate commits for each task:
...

Commits Created (6 total)

[hpinsley]

I'm still a bit confused. It does seem to sometimes ignore_ the commit workflow specified in constitution.md. The last set of tasks completed and nothing was committed.