Doc EARS (Formal Requirements)

Trust Score 92/100

Convert BRD/PRD features into precise, testable EARS (WHEN-THE-SHALL-WITHIN) requirements ready for BDD and downstream engineering.

triggers:create earsformal requirementswhen-the-shall-withinevidence for bddtranslate prd to requirements

GitHub SKILL.md

What it does

Formalises product requirements into EARS (Easy Approach to Requirements Syntax) documents: atomic, testable WHEN-THE-SHALL-WITHIN statements with traceability to BRD and PRD and measurable quality attributes. Produces a five-section EARS document (Document Control, Purpose & Context, Requirements, Quality Attributes, Traceability) and glossary backmatter so requirements are ready for BDD and engineering.

When to use it

Use this skill when you have completed BRD and PRD artifacts and need to translate features into precise, measurable, and traceable requirements suitable for BDD, ADRs, and implementation planning. Ideal during the SDD refinement phase and before writing tests or implementation tickets.

What's included

Scripts: none declared in the repo snapshot, this is a documentation/authoring skill.
References: links to templates and governance (EARS-TEMPLATE.yaml, layer README, ID naming standards, authoring style).
Instructions: detailed authoring guidance, required structure, five EARS patterns, element ID rules, quantifiable language and validation checklist.

Compatible agents

{}</description>

Audit Summary

Documentation-only skill for creating EARS (Easy Approach to Requirements Syntax) formal requirements as part of the aidoc-flow-framework. No scripts to execute. SKILL.md is thorough and well-structured with clear prerequisites, validation checklists, quality gates, and related resources. Niche use case limited to teams adopting the specific SDD framework.

Watch Out

Requires the broader aidoc-flow-framework ecosystem (templates, governance docs) to be useful
CLAUDE_PLUGIN_ROOT env var needed for template paths

Notes

Pure documentation skill with no executable code. Part of a multi-layer requirements engineering framework (BRD → PRD → EARS → BDD). Well-organized but tightly coupled to its parent framework.

Information

Repository: aidoc-flow-framework
Stars: 15

Trust Score

Overall92

Security100

Code Quality82

Architecture88

Usefulness55

More from aidoc-flow-framework

Document Change Autopilot (CHG Autopilot)

Automate change-management (CHG) records end-to-end: detect changes, classify level, draft CHG, run audits/fixes, and prepare gate approval workflows.

Related Skills

Create & Configure Agents

Helpers and templates to scaffold agent directories, generate agent.yaml, and author SOUL.md and RULES files for new agents.

SkillPack Creator

Convert a finished task or workflow into a reusable SkillPack with local skills, prompts, scripts, and an optional zip package.

RLM Workflow

Orchestrates an RLM-inspired repository workflow with phase gates, lockable artifacts, and automated bootstrap for run folders — enforces TDD, traceability, and

Specify — Specification Creator

Create structured product or feature specifications from a short prompt; manages PRD/SDD/PLAN phases, directory scaffolding, and decision tracking.

VCSDD Git Integration

Conventional commit and tagging conventions plus atomic staging rules for committing VCSDD pipeline artifacts to git.

SDD Onboard

Interactive onboarding that guides a user through a full SDD (spec-driven development) cycle on their real codebase, producing proposal, specs, design, tasks, a

Aerospace Systems Engineer

Provide senior-level systems engineering guidance for aerospace programs: requirements management, MBSE, integration planning, and verification & validation bes

Review Design

Analyze technical designs for requirements coverage, flow correctness, and architectural feasibility to surface implementation risks.

Back to Skills