A full agent-friendly spec that you can feed into any coding agent like Cursor, Claude code, Replit.. etc. It actually copies over to some of them automcatically.

Thanks! Go and pitch it!

Yay! Any feature requests?

Thanks! Go and pitch!

Oh! A pitch deck would be a cool idea! Should I add it?

You talk to a virtual PM, UX Designer and Engineer, they output a dev-ready spec you can paste into Cursor, Replit, Lovable, Claude Code or any agent immediately. No signup, no typing - just talk.

I'm obsessed with feeding agents the right specs. Happy to answer questions below.

Is this looking for PII in my code, or trying to understand the code logic that handles PII?

Thanks for your question. I am one of the co-founders. It is the latter. We analyze the names of functions, methods, and variables to detect likely Personally Identifiable Information (PII), Protected Health Information (PHI), Cardholder Data (CHD), and authentication tokens using well tuned patterns and language specific rules. You can see the full list here: https://github.com/hounddogai/hounddog/blob/main/data-elemen...

When we find a match, we trace that data through the codebase across different paths and transformations, including reassignment, helper functions, and nested calls. We then identify where the data ultimately ends up, such as third party SDKs (e.g. Stripe, Datadog, OpenAI, etc.), exposures in API protocols like REST, GraphQL, or gRPC, as well as functions that write to logs or local storage. Here's a list of all supported data sinks: https://github.com/hounddogai/hounddog/blob/main/data-sinks....

Most privacy frameworks, including GDPR and US Privacy Frameworks, require these flows to be documented, so we use your source code as the source of truth to keep privacy notices accurate and aligned with what the software is actually doing.