Close the documentation vacuum.
vibe-doc scans your codebase, classifies your project type, finds the documentation holes, and generates professional docs from the artifacts you already have. For builders shipping fast who don't have time to write docs by hand — and can't afford to skip them.
Includes5 commands · 7 skills · 3 agents
ValidatedScanned the 626 hub.
Find the gaps. Fill them fast.
vibe-doc walks your project, cross-references what you've built against a seven-doc standard, hands back a prioritized gap report — then generates the missing docs from your own artifacts, autonomous-first.
Scan for documentation gaps.
Walks your codebase, classifies your project type, and produces a tiered gap report — Required, Recommended, Optional — with risk callouts. Saves to .vibe-doc/state.json for the downstream commands.
Generate missing docs.
Reads scan results, then fills autonomously from your READMEs, CI configs, SKILL files, schemas, and git history — asking only for the sections that genuinely need human judgment. Outputs to docs/generated/; promotion is your call.
Validate deployment readiness.
CI-safe validation that all Required-tier docs exist and haven't gone stale relative to recent commits. Exits 0 or 1 — drop it into any pipeline as a documentation gate.
Reflect and propose improvements.
Reads your session history and friction log, weights patterns across three tracks, and proposes concrete edits to SKILL files or the classifier. Nothing applies without your explicit yes.
Dual-layer by design.
vibe-doc is two systems sharing one classification engine. The conversational layer (Skills) handles adaptive, interview-driven flows with checkpoint gates so you stay in control at every fork. The deterministic layer (a CLI binary) handles reproducible, CI-safe operations with stable exit codes. Both read and write the same .vibe-doc/state.json so context carries between sessions and tools.
Generate runs autonomous-first: it reads your actual files and fills what it can without asking, interviewing you only where the code genuinely can't answer — security judgment, business intent, operational context. The rule is strict: confident content only, inline source citations, NEEDS INPUT markers where evidence doesn't exist. No fabrication.
Install.
Stable marketplace
Tagged releases via the Vibe Plugins marketplace. Also on npm: @esthernandez/vibe-doc.
/plugin marketplace add estevanhernandez-stack-ed/vibe-plugins /plugin install vibe-doc@vibe-plugins
One plugin in a family.
Vibe Plugins are a coordinated family — installed independently, composed when present.
