domain-population

Populates domain specifications from SPEC.md content using a CLI workflow.

39|3|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill domain-population
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-population
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/domain-population
Command: npx skills add https://github.com/LiorCohen/sdd --skill domain-population

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and synchronization of domain knowledge artifacts by extracting concepts from SPEC.md and updating glossary, entity definitions, and use-case stubs during implementation.

Core Features & Use Cases

  • Glossary population: Updates specs/domain/glossary.md with discovered entities.
  • Entity & Use-Case scaffolding: Creates specs/domain/definitions/<entity>.md and specs/domain/use-cases/<workflow>.md stubs.
  • Snapshot update: Updates specs/SNAPSHOT.md with product overview.

Quick Start

Run the domain population CLI workflow to scaffold domain artifacts from SPEC.md in your project.

Frequently Asked Questions about domain-population

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

FAQPage Schema
How do I scaffold domain specs from a SPEC.md file?

Scaffolding domain specs from SPEC.md is automated by extracting domain concepts to populate glossary entries, create entity definition stubs, and generate use-case files deterministically using a system CLI.

What is the best way to generate entity definitions and use-case stubs from a product specification?

Generating entity definitions and use-case stubs from a product specification involves parsing SPEC.md content to automatically create structured markdown files for domain entities and workflows while preserving existing content.

How do I update a project glossary and SNAPSHOT.md from a domain specification?

Updating a project glossary and SNAPSHOT.md from a domain specification requires extracting discovered entities from SPEC.md to refresh the glossary and update the product overview in the SNAPSHOT file.

Can I populate domain knowledge artifacts without overwriting existing markdown content?

Populating domain knowledge artifacts without overwriting existing markdown content is supported by the system CLI, which deterministically scaffolds domain files and preserves existing content during the glossary and entity definition updates.

When should I use automated domain spec population during software implementation?

Automated domain spec population should be used during software implementation when you need to synchronize domain knowledge artifacts by creating entity and use-case stubs alongside updating the glossary and product overview.

Does domain-population work with existing SPEC.md files to create definition stubs?

Domain-population works with existing SPEC.md files to create definition stubs by extracting concepts from the specification and scaffolding the corresponding domain entity and use-case markdown files.