Add Doc Detective + Promptless blog post

[InlinePizza]

Summary

• Adds a new product updates blog post announcing Doc Detective support in Promptless
• Content sourced from the Notion draft and adapted to the site's MDX blog format
• No images included yet — the Notion source image needs to be uploaded to S3

Test plan

• Verify the post renders correctly on the local dev server
• Confirm frontmatter fields (title, date, section) display properly
• Review content for any needed edits before publishing
• Upload and add the hero image once available

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
promptless-docs	Ready	Preview, Comment	Mar 17, 2026 9:15pm

[hawkeyexl]

I like it overall, but it doesn't address why you might need Doc Detective is you already have Promptless, how they're two sides of the same coin. Promptless reduces drift, but Doc Detective verified that any content, human-created or AI-generated, is accurate.

[hawkeyexl]

Repeated in its own section later on.

[hawkeyexl]

This whole object is completely wrong. We haven't used the "action" key since v2.

[hawkeyexl]

You're likely going to need code syntax here so the markdown doesn't render.

[hawkeyexl]

"Doc test failures show up..."

[prithvi2206]

Suggested change

	## If you have Promptless, why do you need Doc Detective?
	Promptless fixes docs drift. When a pull request renames an API field or changes
	a workflow, Promptless identifies what needs to be updated in the docs before the
	code ships. It monitors pull requests, Slack, Discord, and support channels so
	your writers do not have to manually track every engineering change. The most
	valuable thing Promptless does is catch drift before it reaches your customers.
	But products are complex and teams move fast. Not every change that affects the
	docs will be caught before it ships. Doc Detective is your safety net. It takes
	the procedures your docs describe ("click this button," "send this request,"
	"run this command") and executes them against the real product. If the result
	does not match what the docs say, the test fails. No interpretation, no
	inference. It is a test suite for your documentation, closer to Cucumber than to
	an AI agent, and cheap enough to run on every PR or on a schedule.
	When a Doc Detective test fails, that is definitive proof that your docs have
	drifted. Promptless picks up that failure, figures out what the documentation
	needs to say to match the behavior Doc Detective actually observed, and makes
	the fix. Promptless also uses your product directly to write new Doc Detective
	tests, so your test coverage grows as your docs grow.
	We see Promptless and Doc Detective as two sides of the same coin. Promptless helps prevent and remediate docs drift, and Doc Detective _deterministically validates_ that any content—whether written by Promptless or a human—is faithful to the product that it documents.
	Companies that are the most serious about guaranteeing the accuracy of their docs should use Promptless and Doc Detective together, and now Promptless users can get Doc Detective tests created automatically with every Promptless suggestion!