Reusable AI agent skills maintained in this repository. The work is shaped by
Sebastian Wessel's article
Spec-Driven Development,
which explains this repository's spec-first approach for keeping autonomous AI
agents aligned from business intent through implementation and review. Each
skill lives in its own subdirectory under skills/ and follows Anthropic's
Agent Skills best practices.
Contents
- Skill Index
- Spec-Driven Development
- Installation
- Repository Layout
- Documentation Pattern
- Adding a Skill
- Maintainer Notes
Skill Index
| Skill | Description | Human docs |
|---|---|---|
| spec-architect | Use when specs need creation, review, repair, or approval before autonomous or parallel AI implementation without ambiguity, invention, interface mismatch, drift, or gaps. | docs |
| spec-implementation-planner | Use when approved specs need end-to-end waves, AFK tickets, parallel-agent plans, dependencies, status tracking, or readiness checks. | docs |
| spec-implementation-review | Use when a completed or partial spec implementation wave, plan, or cross-ticket solution needs review before acceptance, merge, release, or handoff. | docs |
| spec-ticket-implementation | Use when implementing one approved spec plan ticket with strict read/write scope, acceptance verification, dependency checks, and no implementation-time decisions. | docs |
Spec-Driven Development
Read Spec-Driven Development for the rationale behind this repository. The article describes how clear specs, implementation plans, ticket execution, and review gates work together so AI agents can build production-ready systems without drifting from the intended business outcome.
Installation
Install this skill package with the open skills ecosystem CLI:
npx skills add sebastianwessel/skills
See Vercel's announcement of
skills
and skills.sh for the package ecosystem.
Repository Layout
skills/
└── <skill-name>/
└── SKILL.md
Optional per-skill directories include references/, scripts/, assets/,
and agents/.
Human-facing skill documentation lives outside the executable skill package:
docs/
└── skills/
└── <skill-name>.md
Documentation Pattern
Each skill should have a concise human docs page with the same structure:
- What the skill is for.
- Installation.
- What it does.
- How it works.
- Workflow or modes.
- Included files.
- Validation and safety notes.
Adding a Skill
-
Create
skills/<skill-name>/SKILL.md. -
Use concise YAML frontmatter with
nameanddescription. -
Keep detailed reference material in files linked directly from
SKILL.md. -
Add
docs/skills/<skill-name>.mdfor human-facing documentation. -
Refresh this table of contents:
python3 scripts/update-readme.py
Maintainer Notes
Repository instructions for agents are in AGENTS.md. Claude reads CLAUDE.md, which points back to the same shared guidance.


















