Transform business requests into testable requirements with acceptance criteria.
npx skills add https://github.com/Uncodier/API --skill requirement-author
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
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.
Draft a new requirement in the prescribed structure and specify its Goals, Non-Goals, Contracts, and Acceptance Criteria.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
januarfontiAutomate product management workflows including PRDs, feature analysis, and roadmap planning.
xvawlPlan feature work into implementation plans with module maps and acceptance criteria.
adnanmuellerTranslate design specs and API contracts into Next.js frontend interfaces.
olivermorgan2Generates a standardized eight-section PRD draft from unstructured notes.
