archflow-agent-api-engineer

Implements backend services and APIs strictly from a project's API contract specification.

28|4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AZidan/archflow --skill archflow-agent-api-engineer-azidan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archflow-agent-api-engineer
Source: https://github.com/AZidan/archflow/tree/main/adapters/generic/.agents/skills/archflow-agent-api-engineer
Command: npx skills add https://github.com/AZidan/archflow --skill archflow-agent-api-engineer-azidan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend implementations often drift from agreed API specifications, causing integration failures between frontend and backend teams. This Skill enforces contract-first API development, ensuring every endpoint, parameter, and response format matches the project's API contract exactly. ## Core Features & Use Cases - Contract-First Implementation: Reads the API contract from the configured path and builds only the endpoints it specifies, with exact paths, methods, parameters, and response schemas. - Stack-Agnostic Backend Development: Detects the project's language, framework, database, and ORM from project settings or repository manifests, and builds in that stack rather than imposing one. - Full Backend Coverage: Handles authentication, RBAC, database schema design, migrations, error handling, validation, and OpenAPI specification generation. - Use Case: During Phase 3 of an Archflow project, delegate a user story to this agent so it implements the backend endpoints defined in docs/api-contract.md, then hands off verified work to the qa-engineer. ## Quick Start Ask the agent to implement the backend endpoints for a specific story from the API contract in the project's declared stack.

Frequently Asked Questions about archflow-agent-api-engineer

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

FAQPage Schema
How do I implement an API that matches a contract specification exactly?

Read the API contract first from the configured api_contract_path, then implement only the endpoints it defines using exact paths, HTTP methods, parameters, and response schemas. Cross-check every endpoint against the contract before marking work complete.

What happens if the API contract is unclear or missing details?

The agent stops and asks for clarification rather than interpreting the contract creatively. It follows a zero-deviation policy, so ambiguous specifications must be resolved by the user before implementation continues.

Does this work with any backend framework or language?

Yes, the agent is stack-neutral and reads the language, framework, database, and ORM from project settings. If the stack is unset, it detects candidates from repository manifests like package.json, pyproject.toml, or go.mod and asks for confirmation.

Can the agent add extra endpoints not in the contract?

No, it implements only endpoints specified in the contract with no additions or modifications. Any deviation is treated as an integration failure risk under its zero-tolerance compliance policy.

Who marks a story as done after backend implementation?

The agent sets completed subtasks and moves the story to review status, handing it to the qa-engineer. Only the acceptance gate closes a story as done after user approval.