Skill

spec-feature

Creates and maintains domain specifications following the SDD approach. Use this skill when specs need to be written, features derived, or domain requirements documented. Pure domain language — no technical details like frameworks, HTTP methods, or data types.

Install

npx claudepluginhub mgoericke/javamark-claude-plugins --plugin sdd-toolkit

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create domain specifications in pure business language. Specifications describe *what* the system should do, never *how* it is technically implemented.

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

167.4k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

167.4k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

167.4k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 30, 2026

Actions

View Source View Plugin View on GitHub View README

Spec-Feature Skill

Purpose

Create domain specifications in pure business language. Specifications describe what the system should do, never how it is technically implemented.

Rules

Strict Separation

IN the Spec: Domain requirements, business rules, actors, processes, domain terms

NOT in the Spec: Framework names, HTTP methods, data types, queue names, database schemas, package structures

Structure of a Domain Spec

# Feature: [Feature Name] ## Context [Why is this feature needed?] ## Actors [Who interacts with the feature?] ## Domain Requirements [What should the system be able to do?] ## Business Rules [What rules apply?] ## Acceptance Criteria [When is the feature complete?]

Anti-Patterns (FORBIDDEN in Specs)

❌ "The REST endpoint returns..."

❌ "The entity has the following fields: String name, Long id..."

❌ "Via RabbitMQ message..."

❌ "The Quarkus extension..."

Correct Domain Formulations

✅ "The system allows the user to..."

✅ "Upon receiving a request, the system validates..."

✅ "The requester receives a confirmation..."

Workflow

Analyze the user's requirement

Identify actors and business processes

Formulate purely domain-level requirements

Define business rules and acceptance criteria

Create the spec file under specs/ in the project

Spec-Feature Skill

Purpose

Create domain specifications in pure business language. Specifications describe what the system should do, never how it is technically implemented.

Rules

Strict Separation

IN the Spec: Domain requirements, business rules, actors, processes, domain terms
NOT in the Spec: Framework names, HTTP methods, data types, queue names, database schemas, package structures

Structure of a Domain Spec

# Feature: [Feature Name]

## Context
[Why is this feature needed?]

## Actors
[Who interacts with the feature?]

## Domain Requirements
[What should the system be able to do?]

## Business Rules
[What rules apply?]

## Acceptance Criteria
[When is the feature complete?]

Anti-Patterns (FORBIDDEN in Specs)

❌ "The REST endpoint returns..."
❌ "The entity has the following fields: String name, Long id..."
❌ "Via RabbitMQ message..."
❌ "The Quarkus extension..."

Correct Domain Formulations

✅ "The system allows the user to..."
✅ "Upon receiving a request, the system validates..."
✅ "The requester receives a confirmation..."

Workflow

Analyze the user's requirement
Identify actors and business processes
Formulate purely domain-level requirements
Define business rules and acceptance criteria
Create the spec file under specs/ in the project