backend-derivation

Name: backend-derivation
Availability: InStock
Author: bennybennison

Derives backend requirements from workflow and contract artifacts.

Updated Apr 11, 2026

Search Tags:#workflow #specification #backend #contract #derivation #system-design #data-requirements

Ready to run

npx skills add https://github.com/bennybennison/agent-toolkit --skill backend-derivation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-derivation
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/backend-derivation
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill backend-derivation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It translates validated workflow and contract artifacts into concrete backend requirements, preventing premature domain modeling and ensuring backend elements are directly tied to proven screen actions and workflow steps.

Core Features & Use Cases

Input Integration: Accepts WorkflowBrief, ScreenFlowSpec, ScreenSpec, MockDataset, ApiContract, and ValidatedAppSlice.
Requirement Generation: Produces DataRequirementSpec and BackendRequirementSpec outlining source systems, fields, joins, transforms, validation rules, service boundaries, and persistence needs.
Focused Derivation: Includes only backend elements that can be traced back to a concrete workflow need, avoiding over‑engineering.

Quick Start

Request the backend-derivation skill to create DataRequirementSpec and BackendRequirementSpec for the given workflow and contract artifacts.

Frequently Asked Questions about backend-derivation

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

FAQPage Schema

How do I derive backend requirements from workflow and API contract artifacts?▼

Deriving backend requirements from workflow and API contract artifacts involves processing validated inputs like ScreenFlowSpec and MockDataset to generate DataRequirementSpec and BackendRequirementSpec documents. This ensures backend elements trace directly to concrete screen actions and workflow steps, preventing premature domain modeling and over-engineering.

What backend design specifications do I need for defining service boundaries and persistence needs?▼

Backend design specifications for service boundaries and persistence needs require a BackendRequirementSpec and DataRequirementSpec. These documents outline required fields, joins, transforms, validation rules, and raw source systems, ensuring every backend element is aligned with proven screen actions and workflow steps.

How to generate data requirement specs identifying source systems, joins, and validation rules?▼

Generating data requirement specs with source systems, joins, and validation rules requires processing validated workflow artifacts like ScreenSpec and ApiContract. The derivation produces a DataRequirementSpec that captures necessary field transforms and persistence needs tied directly to concrete workflow steps.

When do I need to translate validated workflow artifacts into backend specifications?▼

Translating validated workflow artifacts into backend specifications is needed when moving from frontend design to backend implementation. It ensures that required fields, joins, transforms, and service boundaries are directly tied to proven screen actions, avoiding over-engineering and unvalidated domain modeling.

Can I use validated app slices and mock datasets to produce backend requirement specs?▼

Validated app slices and mock datasets can be used to produce backend requirement specs by processing them alongside WorkflowBrief and ApiContract inputs. This derivation generates DataRequirementSpec and BackendRequirementSpec outputs, identifying required transforms, validation rules, and persistence needs.

Why does backend derivation avoid premature domain modeling during system design?▼

Backend derivation avoids premature domain modeling during system design by including only backend elements that can be traced back to a concrete workflow need. By processing validated contract artifacts, it ensures service boundaries and persistence needs are directly tied to proven screen actions.