requirement-author

Name: requirement-author
Availability: InStock
Author: Uncodie

Transform business requests into testable requirements with acceptance criteria.

1|Updated May 8, 2025

Search Tags:#planning #specification #requirements #qa #baseline #product-management #execution-plan

Ready to run

npx skills add https://github.com/Uncodier/API --skill requirement-author

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirement-author
Source: https://github.com/Uncodier/API/tree/main/src/skills/requirement-author
Command: npx skills add https://github.com/Uncodier/API --skill requirement-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Author and maintain the requirement "brain" — a persistent, testable blueprint that downstream roles (investigation, planning, frontend, backend, QA, devops) execute against. Use when creating or refining a requirement before a plan is built, when translating a business request into a technical contract, or when updating instructions mid-cycle.

Core Features & Use Cases

Defines a standardized structure for requirements including Overview, Baseline, Goals, Non-Goals, Technical Guidelines, Contracts, Acceptance Criteria, Base Hint, Execution Plan, Definition of Ready, and Open Questions.
Ensures requirements are testable, bounded, and contract-driven so frontend, backend, and QA can align on API, DB, and UI test ids.

Quick Start

Draft a new requirement in the prescribed structure and specify its Goals, Non-Goals, Contracts, and Acceptance Criteria.

Frequently Asked Questions about requirement-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn a business request into testable requirements?▼

To turn a business request into testable requirements, structure the document with explicit Goals, Non-Goals, Contracts, Technical Guidelines, and Acceptance Criteria to align frontend, backend, and QA teams.

What is the best way to structure product specifications for QA and development teams?▼

The best way to structure product specifications is to enforce a standardized format including Overview, Baseline, Contracts, Acceptance Criteria, Execution Plan, and Definition of Ready to align execution across downstream roles.

How do I define non-goals and acceptance criteria for a product specification?▼

You define non-goals and acceptance criteria for a product specification by explicitly bounding the scope within a standardized requirement structure, ensuring the document remains testable and contract-driven for frontend, backend, and QA alignment.

Does contract-driven product management work for aligning API and UI test ids?▼

Yes, contract-driven product management works for aligning API and UI test ids by ensuring requirements are bounded and testable, allowing frontend, backend, and QA teams to align on API, DB, and UI test ids during execution.

When do I need to update a requirement baseline and execution plan?▼

You need to update a requirement baseline and execution plan when translating a business request into a technical contract, refining a requirement before a plan is built, or updating instructions mid-cycle to maintain aligned execution.