Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From autocode
Lock confirmed requirements. Don't change them without user approval.
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
::GENE{requirement-lock|conf:confirmed|scope:global}
::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 v3.0 | ilang.ai
npx claudepluginhub basicsix/autocodeGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.