[BUG] Claude Code loses multi-phase project context and prematurely declares work complete

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

## Description
When working on a multi-phase project, Claude Code completed one feature
(Daily/Weekly task categories) and then declared the project was done,
asking "which would you like to do?" about committing — completely forgetting
the 5-phase project roadmap established in earlier sessions.

## Actual Behavior

• Claude said "The feature is done — nothing else needed"
• Required 3 rounds of user correction before Claude finally read the

earlier session transcript and found the full 5-phase roadmap

• Claude had no awareness of the broader project scope

What Should Happen?

## Expected Behavior

• Claude should check prior session transcripts / project context before

declaring work complete

• On a multi-phase project, Claude should know what phase comes next
• The plan transcript path was literally in the prompt but Claude never read it

until the user pushed back multiple times

Error Messages/Logs

Steps to Reproduce

## Steps to Reproduce

1. Establish a multi-phase project plan in Session 1 (brainstorm → full roadmap)
2. Build Phase 1 core shell across Sessions 1-2
3. In a new session, give Claude a specific feature plan to implement
4. After completing the feature, Claude assumes the entire project is finished
5. When asked "what's next?", Claude suggests committing and says nothing else is needed

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.49 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_