fec-backend-requirements-handoff

Installation
SKILL.md

Handover of front-end and back-end requirements

Purpose

Organize the data, actions, status, and questions required for front-end pages and interactions into discussion-ready requirements for the back-end.

Procedure

  1. Clarify the functional context
  • Describe what the page, process, or component is, what type of user it is intended for, and the success status of the user completing the task.
    • If there are existing designs, routes, user stories, or permission roles, use them as sources of truth first.
  1. Describe front-end display requirements

    • List information to be displayed by screen or component, relationships between information, sorting/filtering/pagination requirements and visibility rules.
    • Use business language to describe "what needs to be displayed" and do not specify endpoints, field names, DTOs, database tables or response nested structures in advance.
  2. Describe user actions and results

    • List the actions the user can perform, expected results, success feedback, failure feedback and whether optimistic updates are needed.
    • Mark behaviors that affect the UI such as idempotence, undo, confirm, dangerous operations, batch operations, or long task progress.
Installs
5
GitHub Stars
23
First Seen
Jun 24, 2026