Spec.

Details

Name

spec

Purpose

Create requirements from a high-level PRD.

Output

Structured requirements written to specs/requirements.md.

Method

Ask clarifying questions, then use EARS-style requirement syntax.

Markdown

---
name: spec
description: Create a requirements specification for a project based on a PRD file.
---

# Requirements Specification

## Instructions
1. Read the high level PRD file, probably in specs/prd.md
2. Ask the user questions to help refine a set of requirements for the project.
3. Use the The Easy Approach to Requirements Syntax for the requirements, write them to specs/requirements.md

The Easy Approach to Requirements Syntax (EARS) is a mechanism to gently constrain textual requirements. The EARS patterns provide structured guidance that enable authors to write high quality textual requirements.

Generic EARS syntax:

The clauses of a requirement written in EARS always appear in the same order. The basic structure of an EARS requirement is: While , when , the shall

The EARS ruleset states that a requirement must have: Zero or many preconditions; Zero or one trigger; One system name; One or many system responses.

## Examples
Please generate the requirements.
Create requirements.
Create the requirements from the PRD.
Write a requirements spec.
Create the requirements.