sdd-lifecycle

Specification-driven development across microservices requires a phase-driven workflow that enforces Plan, Spec, Implement, Review, and Ship phases. It uses standardized artifacts like plan briefs, technical specs, and status tracking to coordinate cross-service delivery and align bounded contexts.

Aligning planning and specifications requires creating standardized artifacts before implementation. By generating plan briefs and technical specs within a structured workflow, teams coordinate cross-team dependencies and prevent miscommunication across bounded contexts in microservice architectures.

Tracking feature implementation status in a monorepo is handled using a standardized status tracking artifact. This status model integrates within the specification-driven lifecycle to monitor progress across planning, specification, implementation, review, and shipping phases.

Starting the workflow involves creating a feature directory and adding an initial plan brief alongside a technical spec. Following the Plan, Spec, Implement, Review, and Ship sequence ensures lifecycle governance and produces the required implementation logs for tracking.

Specification-driven development supports cross-team collaboration by enforcing a phase-driven workflow with standardized artifacts. It coordinates dependency management and lifecycle governance specifically for microservice architectures, ensuring teams align across bounded contexts during implementation.

Required artifacts for the lifecycle include plan briefs, technical specifications, status tracking files, and implementation logs. These artifacts enforce the workflow rules across planning, specification, implementation, review, and ship phases to ensure consistent multi-service delivery.