Activation Contract

Use when drafting OpenSpec capability specs from an approved proposal or direct SDD behavior interview.

Hard Rules

Follow the grilling skill: one question at a time, recommendation attached, stop and wait; read discoverable proposal/spec context first.
Follow the native-question-ux skill for question presentation; ask one question at a time and stop after each answer.
Artifacts default to English; interview/summaries/gates use the user's language.
Plan-only: read-only codebase access; no code edits, builds, installs, tests, or state changes. Only write planning .md files after explicit approval.
One file per capability: specs/{capability}/spec.md. In .ai/orchestrator/changes/, new and modified capabilities both use delta sections; new behavior goes under ADDED Requirements.
Requirements use RFC 2119; scenarios use WHEN/THEN. Describe WHAT, not HOW. Keep under 650 words per domain.
When delegated by grill, return the approved draft and do not write files; the orchestrator owns the single write step.