requirements-writing
From the author
Guidance on writing high-quality requirements: the requirement quality characteristics and the EARS (Easy Approach to Requirements Syntax) patterns — ubiquitous, event-driven, state-driven, optional-feature, unwanted-behaviour — for unambiguous, singular, verifiable requirements, plus defect/anti-pattern review and verification & traceability. Use when authoring or reviewing requirements. Original synthesis citing EARS (Mavin et al.) and NASA public-domain guidance; not a reproduction of ISO/IEC/IEEE 29148 or the EARS paper.
Install
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill requirements-writing -a claude-code
Installs to .claude/skills/requirements-writing/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- mbse-requirementsdavepoon/buildwithclaudeAuthor, review, and repair system requirements to aerospace and defense practice. Use when writing or fixing requirements, applying EARS patterns, assigning requirement IDs, setting priority or verification method, splitting compound requirements, removing ambiguity, or reviewing a requirements document for quality. Triggers on requirement, shall statement, EARS, spec review, acceptance criteria, requirements quality, ReqIF.Planning★ 3.7K
- feature-forgeJeffallan/claude-skillsConducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.Writing★ 12.1K
- acceptance-criteriaChenxingJi-Innovate/Cheatcode_Write acceptance criteria for user stories or requirements as Gherkin scenarios (Given, When, Then) or EARS statements, including negative, boundary and permission cases, so that business users and testers agree on done before development starts. Use when a story or requirement needs acceptance criteria, when existing criteria are vague, or when preparing stories for refinement or UAT.Writing★ 81
- product-requirementscbrock84/headcountWrites down what is being built so a team can build it and know when they are done — problem and success measure before solution, scope stated by exclusion, user-visible behavior including the states everyone forgets, acceptance criteria someone can test, and the open questions named rather than buried. Use this to write a specification, review one that is causing rework, or work out why a delivered feature technically matched the request and still was not what anyone wanted.Planning★ 2.2K
- specification-writinga5c-ai/babysitterWrite feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.Writing★ 1.9K
- requirement-qualitytechygarg/latticeApply requirement quality principles when generating or validating feature specifications. Enforces feature completeness, scenario structure, AC verifiability, feature independence, and implementation slice quality. Use when writing feature specs, validating existing requirements, or when the user mentions 'validate this spec', 'check this feature', 'requirement quality', 'is this spec complete', or 'requirement-quality'. This skill governs the craft of writing individual feature specifications — not technical design (see design-blueprint), not implementation (see code-forge).Planning★ 209
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in