adapt-to-stack

Generate layer specialist agents and standards skills from a repo's CLAUDE.md chain declaration.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill adapt-to-stack-konstantinos-malavazos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt-to-stack
Source: https://github.com/konstantinos-malavazos/claude-code-playbook/tree/main/templates/skills/adapt-to-stack
Command: npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill adapt-to-stack-konstantinos-malavazos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up per-layer specialist agents and engineering-standards skills by hand duplicates information already declared in a repo's CLAUDE.md, and hand-written copies drift out of sync with the declared layer chain. This Skill reads the chain declaration once and generates the matching agent and skill files, creating only what is missing and never overwriting existing files. ## Core Features & Use Cases - Chain-driven generation: Reads the layer chain, build/test commands, and contracts from the repo's own CLAUDE.md and produces one layer specialist, one slice-mode variant, and one standards skill per layer. - Idempotent, non-destructive runs: Skips files that already exist, detects stale model comments and unfilled placeholders, and reports disagreements between generated files and the current chain without editing anything. - Structured reporting: Ends every run with a per-file report classifying each row as created or skipped, plus findings like still-a-scaffold or disagrees-with-CLAUDE.md, and flags when a session restart is needed. - Use Case: After scaffolding a new repo whose CLAUDE.md declares a schema-api-web chain, run this Skill to populate .claude/agents/ and .claude/skills/ with the nine corresponding files, then re-run it months later when a fourth layer is added to generate only that layer's files. ## Quick Start Ask the AI to adapt this repository to its declared stack by generating the layer specialists and standards skills from the repo's CLAUDE.md.

Frequently Asked Questions about adapt-to-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Claude Code specialist agents for each layer of my repo?

Declare the layer chain, paths, and build/test commands in the repo's CLAUDE.md, then run this Skill. It creates one layer specialist, one slice variant, and one standards skill per layer under .claude/agents/ and .claude/skills/.

What input does the adapt-to-stack skill need?

The only input is the repo's own CLAUDE.md containing a filled-in chain section and build/test commands. If the file is missing, unfilled, or still has placeholder brackets, the Skill stops and tells you which sections are needed.

Does adapt-to-stack overwrite my existing agent files?

No. It creates only missing files and leaves existing ones untouched. Files that disagree with the current CLAUDE.md chain are flagged in the report as disagreements, never edited or regenerated.

What happens when I re-run adapt-to-stack after adding a layer?

The re-run generates the three files for the new layer only and skips everything that already exists. This is also how repos generated before the slice-variant step existed receive their missing slice variants.

Why does the report say my session needs a restart?

A running session only watches the .claude directories that existed when it started. If the run created .claude/agents/ or .claude/skills/ for the first time, dispatching to the new files requires restarting the session.

When should I not use adapt-to-stack?

Do not use it to write CLAUDE.md itself, to edit an already-generated file, or to generate workspace-wide conventions like commit-conventions. It only translates an existing chain declaration into per-layer agent and skill files.