V1.4.0

v1.4.0 — SpecBridge Integration

What's New

Contract testing is now handled by SpecBridge.

The /sdd-spec phase now produces two outputs:

• PRD.md — business behaviour in human-readable Given/When/Then format
• {feature}.feature — SpecBridge HTTP contract (machine-executable)

The /sdd-verify phase now runs specbridge verify against your live
API instead of relying on hand-written contract test code.

Breaking Changes

• /sdd-test removed. Contract tests are no longer generated as
  source code. The .feature file is the contract.
• Output paths unified to .gsi/.
  All phase outputs (PRD.md, *.feature, architecture.md,
  conclusion.md) now live under .gsi/{feature_name}/.
  Previously some outputs were written to docs/features/ or features/
  — update any existing scripts or CI steps accordingly.

Migration

If you have existing .feature files written in the old
business-behaviour Gherkin format (Given/When/Then with domain language),
they are not directly compatible with SpecBridge.
Re-run /sdd-spec on the original requirement to regenerate both
PRD.md and the new HTTP contract .feature.

Prerequisites

SpecBridge must be installed before running /sdd-verify:

npm install -g @ksz54213/specbridge

Full Changelog: v1.3.2...v1.4.0

Version 1.3.2

v1.3.2

feat update version to 1.3.2

Version 1.3.1

v1.3.1

feat: update version to 1.3.1

Version 1.3.0

Full Changelog: v1.2.2...v1.3.0

Version 1.2.2

v1.2.2

feat: update version to 1.2.1

Version 1.2.1

v1.2.1

feat: update version to 1.2.1

Version 1.2.0

v1.2.0

feat: add command for unit-test (only template)

Version 1.1.3

v1.1.3

feat: update spec content

Version 1.1.2

v1.1.2

feat: update version to 1.1.2

Version 1.1.1

v1.1.1

feat: update version to 1.1.1