pmstudio-initlisted

# Project Docs — Standard Document Ecosystem ## Purpose Every project needs the same core set of interconnected documents. This skill scaffolds a complete documentation ecosystem from day one so that: - Nothing gets lost between meetings, decisions, and deliverables - Every document has a clear owner, purpose, and update trigger - The doc-sync watcher can automatically detect when documents go stale - New team members can onboard by reading the folder structure alone ## When to Use - `/project-docs init` — Scaffold a new project from scratch - `/project-docs init --type consulting` — Use consulting template (meetings-heavy) - `/project-docs init --type product` — Use product template (PRD-heavy) - `/project-docs init --type implementation` — Use implementation template (vendor + config) - `/project-docs audit` — Check an existing project against the standard and report gaps ## The Standard Document Set Every project should have these **16 document types** organized in **6 categories**. Not every project needs all 16 — the skill asks which ones apply and only scaffolds what's needed. Documents 11-16 are generated on demand via dedicated slash commands in the `pm-ops` skill category. ### Category 1: Source of Truth (Root Documents) These are authoritative — all other documents derive from them. | # | Document | File Pattern | Purpose | Update Trigger | |---|----------|-------------|---------|----------------| | 1 | **PRD / Requirements** | `PRD/` or `Requirements/` |