sdd-platform-spec

To define platform specs for cross-domain initiatives using SpecKit, you structure the workflow through prerequisite checks, constitution definition, platform spec creation, gap analysis via ADRs, and technical planning. This ensures all non-negotiables and domain responsibilities are encoded.

A platform constitution in SpecKit is a set of encoded platform standards covering UX, security, and observability. You need to set it up during the initial phase of platform spec creation to enforce non-negotiables before defining cross-domain initiative scope and contracts.

Gap analysis for platform specifications is conducted by generating Architecture Decision Records (ADRs) after defining the initial spec. ADRs identify missing domain responsibilities, UX requirements, or NFRs, ensuring the final platform spec adheres to the platform constitution.

Yes, the SpecKit workflow supports fan-out task generation for technical planning. After completing prerequisite checks, constitution setup, and gap analysis, it automatically generates downstream technical tasks to execute the cross-domain platform initiative.

Yes, you can use this SpecKit workflow to define both contracts and non-functional requirements (NFRs). It explicitly guides Platform Architects and Product Managers to satisfy requirements for domain responsibilities, contract definitions, and NFRs while ensuring adherence to platform non-negotiables.

The best way to enforce platform standards like UX and observability during spec creation is by defining a platform constitution using SpecKit. This constitution acts as a prerequisite check, ensuring all subsequent cross-domain features and technical plans adhere to these encoded non-negotiables.