101
Intro: what and why
The problem with default agents, what a skill is, and how to install and get a first win.
- The shortest-path problem
- Skill anatomy
- The lifecycle
- Your first spec
Teach & share
A media kit for the whole SDLC story
Everything you need to explain, teach, or post about agent-skills. Branded workflow diagrams, ready-to-present decks, and plain-language guides for solo work, teams, and customization. Grab anything here and reuse it freely. MIT licensed, no sign-up.
01 Learning tracks
101, 201, 301 - present or share in minutes
Three self-contained decks that build from first principles to team rollout. Present the HTML version right in the browser (arrow keys, F for fullscreen, P for PDF), or download the PPTX to edit and make your own.
201
The SDLC, in practice
The eight commands, the solo daily loop, and how each phase actually plays out.
- Eight commands
- The daily loop
- Define to Ship
- /build auto
301
Teams and customization
Review panels, context budgets, four ways to customize, evals, and rolling out to a team.
- Review panel
- Customize 4 ways
- Context engineering
- Evals and rollout
02 Workflow diagrams
Drop-in visuals, on brand
Five diagrams that explain the model at a glance. Download the SVG to keep it crisp at any size, or the PNG for a quick paste into a post, slide, or thread.
The SDLC lifecycle
Define to Ship, one command per phase. The core mental model in a single frame.
Solo daily loop
How one developer drives spec, build, test, ship, plus the hands-off /build auto option.
Team review panel
/ship fans out to four specialist personas in parallel, then merges one go / no-go.
Anatomy of a skill
Frontmatter, workflow, guardrails, and verification. Why a skill is a process, not a prompt.
Four ways to customize
Install all, pick a few, edit them, or write your own. Skills are plain Markdown.
03 How you use it
Same lifecycle, solo or as a team
The SDLC is the spine of the whole project. Here is how it plays out when you work alone, when you work on a team, and how to customize it for your own stack.
Solo projects
Move through the whole SDLC on your own
Install once, then drive each lifecycle phase with a single command. You approve at every checkpoint, and every slice is tested and committed on its own.
- /spec writes a short PRD before any code
- /build lands thin, tested vertical slices
- /build auto runs an approved plan hands-off
Team projects
Ship past a panel, not a rubber stamp
The same lifecycle scales to a team. /ship fans out to specialist review personas in parallel, then merges their findings into one honest go / no-go with the blocking items called out.
- code-reviewer, security-auditor, test-engineer, web-performance-auditor
- Anti-rationalization guards keep every phase honest
- Commit skills to version control for one shared source of truth
Customize
Bend the workflow to your stack
Skills are plain Markdown, so you own them. Install all 24, load only the few a task needs, fork a SKILL.md to add your house style, or write your own with the same anatomy.
- Context is a budget: load only what the task needs
- Fork any SKILL.md to encode team standards
- New skills follow the same process, guardrails, and verification
04 Share kit
Copy, paste, post
Snippets and assets sized for a quick share. Everything is copy-ready.
Made something with these?
Tag the project so others can find it. Everything here is MIT licensed and free to reuse.