메뉴
Use when an approved non-trivial cybernetic requirements, design, and goal chain must be converted into an executable plan.control.json strategy before review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | cybernetic-planning-workflow |
| description | Use when an approved non-trivial cybernetic requirements, design, and goal chain must be converted into an executable plan.control.json strategy before review. |
Turn approved meaning into a candidate execution strategy without changing the
meaning, approving the strategy, or executing target work. The owning
writing-cybernetic-execution-policies skill writes the official JSON artifact.
Read the approved requirements.control.json, any required
design.control.json, and goal.control.json. Treat their required outcomes,
non-goals, authority boundaries, and completion predicates as immutable inputs.
Main-only, Serial subagent-driven, or Parallel subagent-driven
using the delegation registry and approved human/live gates.Do not impose TDD, red-green order, test counts, or per-package tests. Include a test only when it captures a real counterexample, protects a critical invariant, or materially lowers repeated acceptance cost. Counterexample Gate remains the semantic quality entry.
Return a complete candidate strategy to the owning execution-policy skill. It
must be representable by the current plan.control.json schema and must not rely
on conversational context that runtime cannot read.
shared_infrastructure and return to pre-goal diagnosis.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.