Back to Skills

prompt-optimizer

Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) methodology. This skill should be used when users provide loose requirements, ambiguous feature descriptions, or need to enhance prompts for AI-generated code, products, or documents. Triggers include requests to "optimize my prompt", "improve this requirement", "make this more specific", or when raw requirements lack detail and structure.

1,338stars214forksUpdated 8/16/2026

Security Assessment

Safe(98/100)
Security Score98/100

About prompt-optimizer

prompt-optimizer transforms vague, loosely worded requirements into precise, testable specifications using EARS (Easy Approach to Requirements Syntax), a structured requirements methodology originally created by Rolls-Royce. It solves the common problem of ambiguous feature requests — "build a dashboard," "make it user-friendly" — that lack triggers, conditions, and measurable outcomes and therefore produce unpredictable AI-generated code or documents.

The skill applies a four-layer enhancement process across a six-step workflow: it analyzes the original requirement for weaknesses, converts language into EARS patterns (ubiquitous, event-driven, state-driven, conditional, and unwanted-behavior), grounds requirements in relevant domain theories (GTD, BJ Fogg, Gestalt, Hick's Law, Zero Trust, and others), extracts concrete realistic examples, and generates a structured prompt using a Role/Skills/Workflows/Examples/Formats framework. Supporting reference files document the full EARS syntax, advanced multi-stakeholder and non-functional patterns, worked examples, and a catalog of domain theories.

It is aimed at product managers, engineers, prompt authors, and anyone who needs to turn natural-language intent into atomic, unambiguous, verifiable requirements. Typical uses include refining feature specs before handing them to an AI coding tool, tightening acceptance criteria, and adding measurable constraints such as time bounds or password length to otherwise vague asks. It is a pure documentation and methodology helper with no executable code beyond reference material.

FAQ

What is EARS?

Easy Approach to Requirements Syntax, a structured requirements-writing methodology created by Rolls-Royce that converts descriptive natural language into normative, testable specifications using five core sentence patterns.

When should I use this skill?

When requirements are overly broad, missing triggers, ambiguous, or lack constraints, or when you explicitly ask to optimize a prompt or refine a requirement before generating code, a product, or a document.

What are the five EARS patterns?

Ubiquitous (the system shall...), event-driven (when a trigger...), state-driven (while a state...), conditional/optional (if a condition...), and unwanted behavior (if a condition, the system shall prevent...).

Does it do more than rewrite sentences?

Yes. It also grounds requirements in established domain theories for credibility, surfaces concrete realistic examples covering success, error, and edge cases, and formats the result into a structured prompt.

Does the skill run any code?

No. It is a methodology and documentation skill consisting of a SKILL.md and reference markdown files; there are no scripts or shell commands involved.

All Files

6 files
.security-scan-passed0.2 KB
View
references/ears_syntax.md3.9 KB
View
references/advanced_techniques.md13.5 KB
View
references/examples.md12.5 KB
View
references/domain_theories.md6.1 KB
View
SKILL.md7.7 KB
View

Install prompt-optimizer

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill