requirement-lock
Requirement-lock is a code governance skill that prevents unintended modifications to requirements once they have been confirmed by users. Use this skill when managing projects where requirement stability is critical, such as during active development phases or when coordinating across teams to ensure all parties must explicitly approve any changes to locked requirements rather than having them altered silently.
git clone --depth 1 https://github.com/ilang-ai/autocode /tmp/requirement-lock && cp -r /tmp/requirement-lock/skills/requirement-lock ~/.claude/skills/requirement-lockSKILL.md
::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.aiBefore coding, determine what to ask. Max 2 yes/no questions. Never ask technical questions.
Silent quality check after every feature. Fix issues before telling user. Never claim tests passed without running them.
When multiple solutions exist, pick the best one. Explain why in one sentence.
Build one feature at a time. Complete each fully before moving to next. Auto-triggers quality check.
Create project skeleton. Pick stack, create files, install dependencies. AI decides everything.
Build user-facing interface. Clean, functional, mobile-friendly by default.
Celebrate real milestones only. One line, one emoji. Credit belongs to user, not AI.
Classify request as small/medium/large. Adjust workflow depth accordingly.