# Draft Punk > For AI agents: the site index is at [llms.txt](https://draftpunkdocs.io/llms.txt). Every page has a Markdown version at the same path plus `.md`. For AI agents: the site index is at . A Markdown version of this page is at . Q4 offer: every new client starts with a free Documentation Autopsy. [Claim yours](https://calendly.com/steven-draftpunkdocs/30min) **New:** Drafts now trigger on merged pull requests. Documentation CI/CD # Turn engineering activity into documentation. Automatically. Merged pull requests, issue tracker tickets (e.g. Jira), team chat requests (e.g. Slack) and support questions become reviewed drafts inside the knowledge base you already run. Built for technical writers and PMs who are tired of docs trailing the release. [Book a 30-minute demo](https://calendly.com/steven-draftpunkdocs/30min) [See how it works](#how-it-works) - No migration - Works with your platform - A technical writer approves everything AI drafts. Human approves. Nothing publishes without you. Signal → Draft → Approve → Live PR #482 · main Merged Add scoped, expiring API tokens + token.expires\_at + scopes: read | write | admin ~ settings/api/tokens.tsx User-facing change detected. Diff and linked PRD pulled in as context. Staged draft · 52s Quality 8/10 Create and scope API tokens ☐ Confirm max token lifetime with engineering ☐ Screenshot of Settings › API needs a refresh Ripple: 3 related articles flagged, 1 high impact KAN-112 · Approved Live Create and scope API tokens URL Unchanged Title Unchanged Approved by Docs lead PR author notified Yes **Listens to:** Code repositories (e.g. GitHub) Issue trackers (e.g. Jira) Team chat (e.g. Slack) Linked specs **Writes to:** Your knowledge base HTML Markdown XML How it works ## Real runs, not mockups. Recorded on the live engine. On-screen captions carry the story, so no sound needed. Shown with Zendesk Guide; the same run writes to the knowledge base you already use, or to HTML, Markdown and XML. - [Ticket to new article (1:32)](https://draftpunkdocs.io/video/ticket-to-article.mp4): a ticket lands in the issue tracker (e.g. Jira). Under a minute later, a scored draft waits for review. - [Chat request to new article (2:20)](https://draftpunkdocs.io/video/chat-to-article.mp4): support asks in team chat (e.g. Slack). A ticket opens itself, and the draft follows, open questions included. - [Update a live article, safely (2:54)](https://draftpunkdocs.io/video/update-live-article.mp4): a limit changes from 100 to 500. The live article stays untouched until a human approves, then two related pages get flagged as stale. ## Documentation CI/CD. Same discipline as your code, with a human at the gate. 01 · Signal ### Your team keeps working. A PR merges to main. A ticket moves in your issue tracker (e.g. Jira). Someone asks in team chat (e.g. Slack). Draft Punk listens to all of it and ignores what customers never see, with a logged reason for every skip. 02 · Draft ### A full draft in about a minute. Written from the diff, the ticket, and the linked spec, in your house style. Existing articles are updated as a staged copy. New ones land unpublished. 03 · Approve ### One transition. Then it's live. Move the ticket to Approved and the live article is patched in place. Same URL, same title. Until then, customers see exactly what they saw yesterday. Product ## Everything between the merge and the help center. NEW ### Code-triggered docs. Merge to main and the draft starts. The PR diff and changed files become context, so the draft describes what actually shipped. git merge feature/api-tokens → user-facing: yes → draft staged: "Create and scope API tokens" ### Developers hear back where they work. Draft Punk comments on the PR with a link to the draft. Engineers see their change documented without opening the knowledge base. draft-punk commented Draft ready for review: Create and scope API tokens. 2 open questions, 3 related articles flagged. ### Live articles stay untouched. Updates are staged as a separate unpublished copy. Approval patches the original in place. No broken links, no duplicate titles, no SEO reset. Live Serving customers Staged Waiting on you ### Ripple flags. One change, three articles quietly wrong. After every draft, Draft Punk flags the other pages it just made stale, ranked by impact. Authenticate with the API High Rate limits Low Admin roles Low ### Review the flags, not the whole article. Every draft arrives scored out of 10 with a checklist of anything unverified. Screenshots that need a human are marked. 8/10 ### Release notes and FAQs, on schedule. Release notes compiled from what actually shipped. Repeated support questions turned into self-serve answers before the sixth reply. House style enforced HTML, Markdown, XML Hebrew input Full audit trail PlatformComing Q4 2026 ## From the first merge to the report your VP reads. One engine for the whole documentation lifecycle, running inside the tools your team already uses. Docs-as-code output Writes Markdown to your docs repo and opens a pull request. Same review gate. Any linked spec Specs and PRDs linked from a ticket are read as context, in Confluence, Notion, Google Docs, or GitHub. Backlog backfill Replays the last 90 days of merges and reports the changes your docs missed before drafting. Ask the developer Open questions go to the PR author. Answers flow back into the draft and the score rises. Support-desk trigger Repeated helpdesk tickets cross a threshold and become a drafted answer. Doc lead time report Merge-to-live time, every month, on one page your VP will actually read. No teken? Ain baya. ## A retainer you can approve. Not a headcount you have to win. Hiring is frozen. The backlog isn't. Draft Punk gives the writer you already have the output of a team. ~1 min signal to first draft 0 documents migrated 100% human-approved before publish Security ## Built to pass a cyber company's security review. ### Your content stays in your platform Drafts are written straight into your knowledge base. Nothing hosted or mirrored elsewhere. ### Isolated per client Each client runs on its own deployment. No shared data, no co-mingling. ### Least-privilege access Scoped, revocable tokens. Read-only wherever reading is enough. ### No auto-publish path Every draft is unpublished until a named human approves it. There is nothing to misconfigure. ### Not used to train models Content sent for drafting is not retained for training. ### Full audit trail Every draft links to the PR or ticket that triggered it, and to whoever approved it. Managed, end to end ## You don't get a login. You get a working pipeline. Software you have to set up, tune, and babysit is just another item on the backlog. Draft Punk is built, run, and tuned for you, inside your stack, by documentation people. ### Set up for you. Triggers, outputs, and the approval flow are wired into your repos, tracker, and knowledge base during implementation. Your team configures nothing. ### Tuned to your docs. Your style guide, your terminology, your article patterns. Drafts sound like your docs from week one, not like a model's first guess. ### Watched every week. Draft quality, skipped signals, and stale pages are reviewed by a senior technical writer. When something drifts, it's fixed before you notice. ### Shaped around your stack. Odd knowledge base, custom fields, a release process nobody else has? It gets built in, not filed as a feature request. No seats to count. No admin to train. No setup sprint. Tools hand you features. Draft Punk hands you the outcome: docs that ship when your code does. Pricing ## Managed for you. Priced against a salary, not a seat. MANAGED SERVICE One-time implementation Scoped Monthly retainer Flat Set up inside your existing platform Tuned to your house style guide Code, ticket, chat, and support signals connected Onboarding for your writers and PMs [Book a 30-minute demo](https://calendly.com/steven-draftpunkdocs/30min) Q4 OFFER ### Start with a free Documentation Autopsy. One recent release, traced from merge to help center. Then 30 days running on a live workflow in your own issue tracker and knowledge base. Free for every new client this quarter. ## Questions. ### Does this replace our technical writer? No. It removes the typing and keeps the judgment with your writer. Only a human can publish. ### Do we have to migrate our docs? No. Draft Punk writes into the platform you already use. Your structure, URLs, and style guide stay exactly as they are. ### What if a PR has no customer impact? It is skipped, and the reason is logged. Refactors and internal changes never reach your review queue. ### Our platform isn't listed. Can you support it? Usually, yes. New outputs are built during implementation. Ask on the call. ### Does anything publish automatically? Never. There is no auto-publish path to switch on. ## Bring a ticket. Watch it become a doc. Thirty minutes, live, on your kind of content. No deck. [Book a 30-minute demo](https://calendly.com/steven-draftpunkdocs/30min) [info@draftpunkdocs.io](mailto:info@draftpunkdocs.io) [Contact](https://draftpunkdocs.io/contact.md) · [Privacy Policy](https://draftpunkdocs.io/privacy.md) · [Terms of Service](https://draftpunkdocs.io/terms.md)