Implement Documentation from an Issue

Ship the feature, ship the docs

Label an issue needs-docs-update and the playbook clones your docs and product repos, analyzes the linked PR to find the customer-facing changes, and plans exactly which pages to create or update. A Tech Writer drafts the content with Mintlify components while a developer verifies it for accuracy, then it opens a PR linked back to the issue.

Implement Documentation from Issue — how the workflow runs, trigger to result

The edge cases, covered

It right-sizes every update to the actual change, respects your existing docs hierarchy, and runs a two-phase write-then-verify pass for technical accuracy.

Customer-facing changes only

Analyzes the linked product PR to surface what's genuinely new for users, filtering out internal changes that don't need documentation.

Follows your docs standards

Writes with Mintlify components and matches the existing tone, structure, and navigation so new pages fit right in.

Write-then-verify pass

A Tech Writer drafts each page and a developer reviews it for technical accuracy before the change is committed.

Right-sized updates

Assesses the real importance of each change and scopes the documentation to match, avoiding bloat and duplicate pages.

PR linked to its source

Opens a documentation PR that links back to the originating issue and the product PR, with appropriate labels applied.

Built for your docs stack

It works against Mintlify docs in .mdx format, updates navigation files, and opens the PR on your Git host with the right labels and issue links.

Running from day one

Fires automatically when an issue is labeled needs-docs-update, or run /implement-docs on any docs issue. Needs Senior Developer, Tech Writer, and Product Manager agents and a product-PR link on the issue.