メニュー
Use when cybernetic requirements or solution design has a genuinely open search space and needs candidate paths, trade-offs, and discriminating questions before commitment.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a formed task needs durable human-approved meaning, completion obligations, evidence claims, non-goals, or live/destructive authority boundaries.
Use when maintaining or resuming an existing v1 requirements.control.json run; new runs use forming-cybernetic-commitments.
Use when an existing v1 run must compile its reviewed control chain into runtime.control.json.
Use when optional local workflow guidance or legacy v1 workflow compatibility needs diagnosis.
Use when an existing v1 control chain requires design.control.json; v2 strategies remain agent-owned.
Use when cybernetic routing is requested but user input is pre-task intent or role-ambiguous context: confusion, dissatisfaction, risk sense, observed symptoms, failed attempts, method preference, process distrust, source material, declared current state, or unclear requested transformation.
| name | cybernetic-brainstorming-workflow |
| description | Use when cybernetic requirements or solution design has a genuinely open search space and needs candidate paths, trade-offs, and discriminating questions before commitment. |
Explore competing interpretations or solution paths before commitment while preserving requirement provenance and authority.
