Skip to content

Architect & Specification

Phase 1: Architect designs the entire system

Roles: Architect + manual PM review.

Inputs: clean evidence from intake, existing AutoERP modules.

Activities:

  • Prepare an end-to-end design (data model, workflow, integrations, performance) before sprints.
  • Create the first version of openspec/specs/<module>/spec.md and spec.yaml (machine-readable if needed).
  • Record assumptions and blockers (e.g., feeds, integrations).
  • Run a manual review with PM (check against recording/email).

Output: Approved baseline specification ready for sprints. Without approval nothing is developed.

Phase 2: Specification and review (OpenSpec)

Goal: Every change has a delta specification and a link to the evidence source.

  • Directory: openspec/specs = current state; openspec/changes/<id> = change proposals. A proposal always references the source (source:) and contains proposal.md, tasks.md, specs/<module>/spec.md (delta).
  • Manual review: Architect/PM checks that acceptance criteria are complete, traceable to evidence, and avoid free-form text without scenarios.
  • Gherkin: acceptance criteria are written as scenarios; UI tests are generated from them.
  • Review ready: openspec validate --strict must pass before the sprint.

Architect checklist

  • [ ] End-to-end design is complete
  • [ ] Baseline specification is created
  • [ ] Assumptions and blockers are recorded
  • [ ] PM review completed
  • [ ] openspec validate --strict passed

➡️ Continue to Sprint Build.