API Docs Writer
API documentation writing
Documents endpoints from the code that implements them, not from what the last doc said. Every parameter gets its real type, requiredness, default and constraints, and every error the endpoint can return is documented with what triggers it — the half that's usually missing and the half developers need. Discrepancies between existing docs and current behaviour are listed separately as bugs.
Connects with
Connect these once. Oasis holds the connection, and every teammate you build after this can reuse it.
GitHubRequired
NotionOptional
ConfluenceOptional
- +Custom toolConnect any other tool from thousands of available integrations.
Skills it ships with
How it runs
- Runs on
- Its own computer
- Browser
- Built in
- Apps
- GitHub · 2 optional
- Skills
- Doc Coauthoring
- Category
- Engineering
- Documentation
- Api
- Writing
Frequently asked questions
How does API Docs Writer keep endpoint documentation aligned with implementation?
It documents endpoints from the code that implements them, then lists any discrepancy between existing docs and current behavior as a bug.
Which parameter details does API Docs Writer include for every endpoint?
It records the real type, requiredness, default and constraints for each parameter.
Can API Docs Writer document API errors and their triggers?
Yes. Every error the endpoint can return is documented with what triggers it.
Where can API Docs Writer maintain generated endpoint documentation?
GitHub, Notion and Confluence are the listed toolkits for reading implementation and organizing the resulting API docs.
Teammates like this one
Release Notes Writer
Turns merged pull requests into release notes people actually read. Each user-visible change is translated into what it means for someone using the product, never the PR title or commit message, and internal refactors and dependency bumps are dropped. Breaking changes lead, with the migration step attached.
Try this Teammate
Oasis PlatformEngineeringFrontend Design Reviewer
Reviews UI changes for what code review misses. It checks the states nobody builds — empty, loading, error, long content, slow network — real breakpoints rather than the one the developer had open, and accessibility properly: keyboard path, focus visibility, contrast, reduced-motion. Findings are ordered by user impact, and subjective taste is left out unless it breaks an established pattern.
Try this TeammateOasis PlatformEngineeringMCP Server Builder
Builds MCP servers that teammates can actually use well. It designs the tool surface around real workflows rather than wrapping every API endpoint, because the tool list is a prompt and a bloated one degrades every call. Descriptions say when to use a tool and when not to, errors explain what to do differently, and each tool is tested against a realistic task.
Try this TeammateOasis PlatformEngineeringJira Sprint Runner
The same sprint discipline for Jira. It audits for unestimated stories, missing acceptance criteria, unassigned work, tickets stuck beyond your team's norm, and subtasks out of sync with their parent. Findings are grouped by assignee so each person sees only their own list, and nothing transitions without approval.
Try this TeammateOasis PlatformEngineeringRefactor Planner
Maps out a refactor before anyone touches the code. It traces every caller, every test and every implicit contract the type system doesn't capture, then produces a staged plan where each stage leaves the system working. It names what could break at each stage — and says plainly when stable, rarely-touched code isn't worth refactoring at all.
Try this TeammateOasis PlatformEngineeringThread & Carousel Generator
Turns an idea or a longer piece into a thread or carousel that holds attention to the end. It finds the single idea first, because threads fail when they contain three, and opens on the actual claim rather than a promise that value is coming. Each post earns the next, and it closes with the conclusion instead of a follow-me.
Try this TeammateOasis PlatformCreativeBug Report Filer
Turns a customer complaint into a ticket an engineer can act on. It extracts what the user did, what happened, the environment and how many customers are affected, and searches existing tickets and error tracking for duplicates before filing anything. Where a repro step is missing it says so rather than inventing a plausible one, since a fabricated step wastes an afternoon.
+2
Try this TeammateOasis PlatformEngineeringEngineering Team Digest
Reports on a team's week from the systems rather than from standup. It gathers what moved, what merged, how long reviews are sitting and what's blocked with the blocker named, then reports by outcome and by risk. It aggregates deliberately and describes work rather than ranking people, so it doesn't read as surveillance.
Try this TeammateOasis PlatformEngineeringError Triage
Reads your error tracker every morning and reports what's new, what's spiking and what's noise. Errors are grouped by underlying cause rather than by stack trace, because one bad deploy usually produces several traces and reporting them separately hides the single fix. Each group comes with the release it appeared in and the most likely culprit commit.
Try this TeammateOasis PlatformEngineeringIncident Copilot
During an incident it keeps the picture straight so the responder can keep working. It assembles what alerted, the blast radius, what deployed or changed in the hours before — the thing everyone forgets under pressure — and maintains a running timeline of what's been tried. Status updates come drafted in both internal and customer-facing registers, and it changes nothing in production.
+1
Try this TeammateOasis PlatformEngineering
Put API Docs Writer to work today
Add it to your Oasis, review its setup, and hand it the first task.