sdd-component-spec

To write a component implementation spec, you define how your service implements platform specifications by declaring mandatory source references and passing structural gate checks. This ensures your service accurately reflects platform intentions and adheres to domain invariants.

An OpenSpec component implementation spec is used to document how a specific service implements platform-level requirements. It defines the service-level how-to implementation derived from platform specs, ensuring integration contracts and domain invariants are strictly followed.

To ensure your component spec includes necessary platform sources, you must enforce referencing platform and domain MCPs for all spec sections. This mandatory source declaration prevents inventing requirements and maintains alignment with platform specifications.

Yes, you can use this to document service-level implementation for a fan-out task. When a component team engineer receives a fan-out task from the Platform Repo, this skill guides them to generate the complete Component Spec with all necessary sections and sources included.

Gate checks for OpenSpec component spec approval and readiness include a structured checklist verifying spec completeness, domain validity, integration safety, and NFR compliance. These checks ensure the spec is fully prepared before actual implementation begins.

Yes, writing a component spec requires referencing domain MCPs. The skill enforces mandatory source declarations that reference both platform and domain MCPs across all spec sections to prevent inventing unverified requirements.