Back to Home

Spec Formats & Domains in Palmz

Choose a primary authoring style, then compose optional domains like Infrastructure, Data, or Telemetry. Palmz turns your selection into structured, AI-ready specs.

Overview: Primary vs Add-On

Palmz separates HOW you write a spec from WHAT domains it covers

Primary Authoring Style

Pick ONE (mutually exclusive). Sets base schema and tone.

Examples: EARS, BDD, User Stories, Palmz Structured, INCOSE/IEEE, GitHub Spec-Kit, Kiro Spec.

Add-On Domains

Multi-select. Augment with Infrastructure, Data, Telemetry, Tests, Prompt, or Policy sections.

Combine domains to match your workflow—Infrastructure + Data, or Telemetry + Tests, etc.

Primary Authoring Styles

Pick one style as your base. Each sets schema and tone for your specs.

Palmz Structured (Default)

YAML/Markdown with spec_type, intent, requirements, quality.

Ideal for: Clarity, governance, AI-readability without ceremony

EARS (Easy Approach to Requirements)

Lightweight natural-language templates (Ubiquitous, Event-Driven, State-Driven).

Ideal for: Regulated/safety-critical teams

INCOSE / IEEE

Formal requirements with ID, description, rationale, verification, priority.

Ideal for: Government, systems engineering, procurement

BDD / Gherkin

Given-When-Then scenarios.

Ideal for: Agile/QA teams, test-first development

User Story (Agile)

"As a [role], I want [goal], so that [benefit]" + acceptance criteria.

Ideal for: Product discovery, UX alignment

GitHub Spec-Kit

Modular spec.yaml for Frontend, Backend, Deployment.

Ideal for: Spec-Kit migration, GitHub integration

Kiro Spec

Markdown-first with consistent sections.

Ideal for: Kiro CLI users, Markdown preference

Add-On Domains

Multi-select domains to augment your spec. Click a badge or card to toggle.

0 domains selected

Frequently asked questions

Ready to Create Your First Spec?

Choose your format, compose your domains…

Get Started with Palmz

Join early access…