hermes - 💡(How to fix) Fix Operating model: SDD, ADRs, DoR/DoD, and quality gates [1 pull requests]

Goal

Create the operating model for building the product with discipline and low ambiguity.

Required artifacts

1) Vision doc

• What the product is
• Who it is for
• What success looks like

2) Feature spec

• Objective
• User story
• Scope / non-scope
• Acceptance criteria
• Metrics

3) ADRs

• Why this architecture
• Why these build-vs-buy decisions
• Why this rollout path

4) Definition of Ready

A task is ready only if it has:

• clear objective
• scope
• acceptance criteria
• dependencies
• owner

5) Definition of Done

A task is done only if it has:

• implementation completed
• tests passing
• docs updated
• validation performed
• no unresolved critical issues

6) Review gates

• Spec approved before build
• Architecture approved before implementation
• QA/validation before release
• No PR merge while required checks are red

Orchestration rules

• Use GitHub issues as the source of truth for execution
• Link child tasks under epic issues
• Keep one issue = one coherent deliverable
• Prefer small issues over giant ambiguous ones

Acceptance criteria

• The process is short enough to use every day
• It prevents ambiguity without slowing execution too much
• It is suitable for a premium product team