project-domain

Capture and formalize project domain knowledge into a domain-model.md file.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill project-domain-telum-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-domain
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/project-domain
Command: npx skills add https://github.com/telum-ai/speck --skill project-domain-telum-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill captures and formalizes the specialized knowledge, terminology, and rules of a project's domain, ensuring all product decisions are informed by accurate subject matter expertise.

Core Features & Use Cases

  • Terminology Elicitation: Defines canonical terms and avoids synonyms.
  • Rule Definition: Captures domain-specific invariants and constraints.
  • Principle Identification: Documents foundational scientific or industry principles.
  • Use Case: For a new healthcare app, this skill would define terms like "patient encounter," "diagnosis code," and "treatment plan," and establish rules like "a diagnosis must precede a prescription."

Quick Start

Use the project-domain skill to create or update the domain model for the 'fitness-tracker' project.

Frequently Asked Questions about project-domain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture domain knowledge and ubiquitous language for a project specification?

You can capture domain knowledge by running interactive elicitation sessions to formalize canonical terms, constraints, and principles into a comprehensive domain-model.md file. This ensures all product decisions are informed by accurate subject matter expertise.

What is the best way to define project terminology and avoid synonyms in a domain model?

Defining project terminology requires interactive elicitation to identify canonical terms and eliminate synonyms. The process formalizes this ubiquitous language alongside domain rules and principles into a single domain-model.md file.

How do I document domain rules and invariants for a new software project?

Document domain rules and invariants through guided elicitation and just-in-time research. This process captures specific constraints, such as "a diagnosis must precede a prescription," and formalizes them within a domain-model.md file.

Do I need existing project artifacts to start building a domain model?

Yes, building a domain model requires context loading from existing project artifacts. The skill utilizes these inputs to guide the elicitation process and accurately formalize subject matter expertise.

Can I use just-in-time research to identify foundational industry principles for my domain?

Yes, the skill utilizes just-in-time research via MCP tools to identify and document foundational scientific or industry principles. This ensures the domain model accurately reflects specialized external knowledge.

When should I formalize subject matter expertise into a domain model?

You should formalize subject matter expertise when starting a new project or updating an existing specification. This captures specialized terminology, rules, and principles to ensure all subsequent product decisions are accurately informed.