Claude Code Introduces Agent and Skill Frameworks to Enforce Senior‑Engineer Workflows
Create a SKILL.md file with a clear description and trigger words so Claude auto‑discovers it; place it in .claude/skills/<name>/ and restart Claude Code to use it.
Create a .claude/skills/<name>/SKILL.md file with a descriptive name and trigger words, then restart Claude Code to enable the skill.
Summary
Anthropic’s Claude Code platform has rolled out a new “Agent Skills” plugin that scaffolds AI coding agents with a disciplined, senior‑engineer‑style workflow. The plugin has already attracted 26 000 GitHub stars and is organized around 20 markdown‑based skills that map to six software‑development lifecycle phases—Define (/spec), Plan (/plan), Build (/build), Verify (/test), Review (/review), and Ship (/ship)—plus an optional /code‑simplify command. Each skill file contains frontmatter that the agent loads on demand via a router skill, allowing the system to reveal only the necessary steps and keep token usage low.
The design incorporates anti‑rationalization tables that pre‑empt common excuses for skipping work, enforce scope discipline, and require concrete evidence—such as passing tests, a clean build, runtime traces, and reviewer sign‑off—before the agent can exit a phase. The approach draws heavily on Google’s engineering practices, including Hyrum’s Law, the test pyramid, and trunk‑based development, providing teams with a ready‑made framework for integrating AI into their existing pipelines.
In parallel, Claude Skills offers reusable playbooks that fire automatically when Claude recognizes a task, eliminating repetitive prompts. A skill lives in a folder with a SKILL.md file that contains a YAML frontmatter—name, description, and optional disable‑model‑invocation flag—followed by a playbook of steps, examples, and rules. The description must include trigger phrases that match how users actually ask for the task, ensuring the skill activates only when appropriate. The body of SKILL.md can reference additional files for style guides or API documentation, which are loaded only when the skill runs, keeping token costs low. Anthropic ships a skill‑creator that walks users through drafting the frontmatter and playbook, and skills can be shared across projects by placing them in ~/.claude/skills/. They can also be disabled from auto‑firing and invoked manually with /skill‑name, useful for actions that have side effects such as publishing to a CMS or sending a Slack message.
Together, these tools aim to bring the rigor of senior‑engineer workflows to AI agents, enabling teams to adopt automated coding assistance without sacrificing quality or oversight. By combining structured skill sets with reusable playbooks, Claude Code offers a comprehensive ecosystem that supports disciplined development, reduces token waste, and encourages best practices across the software‑engineering lifecycle.
Key changes
- A skill is a directory with a single SKILL.md file containing YAML frontmatter (name, description) and markdown body
- The description drives auto‑discovery; it must start with a clear verb and include trigger phrases
- Skills live in three scopes: project (.claude/skills/), personal (~/.claude/skills/), or shared packages
- Project‑level skills override personal ones when both exist
- A single skill file automatically provides a slash command (e.g., /run‑tests) for manual invocation
- Restarting Claude Code loads new skills and triggers auto‑discovery on each message