메뉴
Deprecated compatibility wrapper for explicit legacy invocation of `process-budget-controller`. Do not auto-activate; use the active router's minimum-skill and process-budget policy instead.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | process-budget-controller |
| description | Deprecated compatibility wrapper for explicit legacy invocation of `process-budget-controller`. Do not auto-activate; use the active router's minimum-skill and process-budget policy instead. |
Deprecated compatibility wrapper.
Skill-count caps and process restraint now belong to the active router or repository policy so selecting a budget does not require another skill. This wrapper remains only for older prompts, profiles, and artifacts that explicitly name process-budget-controller.
When explicitly invoked:
Read Migration when interpreting an old tier, profile, artifact, or workflow.
Remove this wrapper only after active profiles, routing artifacts, governed records, and external consumers no longer reference the legacy name.
Use for enforcing hard limits on cached artifacts, summaries, indexes, and other compact metadata files so they stay bounded and high-signal.
Use for maintaining a rolling summary of only the last 10 conversations and refreshing matched history entries instead of appending unbounded cache.
Manage an explicitly approved rename, merge, supersession, discouragement, deprecation, or removal with compatibility routing and evidence-based exit criteria. Do not activate for ordinary edits, speculative consolidation, or a direct correction with no lifecycle impact.
Design, add, or amend tests for changed behavior with surface-appropriate coverage. Use when test design or test-file changes are part of the task; do not activate merely to run an existing test command, and use Playwright only when a browser-visible flow changed.
Perform an explicitly requested repository file-hygiene review or maintenance pass focused on factual accuracy, freshness, consistency, and duplicate or stale file prevention; read-only audits do not authorize corrections.
Use for designing and maintaining repository file structure for clarity, modularity, discoverability, and low-duplication across app and documentation surfaces.
