Criterion 2

Versioned system design

Ratings 2026-10

A complete, integrated description of the intended system for a selected version is available before implementation finishes. Proposed, approved but unimplemented, and implemented changes are distinguishable. Delivered code identifies the governing design version.

Coverage levels

1. Level 1 Persistent intended design for a feature or area; an integrated approved system target is missing.
2. Level 2 A maintained integrated target or controlled baseline exists; delivered-code/design binding or state distinctions remain incomplete.
3. Level 3 A complete selected-version target distinguishes proposed, approved-unimplemented and implemented states; delivered code identifies its governing design.

Product ratings

• GitHub Copilot coding agent ?

  Repository instructions and task sessions do not establish a complete intended system description with approval/implementation states and governing design versions.

  Read the rating and evidence

• Azure DevOps + Copilot

  Persistent work items, revision history and lifecycle states preserve parts of the system intent.

  Read the rating and evidence

• Atlassian suite (Confluence, Jira, Rovo Dev)

  Confluence page versions and Jira lifecycle states retain documents and work state.

  Read the rating and evidence

• AWS Kiro

  The reviewed workflow retains feature specifications.

  Read the rating and evidence

• GitHub Spec Kit

  A living-spec maintenance option is documented alongside per-feature history.

  Read the rating and evidence

• OpenSpec

  Active change proposals describe intended changes; archive merges deltas into current capability specs.

  Read the rating and evidence

• BMAD Method + Test Architect

  Persistent PRD, UX, architecture and plans form a system-level target; plans retain baseline revisions.

  Read the rating and evidence

• Tessl

  Specs persist and can be maintained in place.

  Read the rating and evidence

• Jama Connect

  Versioned items, lifecycle states, baselines and signed reviews preserve an approved requirement/design set before implementation.

  Read the rating and evidence

• Siemens Polarion

  Versioned LiveDocs and hierarchical release/phase Collections retain approved requirements, design and tests, including future releases.

  Read the rating and evidence

• Factory.ai (Droid + QA) ?

  The reviewed Droid/QA documentation does not establish a complete versioned system design with approval/implementation states and governing design versions for code.

  Read the rating and evidence

Back to comparison