/openspec-apply is not loading project.md

[alexandrereyes]

I tried in Cursor and in OpenCode. When the /openspec-apply command is triggered, the project.md file doesn’t load. That’s a problem because all the project conventions are described there.

[stephenstubbs]

I have the same issue. I have added that file to the apply slash command which works but this or another fix should be done by default.

[jax-max]

Threre is a talk about apply without reading project.md , pls take a look #306 @stephenstubbs @alexandrereyes

[jax-max]

really need scaffold :) @TabishB

[stephenstubbs]

Hi @jax-max, This still seems to be an issue. I am not entirely sure what #306 resolves in relation to this.

[stephenstubbs]

Is there anything I can help with to get this resolved if not already @TabishB?

[TabishB]

@stephenstubbs I've had this discussed before but the general idea is project.md is read when the plan is created and thus the plan follows any conventions of the project.

If the plan itself is right the application of that plan should techincally be correct as well.

Unless there's a need to read the conventions twice <- Which I can't see as great practice but I'm open to a conversation here.

Have I missed something, is there a case where reading it twice is helpful?

[stephenstubbs]

Hi @TabishB, I understand. Where would be the best place for me to define where it should use context7 and latest version of dependancies as an example? Currently I have that added to the apply slash command but I am not sure if there is a better place to add this into the openspec workflow.

[stephenstubbs]

Hi @TabishB, Just to follow up on this I have noticed other conventions also not being followed in the planning stage. If I alter the slash commands I can include them but it doesn't seem to work out the box for me.

[TabishB]

@stephenstubbs what alteration to the slash command seems to make them work better?

[stephenstubbs]

Hi @TabishB, after more testing it seems there is always a chance of some missed if only included in the planning stage. I have now just included reading the project.md in stage 2:

### Stage 2: Implementing Changes
Track these steps as TODOs and complete them one by one.
1. **Read project.md** - Review project conventions (coding style, module structure, testing requirements)
2. **Read proposal.md** - Understand what's being built
3. **Read design.md** (if exists) - Review technical decisions
4. **Read tasks.md** - Get implementation checklist
5. **Implement tasks sequentially** - Complete in order, following project.md conventions
6. **Confirm completion** - Ensure every item in `tasks.md` is finished before updating statuses
7. **Update checklist** - After all work is done, set every task to `- [x]` so the list reflects reality
8. **Approval gate** - Do not start implementation until the proposal is reviewed and approved

[TabishB]

@stephenstubbs Thanks this is useful context and data points. FWIW we're reworking a lot of the internals to make the instructions a lot more modular as well as extendible which should help us test these things as well as allow users to control/customize these things more granularly.

(Check out the discord for more info)

If I could ask for some more data points:

1. What model are you using?
2. What agent harness are you using (e.g Claude Code, Cursor)

[stephenstubbs]

Hi @TabishB,

Thank you that is great news. I genuinely think openspec is the perfect approach to this and have loved using it. More granularity will be appreciated when needed but out the box things have been really smooth for the most part.

1. Claude Opus 4.5
2. opencode

[TabishB]

@stephenstubbs No problem! Would love for you to try out the new experimental version that will be released soon under a feature flag.

It might be a little shaky/rough at the start but it lets us iterate much much faster towards something more reliable. (Alongside eventually letting us set up a proper evaluation system).

If you're keen to try let me know. Not sure if you're in the discord so providing some screenshots:

[stephenstubbs]

Hi @TabishB, Wow that looks awesome. I am happy to test and will join the discord.