How does the skill handle edge cases?

It identifies 3-5 boundary conditions across categories like system limits, invalid input, external failures, and concurrency to ensure the software design is robust and secure.

Why does this skill emphasize RFC 2119 keywords?

Keywords like MUST, SHOULD, and MAY provide absolute clarity on the necessity of a requirement, reducing ambiguity between stakeholders and developers regarding project scope.

What is the FR-XXX format used by this skill?

It is a standardized three-digit numbering system (e.g., FR-001, FR-002) used to uniquely identify and organize functional requirements in a sequential, searchable manner.

What does 'technology-agnostic' mean in this context?

It means the requirements focus entirely on WHAT the system does and WHY, intentionally excluding specific implementation details like database types, API endpoints, or code frameworks.

Authoring Requirements

Name: Authoring Requirements
Author: deepeshBodh

bydeepeshBodh

•

Productivity & Workflow

Generates technology-agnostic functional requirements and measurable success criteria using standardized RFC 2119 syntax.

About

This skill empowers Claude Code to draft professional, high-quality technical specifications by enforcing a strict 'what-not-how' philosophy. It structures requirements using the FR-XXX format and RFC 2119 keywords (MUST, SHOULD, MAY), identifies critical edge cases across five key categories, and establishes measurable success criteria (SC-XXX) focused on user outcomes rather than technical implementation details. It is an essential tool for developers and product owners who need to maintain platform-agnostic standards while bridging the gap between business goals and technical execution.

Key Features

Automated identification of 3-5 critical edge cases per specification
Strict adherence to RFC 2119 keywords (MUST, SHOULD, MAY) for requirement clarity
Conceptual entity modeling focused on purpose and relationships over schema
Standardized FR-XXX and SC-XXX numbering systems for easy tracking
7 GitHub stars
Built-in validation script to ensure format and language compliance

Use Cases

Defining objective success criteria for stakeholder sign-off and QA testing
Translating vague business requests into actionable, measurable functional requirements
Drafting initial project specifications before starting technical development

About

Key Features

Automated identification of 3-5 critical edge cases per specification
Strict adherence to RFC 2119 keywords (MUST, SHOULD, MAY) for requirement clarity
Conceptual entity modeling focused on purpose and relationships over schema
Standardized FR-XXX and SC-XXX numbering systems for easy tracking
7 GitHub stars
Built-in validation script to ensure format and language compliance

Use Cases

Defining objective success criteria for stakeholder sign-off and QA testing
Translating vague business requests into actionable, measurable functional requirements
Drafting initial project specifications before starting technical development