Record an approved technology stack in Claude Code

After approval, document the stack categories, exact versions, scope exclusions, and change approval rules.

Install in Claude Code

The ateschh-kit workflow in Claude Code. Obtain a proposed stack from the requirements expert and explicit user approval.

Review `.claude/skills/requirements-lock/SKILL.md` and its requirements at the pinned GitHub commit.
Create `.claude/skills/requirements-lock/` in your project and save the reviewed file as `.claude/skills/requirements-lock/SKILL.md`.
Start Claude Code from that project's root, then select `/requirements-lock` in the slash menu.

Example task

A fictional stack is ready to lock. Its approval includes `{library:'Vue',version:'3.5.13',purpose:'interface'}`. The remaining category versions are recorded, and offline sync is out of scope.

What to check

Record Vue `{library:'Vue',version:'3.5.13',status:'LOCKED'}` using its approved version. Keep the scope exclusion, check the remaining entries, and add the stack lock to the decision log.

Original SKILL.md on GitHub · Updated 2026-11-14

Frequently asked question

When should a stack requirements file become locked?

Obtain approval for the proposed stack. Confirm the versions and purposes, record what is outside scope, then preserve the lock and the policy for later changes.