OpenSpec with Claude Hooks

[PwrBank]

Hey there @TabishB

I'm working on a proposal to add features from CC-Sessions into OpenSpec.

Here is the current plan:
https://github.com/PwrBank/OpenSpec/blob/add-claude-hooks/openspec-claude-hooks-plan.md

The idea is pull the features in from CC-Sessions that help keep a project going but still retaining the structure of OpenSpec, which I prefer in my workflow.

This would all be optional, the idea is when you run openspec init and choose the Claude Code CLI option, it will ask if you would like to inject the hooks workflow and/or the statusline. This should keep this change agnostic to other coding agents.

Changes

What I'm wanting to add to OpenSpec based on the plan:

Hooks

When using Claude Code, hooks are called on user input. Hooks prevent Claude from making changes to the current plan without approval, keeping Claude from doing whatever it thinks is correct instead of what you agreed for it to do.

Git branches

When starting the implementation of a proposal plan a Git branch will be created to help track changes and make it easier to revert

Worklogging and session resume

Either by using a keyword or a slash command, run a sub-agent that will document the current session with worklogs on what was changed and what needs done, append it to a worklog document within the change folder. A similar command can be ran to resume where you left off. This prevent Claude from losing context and helps users remember where they left off. This should also help with context exhaustion, ideally running this command before you run out of current context will prevent loss in productivity.

Pre-Archive post Implementation workflow

Two agents should be activated (or they can be skipped) after the implementation has been completed but prior to archiving the change. One agent will do a comprehensive code review and the other will verify documentation, worklogs, and changes have been updates accurately. It then prompts the user with the findings from both agents giving the option to skip, make the changes, or create a separate change with the updates needed and then archives the current one. Actions will be documented regardless of choice in the worklog/task - So no information is lost.

Statusline

This will also be an optional configuration during the init process. I liked the amount of information CC-Sessions displays with their statusline, it helps give you an idea of where you currently are in a process.

📝 add-api-versioning | 󱃖 █████████░ 92.5% (148k/160k)
󰷫  Implementation (4/7) | ✎ 12 | 📋 5 open | 󰘬 feature/add-api-versioning (↑5 ↓2)

This displays the current task being worked on, the context left in the session
What phase of the plan you are in, the amount of todos Claude has in it's TodoList, how many open changes are in OpenSpec currently, and the current active git branch with the amount of ahead and behind changes.

Current issues this might solve?

Obviously only if they are using Claude Code... But still.

This should hopefully help with problems like:
#286
#254
#246

Ideas / Feedback

Would this change be appropriate for the OpenSpec project? Or what would need modified to be more inline with the current OpenSpec... Spec?

[sfearl1]

+1 for adding an optional statusline to openspec. And I think adding a "next action" would be useful so you could quickly glance and know what to run at any point in a session... "next action: /openspec:apply some-spec-2"