Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.
86
79%
Does it follow best practices?
Impact
99%
1.70xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./dist/plugins/frontend-to-backend-requirements/skills/frontend-to-backend-requirements/SKILL.mdBackend requirements document structure and workflow
Correct output path
40%
100%
Title format
0%
100%
Context section
50%
100%
Screen subsections
57%
100%
Data display described
100%
100%
Actions described
100%
100%
States covered
100%
100%
Uncertainties section
25%
100%
Questions for Backend
62%
100%
Discussion Log present
0%
100%
No endpoint specs
0%
100%
No field names
0%
100%
Context-rich data descriptions
40%
100%
Updating requirements after backend feedback
Correct output path
100%
100%
Discussion Log populated
100%
100%
Decisions recorded
100%
100%
Uncertainties resolved
100%
100%
Requirements adjusted
100%
100%
Original structure preserved
100%
100%
No implementation details added
100%
100%
Source of truth note
100%
100%
Remaining questions flagged
100%
100%
Pushback invitation present
100%
33%
Data relationships and pushback invitation
Correct output path
28%
100%
Relationship descriptions
20%
100%
No nesting assumptions
30%
100%
No field names
0%
100%
Context for data items
50%
100%
Pushback invitation phrases
0%
100%
Open questions phrasing
50%
100%
Business rules section
0%
100%
Edge case states
87%
100%
Uncertainties checklist
14%
100%
No endpoint specs
100%
100%
3027f20
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.