Thanks for contributing.
Good contributions usually improve one of these areas:
- protocol clarity
- role boundary definitions
- review and archive rules
- template usability
- example quality
- automation ideas that do not replace the source of truth
- vendor-specific assumptions
- hidden state that depends on chat memory
- workflows that collapse planner, implementer, and reviewer into one implicit role
- automation that silently changes acceptance or archive state
- explain the problem first
- propose the smallest rule or template change that fixes it
- include an example when the change affects workflow semantics
- avoid adding complexity unless it prevents a real failure mode
Changes should preserve these principles:
- file-based handoff
- explicit role boundaries
- tests as primary executable verification
- review writeback before chat summary
- opt-in automation
If you change workflow semantics, include or update an example under examples/.