Implementation sub-skill: Database
Builds the database schema and migrations from the approved architecture. The first of implementation's four sub-skills, and the first to write actual code rather than a planning document.
Claude CodeLast reviewed September 3, 2026
In one minute
- A sub-skill of Implementation, invoked first of its four.
- Reads
docs/product/planning.mdfor the architecture. From here on, the sub-skills in this phase stop reading and writingdocs/product/files, and start reading and writing the codebase itself. - Writes migrations, not a hand-edited database, so the change is reviewable and repeatable, the same reason a hook runs a formatter instead of asking Claude to format by hand.
SKILL.md
.claude/skills/database-implementation/SKILL.md
yaml
---
name: database-implementation
description: Builds the database schema and migrations from the architecture in docs/product/planning.md. Use as the first of implementation's four sub-skills, invoked by /implementation, before any code that depends on the schema.
---
Read docs/product/planning.md for the architecture.
Write the schema as migrations, not a hand-edited database, so the change is reviewable and repeatable.
Do not add a table or column the architecture did not call for without flagging it.Where it fits
Invoked by Implementation, first of its four sub-skills. Hands off to Backend, which builds against the schema this skill just wrote.
Last reviewed September 3, 2026