document-app reverse-engineers the durable documentation an AI-built app is usually missing. It reads the code as the source of truth and produces core documents for architecture, permission-relevant flows, roles and permissions, and config and secrets, plus conditional documents for emails, cron, SEO and embedded agents when those capabilities exist.
Those documents become the baseline that later audits compare the code against. A check-only mode reads existing docs and code, prints every factual disagreement with both sides cited, and writes no file.
What You Get
- architecture.md with the stack, auth flow and trust boundaries, linking to each other document produced
- flows.md listing permission-relevant journeys, each protected step’s authorization check and the side effects it causes
- permissions.md with roles, scope derivation and a resource by operation by role matrix, noting which checks are row-level security and which are code
- variables.md mapping config and secrets to risk and rotation, plus conditional emails.md, cron.md, seo.md and automation.md where they apply
- A check-only report of disagreements, behaviors present in code but in no doc, and what was not checked
Common Use Cases
- Giving an AI-built app the written intent that a security or performance audit needs
- Refreshing docs before a release and seeing where they drifted from the code
- Handing a reviewer a map of who can do what and where the risk lives
- Checking hand-maintained docs against the code without letting an agent overwrite them
What Makes It Unique
It treats the codebase as untrusted input to describe, so instructions embedded in code are never followed. It follows the repo’s own docs location and names first and uses documentation/ only where none exist. For large scopes it gives parallel subagents one core document each. Check mode leaves the choice of which side is wrong to the owner.
Under The Hood
The skill is a single markdown file. The agent reads source files in the repository, may start parallel subagents for large scopes, and writes markdown documents into the docs folder. Check mode only reads and prints. It runs no scripts and calls no web services, and it relies on the shipping-artifacts skill for the contents of each document.