Maintain spec integrity in subsequent changes

[lqchinh88]

How do we keep the specs updated / versioning the specs in subsequent changes of the features, or if other features requires modification of existing features ?

[notdp]

First, I always believe that code is the most precise context, as it can accurately describe implementation details.

Second, since the current model's context is limited, I feel that spec documents do not have the archival significance of PRD documents. Their primary role is to guide the model in developing a specific function and can be discarded after use. Of course, when you need to change this function, you can refer CC to these spec documents for modifications for better results. You can also ensure that the spec document is updated when changes are made by the model. However, in my view, it's challenging for CC to proactively refer to spec documents when you're asking them to make certain implicit changes.

When replying to you, I thought of something: perhaps I could have CC actively maintain the relationship between spec documents and specific functions in CLAUDE.md. This way, when you make modifications, both the spec document and past designs will be well-updated and understood by CC.

What do you think of this idea? I can implement it quickly, similar to the already implemented steering function.

[lqchinh88]

Thanks for the reply.

First, discarding the specs after use is a big waste. I'm in favor of spec-first development and your extension is doing a good job in coming up with the specs. Moreover, we spend lots of time reading, adjusting the specs before pushing to development too, so I dont think discarding it after is wise.

However, as agreed with you, the model context might pose technical challenges to consolidate the specs. Let's say we start with what you propose : try to maintain the specs relationship somewhere ( I dont think CLAUDE.md, lets leave it for steering claude purpose, how about a separate doc just for spec maintainance ). Maybe you can create an agent specifically for consolidating specs, and have it do its job after a new feature is done, then you can improve this agent over time.

In an ideal world, I imagine anytime I add a feature, or modify an existing feature, the specs I have always reflect the whole system to the minute detail. For now, a step in this direction is enough. I believe with the right model development, and with further enhance in this agent flow, we could achieve something similar.

Your thoughts ?

[notdp]

I will try to create a CLAUDE.md under the .claude/specs directory specifically to maintain the mapping between spec documents and feature points, to see if it will be included in the context.

[seanGSISG]

any update on this or how to implement?

[notdp]

any update on this or how to implement?

I've been working a lot with the iTerm2 terminal recently, mainly exploring parallel work.

The next step for the plugin is Codex integration and worktree management.