Skip to content

Conversation

@christso
Copy link
Collaborator

@christso christso commented Jan 21, 2026

The idea is that we can evaluate whether any changes requiring a new openspec proposal should be done in a new feat branch. Never on main branch. Also when creating an eval it should include the relevant input files.

The process is :

  1. create new feat branch
  2. create proposal
  3. apply
  4. review
  5. archive openspec.

At each stage it should prompt the user for the next step rather than user having to remember.

- Add Branching Strategy section: never work on main
- Update TL;DR checklist: create feature branch first, open PR
- Update Stage 1: create branch, open draft PR for review
- Update Stage 2: ensure on feature branch, merge after approval
- Update Stage 3: archive after merge (can be on main)
- Update Happy Path Script with full branch/PR workflow
- Reduce AGENTS.md by 58 lines while preserving key guidance
- Consolidate branching strategy to single line
- Simplify workflow steps in all 3 stages
- Add openspec-branching eval to test agent compliance
@christso christso changed the title refactor: move openspec-branching eval to root evals/ refactor: openspec branching eval Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants