跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

freeze

Scope lock for current task. Declares editable zone — everything outside is frozen (read-only). Call before starting implementation to prevent scope creep.

AlexZio00 · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add AlexZio00/sovereign-skills --skill freeze

技能说明


skill_type: utility tools: Read name: freeze description: "Scope lock for current task. Declares editable zone — everything outside is frozen (read-only). Call before starting implementation to prevent scope creep." depends_on: skills: [] agents: [] files: [] concurrency_profile: read_only: true concurrency_safe: true destructive: none tags: [meta, safety] version: "1.0.0" source: "garrytan/gstack freeze pattern" triggers:

  • "/freeze"
  • "freeze this"
  • "scope lock"
  • "스코프 잠금"
  • "이것만 건드려"
  • "나머지 건드리지 마"
  • "범위 잠가" user_invocable: true not_for:
  • "Scope planning -> scope skill"
  • "Execution loop -> goal-lock" see_also:
  • skill: scope relation: "freeze=zone lock, scope=planning scope"
  • skill: goal-lock relation: "freeze=manual lock, goal-lock=loop enforcement"

/freeze — Scope Lock

Declare editable zone — everything outside is frozen.

Dominant Variable

In this task, is the editable scope explicitly declared? — If unclear, scope creep naturally develops during implementation. First of three principles (freeze / careful / guard): freeze = boundary lock (this skill), careful = 3-strike debugging gate, guard = risky path protection.

Trigger

  • /freeze
  • "freeze this"
  • "scope lock"
  • "스코프 잠금"
  • "이것만 건드려"
  • "나머지 건드리지 마"
  • "범위 잠가"

Discard If

  • Exploration / research only (no modifications expected)
  • Already a clear single-file edit (1 file, ≤10 lines)
  • Brainstorming phase (scope not yet finalized before design approval)

Key Assumptions

  1. User specifies ≥1 modification target — If broken: ask once for clarity; if still unclear, freeze broadly.
  2. Implementation work follows in the same session — If only declaring scope and ending, this skill is unnecessary.

Architecture

User input (file / module / concept scope)
    ↓
[PARSE]   → classify as editable / frozen / read-only
    ↓
[DECLARE] → generate FROZEN SCOPE block
    ↓
[OUTPUT]  → emit immediately, then exit

Stage 1: PARSE

Extract from user input:

  • editable: explicitly named files / modules / paths — modifications allowed
  • frozen: everything else (default frozen if not mentioned)
  • read-only: mentioned but modification status unclear → conservatively treat as read-only

If scope is too vague ("everything", "roughly") → ask for clarity once only. Still unclear → freeze more broadly (Invariant 2).


Stage 2: DECLARE

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔒 FROZEN SCOPE — [One-line task description]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✅ EDITABLE (modifications allowed)
  [list of files / modules]

❌ FROZEN (no modifications)
  [everything else — or "all except above"]

⚠️  READ-ONLY (reference only)
  [mentioned but no modifications allowed]

Rules:
- FROZEN files: Edit/Write forbidden. Read only.
- If modification necessity discovered → stop immediately, report to user
- Thaw: user must explicitly say "unfreeze [file]" or "expand scope"
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Stage 3: OUTPUT

Emit FROZEN SCOPE block, then exit immediately. No code generation, no agent spawning, no implementation start.

All implementation work in this session follows this declared scope.


Output

The only artifact this skill produces is the FROZEN SCOPE block itself, emitted straight into the conversation — nothing is written to disk. The block is the state (see Design Note below): there is no external file to persist or reload, so "declared" means "visible in this reply," not "saved somewhere."


Hard Rules

  1. Emit immediately, exit immediately — no "I'll now start implementing" after declaration.
  2. No agent spawning — main context only.
  3. No code generation — scope declaration only.
  4. Ask for clarity at most once — if still unclear, freeze more broadly.

Scope Boundary

DoesDoes NOT
[READ] Parse user input → classify editable/frozen/read-onlyWrite code or modify files
Emit FROZEN SCOPE blockSpawn agents or start implementation
Ask for clarity once if scope is ambiguousMake direct judgment calls on out-of-scope modifications

Safety Layers

Risky ActionReversibilityApplied Layers
(none — read-only, block output only)—L1 (Invariant 1: no modifications to frozen files, ever)
  • L1 (Invariants): Frozen = intended instruction-level block on Edit/Write (a declarative constraint, not sandbox/hook-enforced). Exit immediately after declaration.

Error Recovery

On failure detection: Stop → Classify → Apply Recovery → Report & Resume.

Failure TypeDetection ConditionRecovery Path
input_errorUnclear which files / scope to freezeAsk once for target — never guess scope
logic_inconsistencyFreeze request conflicts with simultaneous modification requestClarify: "This file will be frozen — modification requests rejected." Do not allow both.
missing_dataSpecified file does not existState "file not found." Do not guess paths and freeze different files.

Invariants (never violate)

  1. Frozen = absolutely no modifications: Files declared frozen cannot be edited/written in this session. "Just a tiny tweak" is rationalization. Violation → scope creep and unexpected side effects.

  2. When unclear, freeze broader: If boundaries are ambiguous, choose the broader frozen range. Narrow scope fails to prevent creep. Violation → freeze declaration becomes meaningless.

  3. Exit immediately after declaration: No further action after emitting FROZEN SCOPE block. User initiates follow-up implementation requests normally. Violation → declaration and implementation blur, scope awareness fades.


Thaw Protocol

When a frozen file needs modification mid-work:

Trigger: "unfreeze [file]", "thaw", "expand scope"

Steps:

  1. State reason — why the frozen
阅读完整来源 ↗