11/18/2026
Speck skills: Build a structured context layer for modeling product and design decisions
I’ve been refining a set of skills that collect concepts from jobs-to-be-done, domain-driven design, and ontologies to build out a structured context layer to help with modeling product and design decisions. The skills create and refine six kinds of interlinked notes:
- Entities: the core nouns of a product, with their fields, relations, and invariants.
- Jobs: the jobs users hire the product to do, including the situation, the outcome, and the forces acting on them.
- Performers: the roles that execute those jobs, defined by what they do rather than who they are.
- Surfaces: where the product is delivered, such as a web app, an API, or an MCP server.
- Workflows: the concrete sequences of steps that carry out a job.
- Constraints: implementation commitments, kept separate from the functional notes they apply to.
Notes link to each other using wiki links, so the same context can also be opened as an Obsidian vault and browsed through the graph view.
You can find an example of a todo app modeled using these skills, along with instructions to install the Claude plugin, in the GitHub repo.