#workflow

Articles tagged with #workflow

Generate code from the spec, not the spec from the code
Agents guess field names when they never see the contract. Serve the spec over MCP, generate one verified vertical slice at a time, run scenarios against localhost, and rescan to catch drift.
Oct 2, 20266 min read
Designing an API before the first line of code
Behavior first, routes second. AI drafts the OpenAPI contract as reviewable diffs, the team settles money, idempotency, and error envelopes up front, and mocks plus scenarios define done before implementation starts.
Oct 1, 20265 min read
Publishing partner API docs shouldn't become a website project
Integration is done and the partner asks for a link. Finish descriptions locally, verify real calls, and publish versioned hosted docs and MCP from the same workspace, with no doc-tool rollout attached.
Sep 29, 20263 min read
We inherited a service with no OpenAPI. Here is how we scanned the real one.
Two hundred routes, an Express and two FastAPI services, and a Postman collection from 2023. An AST scan reconstructs the real contract, marks honest gaps instead of guessing, and stays repeatable through rescans.
Sep 28, 20265 min read
A local-first Postman alternative in 2026: what an OpenAPI-native workflow looks like
Postman made collections the source of truth and put them in the cloud. A newer workflow makes the OpenAPI spec the source, keeps files on disk where git can see them, and treats debugging, mocks, tests, and MCP as views over one document. Here is an honest comparison.
Sep 25, 20266 min read
One spec, two audiences: the human reading your docs and the agent calling your API
Inventory APIs get consumed by developers reading docs and by agents discovering tools. Separate web docs, prompt pastes, and hand-written schemas guarantee drift; one OpenAPI file produces both.
Sep 25, 20264 min read

#workflow - Powerduck Blogs