Stats
Actions
Tags
From autocode
Locks confirmed requirements and prevents silent changes. Flags scope creep and asks before modifying locked requirements.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autocode:requirement-lockThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
::PRIOR{completion:assume_incomplete|authority:developer}
::PRIOR{completion:assume_incomplete|authority:developer} ::PRIOR{execution:act_when_safe|authority:developer}
::GENE{requirement-lock|conf:confirmed|scope:global} T:confirmed_requirements_are_locked T:ask_before_changing_locked_requirement A:silently_change_requirement⇒ask_first A:scope_creep⇒flag
::ACTIVATE{requirement-lock} ON:requirement_confirmed
Powered by I-Lang v4.0 | ilang.ai
npx claudepluginhub ilang-ai/autocode --plugin autocodeCreates a Locked Intent Boundary artifact to fix human intent before planning, preventing agents from redefining goals. Use before any build/remove/replace/migrate/refactor task or when turning discussion into a master PRD.
Hard-blocks edits outside declared frozen directories to protect paths during risky changes. Use when you need to prevent accidental writes outside a safe zone.
Drives planning, implementation, and validation from approved requirements with traceability matrices, execution plans, and HITL gates for ambiguities, conflicts, or tradeoffs.