Glossary
Skill
A skill is a reusable brief attached to a work item. Before an AI agent touches a single line of code, it reads every skill attached to that card.
Examples
- backend-designREST conventions, service boundaries, and error handling patterns for the Go API.
- database-migrationsSafe, reversible schema changes with rollback steps before any destructive ALTER.
- code-reviewWhat to look for in a diff: logic correctness, edge cases, test coverage, naming.
- security-architectureSTRIDE threat modelling rules and credential-hygiene checks applied to every card.
- technical-writingTone, structure, and brevity principles for changelog entries and inline docs.
How it fits the product
Skills live at the board level and attach to individual cards. One skill can be attached to dozens of cards simultaneously — the standard travels with the work rather than living in a shared doc nobody reads. When you run /breakdown in Claude Code, the agent automatically picks the right skills for the card it is creating. When you run /doing, every attached skill is loaded into the agent's context before execution begins. Skills exist in three layers: shipped defaults provided by Kontekstboard, team or enterprise policies, and personal overrides.