メニュー
Use when older prompts invoke cybernetic clarification terminology; prefer analyzing-cybernetic-requirements for formed task requirements analysis.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
SOC 職業分類に基づく
| name | clarifying-cybernetic-tasks |
| description | Use when older prompts invoke cybernetic clarification terminology; prefer analyzing-cybernetic-requirements for formed task requirements analysis. |
Deprecated alias for $analyzing-cybernetic-requirements.
When invoked, perform the requirements-analysis workflow from:
.agents/skills/analyzing-cybernetic-requirements/SKILL.md
Use the current official control path:
docs/cybernetics/runs/<slug>/requirements.control.json
Do not create legacy Markdown clarification or requirements files. Historical Markdown is non-authoritative background only.
Compatibility terms:
requirements.control.json.The limit is unchanged: this alias may analyze requirements, rubrics, safe defaults, blocking decisions, and checks, but it must not resolve solution design, write goals, write plans, review approved work chains, compile runtime /goal, or execute target work.