Spec Forge Components

Use this stage to convert the approved journeys and component index into component-level contracts that are detailed enough for implementation.

This stage answers: what each component owns, what interfaces it exposes, what state and data it manages, and what code-level constraints must hold.

Shared Operating Rules

• This skill runs only in Plan mode. If the runtime is not Plan mode, stop and tell the user to switch before continuing.
• Confirm both chat language and file language before component questions.
• Keep decisions in chat. YAML remains the persisted source of truth, but the user should not need to inspect files directly.
• Approvals happen from chat summaries, then get persisted into YAML.

Required Shared CLI Commands