[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JY3B4KEN2ECBC0ZKP3H1N":3,"skill-same:01M71JY3B4KEN2ECBC0ZKP3H1N":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M71JY3B4KEN2ECBC0ZKP3H1N","project-docs",null,"Use when starting a new project, onboarding to an existing product, or auditing an existing folder structure against the standard. Scaffolds the 16-document set, folder structure, project memory and doc-sync config.","coco-research\u002Fcoco","coco-research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68911604?v=4","01M71JRE9C4NM4NSZM4JD0BJTB","Coco Research","01M71JREA0ZMR0PMH3CKA99SN1",631,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fproject-docs\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"project docs","project","docs","document","new","when","standard","project memory","Existing","pm","structure","folder structure","use","new project","doc","SET","product","config","sync","memory","2026-11-10 10:12:30",false,"---\nname: project-docs\ndescription: \"Use when starting a new project, onboarding to an existing product, or auditing an existing folder structure against the standard. Scaffolds the 16-document set, folder structure, project memory and doc-sync config.\"\ndomain: pm\n---\n\n# Project Docs — Standard Document Ecosystem\n\n## Purpose\n\nEvery project needs the same core set of interconnected documents. This skill scaffolds a complete documentation ecosystem from day one so that:\n\n- Nothing gets lost between meetings, decisions, and deliverables\n- Every document has a clear owner, purpose, and update trigger\n- The doc-sync watcher can automatically detect when documents go stale\n- New team members can onboard by reading the folder structure alone\n\n## When to Use\n\n- `\u002Fproject-docs init` — Scaffold a new project from scratch\n- `\u002Fproject-docs init --type consulting` — Use consulting template (meetings-heavy)\n- `\u002Fproject-docs init --type product` — Use product template (PRD-heavy)\n- `\u002Fproject-docs init --type implementation` — Use implementation template (vendor + config)\n- `\u002Fproject-docs audit` — Check an existing project against the standard and report gaps\n\n## The Standard Document Set\n\nEvery 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.\n\n### Category 1: Source of Truth (Root Documents)\n\nThese are authoritative — all other documents derive from them.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 1 | **PRD \u002F Requirements** | `PRD\u002F` or `Requirements\u002F` | What we're building and why | Decisions, research findings, stakeholder feedback |\n| 2 | **Project Memory** | `CLAUDE.local.md` | AI context — architecture, decisions, recent changes | Every session (auto-maintained) |\n\n### Category 2: Source Documents (Inputs)\n\nRaw inputs that feed the root documents. These are append-only — never edited after creation.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 3 | **Meeting Notes** | `Meeting-Notes\u002FYYYY-MM-DD-Name.md` | Decisions, action items, context from calls | After every meeting |\n| 4 | **Research** | `Research\u002FTopic-Name.md` | Deep dives, competitive analysis, technical research | As needed |\n| 5 | **Source Documents** | `Source-Documents\u002F` | Contracts, emails, vendor docs, screenshots | When received |\n\n### Category 3: Derived Documents (Outputs)\n\nGenerated from root + source documents. These go stale and need syncing.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 6 | **Presentation \u002F Deck** | `Presentations\u002FName-vN.html` | Stakeholder-facing summary | PRD changes, new meetings, new decisions |\n| 7 | **PRD Presentation** | `PRD\u002FPRD-Presentation.html` | Slide version of PRD for reviews | PRD changes |\n| 8 | **Architecture Map** | `Architecture\u002F` | System diagrams, data flows, integration maps | Design decisions, technical research |\n| 9 | **ARB Review** | `ARB\u002F` | Architecture Review Board presentation (Coco Inc 11-slide format) | Architecture changes, pre-go-live |\n\nGenerate with: `\u002Farb-review` — auto-populates from PRD + architecture + project registry data.\n\n### Category 4: Operational Documents\n\nLiving documents that track ongoing state.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 10 | **Verification \u002F Audit** | `Verification\u002F` | Data verification, gap analysis, compliance checks | Before milestones |\n| 11 | **Stakeholder Directory** | `Data\u002FStakeholder-Directory.xlsx` | Contact list with roles, groups, ownership | New people mentioned in meetings |\n| 12 | **Change Log** | `Change-Log.md` | Running log of product\u002Fplatform changes (config, users, modules) | After every change |\n| 13 | **NFR Tracker** | `.nfr-status.json` | Cross-cutting readiness dashboard — tracks status of all document types | Continuous |\n\nGenerate with: `\u002Fchange-log` (init or append) and `\u002Fnfr-tracker` (audit readiness).\n\n### Category 5: Compliance & Resilience\n\nRequired for production systems. Generated on demand as go-live approaches.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 14 | **DR Plan** | `Operations\u002FDR-Plan.md` | Disaster Recovery — RTO\u002FRPO targets, failover, manual fallbacks | Pre-go-live, annually |\n| 15 | **IRP** | `Operations\u002FIRP.md` | Incident Response Plan — severity matrix, escalation, SOX implications | Pre-go-live, annually |\n| 16 | **Recovery Plan** | `Operations\u002FRecovery-Plan.md` | Step-by-step restoration runbooks per failure scenario | After DR + IRP created |\n\nGenerate with: `\u002Fdr-plan` → `\u002Firp` → `\u002Frecovery-plan` (in dependency order).\n\n### Category 6: Communications\n\nTemplates for stakeholder announcements. Generated on demand.\n\n| Document | File Pattern | Purpose | Generate With |\n|----------|-------------|---------|---------------|\n| **Stakeholder Comms** | `Comms\u002FStakeholder-Comms.html` | Pre-filled templates: go-live, status, onboarding, incident, SteerCo | `\u002Fstakeholder-comms` |\n\n## The Dependency Graph\n\n```\nMeeting Notes ──┬──→ PRD ──────────→ PRD Presentation\n                │     │\nResearch ───────┤     ├──→ Main Presentation\n                │     │\nSource Docs ────┘     ├──→ Architecture Map\n                      │\n                      ├──→ \u002Farb-review (ARB presentation)\n                      │\n                      ├──→ \u002Fdr-plan ────→ \u002Frecovery-plan\n                      │\n                      ├──→ \u002Firp ────────→ \u002Frecovery-plan\n                      │\n                      ├──→ \u002Fchange-log (append mode)\n                      │\n                      └──→ \u002Fstakeholder-comms\n\n\u002Fnfr-tracker ──────→ Reads ALL of the above, reports readiness\n\nAll changes ──────────→ CLAUDE.local.md\n                ──────→ Stakeholder Directory (if new people)\n```\n\n**Key rule:** Source documents (meetings, research) flow INTO root documents (PRD). Root documents flow INTO derived documents (presentations, architecture, ops docs). Never the reverse. The NFR tracker is read-only — it audits but never modifies.\n\n## Staged Generation\n\nNot all documents are needed on day one. The standard cadence:\n\n| When | Generate | Command |\n|------|----------|---------|\n| **Day 1** (project start) | Folder structure, CLAUDE.local.md, .sync-watch.json | `\u002Fproject-docs init` |\n| **Week 1** (after first meetings) | PRD, Meeting Notes, Research | `\u002Fprd-generator` |\n| **Ongoing** | Change Log, Meeting Notes | `\u002Fchange-log`, manual |\n| **Pre-kickoff** | ARB Review, Stakeholder Comms | `\u002Farb-review`, `\u002Fstakeholder-comms` |\n| **Pre-go-live** | DR Plan → IRP → Recovery Plan | `\u002Fdr-plan` → `\u002Firp` → `\u002Frecovery-plan` |\n| **Anytime** | Readiness check | `\u002Fnfr-tracker` |\n\n## Process\n\n### Step 1: Gather Project Context\n\nAsk the user these questions (skip any they've already answered):\n\n1. **Project name?** (used for folder name and CLAUDE.local.md header)\n2. **What type of project?**\n   - `product` — Building software (PRD-centric, Jira\u002FConfluence integration)\n   - `consulting` — Advisory\u002Fimplementation engagement (meeting-notes-centric, stakeholder-heavy)\n   - `implementation` — Deploying a vendor product (config-centric, vendor docs, phased rollout)\n   - `governance` — Risk, compliance, controls (framework-centric, regulatory docs)\n3. **One-line description?** (goes in CLAUDE.local.md overview)\n4. **Who are the key stakeholders?** (seeds the stakeholder directory)\n5. **What's the primary deliverable?** (determines which Tier 1 doc to scaffold first)\n6. **Is this a git repo?** (affects .gitignore recommendations)\n\n### Step 2: Scaffold Folder Structure\n\nCreate the folder structure for the chosen project type, per the layouts below.\n\n**All types get:**\n```\nProject-Name\u002F\n├── CLAUDE.local.md\n├── .sync-watch.json\n├── .nfr-status.json          # NFR tracker state (created by \u002Fnfr-tracker)\n├── Meeting-Notes\u002F\n├── Research\u002F\n├── Source-Documents\u002F\n├── Data\u002F\n├── Operations\u002F               # DR Plan, IRP, Recovery Plan (created by slash commands)\n├── Comms\u002F                    # Stakeholder communication templates\n└── _temp\u002F\n```\n\n**Product type adds:**\n```\n├── PRD\u002F\n│   ├── PRD-Name.html (or .md)\n│   └── PRD-Presentation.html\n├── Architecture\u002F\n└── Verification\u002F\n```\n\n**Consulting type adds:**\n```\n├── Presentations\u002F\n│   ├── Name-v1.html\n│   └── _archive\u002F\n├── PRD\u002F (optional)\n└── Verification\u002F\n```\n\n**Implementation type adds:**\n```\n├── PRD\u002F\n│   ├── PRD-Name.html\n│   └── PRD-Presentation.html\n├── Presentations\u002F\n│   ├── Name-v1.html\n│   └── _archive\u002F\n├── ARB\u002F                      # Created by \u002Farb-review\n├── Architecture\u002F\n├── Verification\u002F\n├── Change-Log.md             # Created by \u002Fchange-log\n└── Source-Documents\u002F\n    ├── Contracts\u002F\n    ├── Emails\u002F\n    └── Screenshots\u002F\n```\n\n**Governance type adds:**\n```\n├── Framework\u002F\n│   ├── Controls\u002F\n│   ├── Risks\u002F\n│   └── Policies\u002F\n├── Presentations\u002F\n├── Architecture\u002F\n└── Verification\u002F\n```\n\n### Step 3: Create CLAUDE.local.md\n\nUse the template from `templates\u002Fproject-memory.md`. Pre-fill:\n- Project name and description from Step 1\n- Folder structure section (document what was created)\n- Routing guide table (map \"I need X\" → \"Go to Y\")\n- Empty sections for: Key Decisions, Recent Changes, Open Questions, Commands\n\n### Step 4: Create .sync-watch.json\n\nGenerate based on project type and folder structure. Map:\n- `watch_dirs` → all source document directories (Meeting-Notes, Research, etc.)\n- `target_docs.tier1` → root + primary derived documents\n- `target_docs.tier2` → secondary derived documents\n\nRegister the project in `~\u002F.claude\u002Fsync-watch-projects.txt`.\n\n### Step 5: Create Starter Files\n\nFor each document type the user selected, create a minimal starter:\n- **Meeting Notes:** Create `Meeting-Notes\u002F` with a `_template.md` file\n- **PRD:** Trigger `\u002Fprd-generator` or create empty PRD scaffold\n- **Presentation:** Create empty `Presentations\u002FName-v1.html`\n- **Stakeholder Directory:** Create `Data\u002FStakeholder-Directory.xlsx` or `.md` with initial contacts\n\n### Step 6: Report\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n PROJECT DOCS ► SCAFFOLDED ✓\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nProject: [Name]\nType: [product\u002Fconsulting\u002Fimplementation\u002Fgovernance]\nDocuments: [N] types configured\nSync watcher: Registered\n\nFolder structure:\n[tree output]\n\nNext steps:\n1. Start capturing meeting notes in Meeting-Notes\u002F\n2. Begin your PRD: \u002Fprd-generator\n3. The doc-sync watcher will alert you when documents need updating\n```\n\n## Audit Mode\n\nWhen invoked with `\u002Fproject-docs audit`:\n\n1. Read `.sync-watch.json` (if exists) or scan folder structure\n2. Check against the standard document set\n3. Report:\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n PROJECT DOCS ► AUDIT\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n| Document Type | Status | Path | Last Updated |\n|---------------|--------|------|--------------|\n| PRD | ✓ | PRD\u002FProductB-PRD.html | 2026-03-17 |\n| Project Memory | ✓ | CLAUDE.local.md | 2026-03-17 |\n| Meeting Notes | ✓ | Meeting-Notes\u002F (3 files) | 2026-03-13 |\n| Research | ✓ | Research\u002F (4 files) | 2026-03-17 |\n| Presentation | ✓ | Presentations\u002Fv5.html | 2026-03-12 |\n| Architecture | ✓ | ProductB-Architecture-Map.html | 2026-03-13 |\n| Verification | ✓ | Verification\u002F (2 files) | 2026-03-12 |\n| Stakeholder Dir | ✗ MISSING | — | — |\n| Source Documents | ✓ | Source-Documents\u002F | 2026-03-12 |\n| Sync Config | ✓ | .sync-watch.json | 2026-03-17 |\n\nCoverage: 9\u002F10 (90%)\nMissing: Stakeholder Directory\n```\n\n## File Naming Conventions\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Meeting notes | `YYYY-MM-DD-Attendee-or-Topic.md` | `2026-03-17-{Stakeholder}-Kickoff.md` |\n| Research | `Topic-Name.md` (no date suffix) | `Access-Management-Research.md` |\n| PRD | `ProjectName-PRD.html` or `PRD-Name.html` | `ProductB-PRD-Control-Framework.html` |\n| Presentation | `Name-vN.html` | `AppName-v5.html` |\n| Source docs | Original filename | `20251215-TGT-POC-Writeup.docx` |\n| Architecture | `Architecture-Map.html` or descriptive | `ProductB-Architecture-Map.html` |\n\n## Integration with Other Skills\n\n### pm-core (Document Creation & Sync)\n\n| Skill | How project-docs connects |\n|-------|--------------------------|\n| `\u002Fprd-generator` | Called in Step 5 if user wants PRD scaffolded |\n| `\u002Fdoc-sync` | `.sync-watch.json` created in Step 4 enables automatic sync detection |\n| `\u002Fprd-mastery` | PRD folder structure follows prd-mastery's `prds\u002F` convention |\n| `CLAUDE.local.md` | Template from `core\u002Fmemory\u002Fproject-memory-template.md` |\n\n### pm-ops (Operational Documents — Generated On Demand)\n\n| Skill | What it generates | When to run |\n|-------|-------------------|-------------|\n| `\u002Fnfr-tracker` | Readiness dashboard across all 16 doc types | Anytime — audits what exists vs what's missing |\n| `\u002Fchange-log` | Running log of product\u002Fplatform changes | After project init, then ongoing |\n| `\u002Fstakeholder-comms` | Pre-filled communication templates (6 types) | Before kickoffs, go-lives, status cycles |\n| `\u002Farb-review` | Coco Inc ARB presentation (11 slides) | Pre-go-live or when architecture review required |\n| `\u002Fdr-plan` | Disaster Recovery plan with RTO\u002FRPO | Pre-go-live |\n| `\u002Firp` | Incident Response Plan with escalation matrix | Pre-go-live (after DR plan) |\n| `\u002Frecovery-plan` | Step-by-step restoration runbooks | Pre-go-live (after DR + IRP) |\n\n**Dependency chain:** `\u002Fdr-plan` → `\u002Firp` → `\u002Frecovery-plan` (each builds on the previous).\n**Meta-command:** `\u002Fnfr-tracker` checks which of the above exist and reports gaps.\n\n## Critical Rules\n\n1. **Don't over-scaffold.** Only create directories the user confirmed they need. Empty folders are noise.\n2. **Don't create placeholder content.** An empty `PRD.html` with boilerplate headers is worse than no file. Either use `\u002Fprd-generator` to make a real one, or leave it for later.\n3. **Date everything.** CLAUDE.local.md entries use `[YYYY-MM-DD]` format. Meeting notes use date-first filenames.\n4. **Archive, don't delete.** When presentations get major updates, move old version to `_archive\u002F` before creating new one.\n5. **Source docs are immutable.** Meeting notes and research files are never edited after creation. New information goes in a new file.\n","# Project Docs — Standard Document Ecosystem\n\n## Purpose\n\nEvery project needs the same core set of interconnected documents. This skill scaffolds a complete documentation ecosystem from day one so that:\n\n- Nothing gets lost between meetings, decisions, and deliverables\n- Every document has a clear owner, purpose, and update trigger\n- The doc-sync watcher can automatically detect when documents go stale\n- New team members can onboard by reading the folder structure alone\n\n## When to Use\n\n- `\u002Fproject-docs init` — Scaffold a new project from scratch\n- `\u002Fproject-docs init --type consulting` — Use consulting template (meetings-heavy)\n- `\u002Fproject-docs init --type product` — Use product template (PRD-heavy)\n- `\u002Fproject-docs init --type implementation` — Use implementation template (vendor + config)\n- `\u002Fproject-docs audit` — Check an existing project against the standard and report gaps\n\n## The Standard Document Set\n\nEvery 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.\n\n### Category 1: Source of Truth (Root Documents)\n\nThese are authoritative — all other documents derive from them.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 1 | **PRD \u002F Requirements** | `PRD\u002F` or `Requirements\u002F` | What we're building and why | Decisions, research findings, stakeholder feedback |\n| 2 | **Project Memory** | `CLAUDE.local.md` | AI context — architecture, decisions, recent changes | Every session (auto-maintained) |\n\n### Category 2: Source Documents (Inputs)\n\nRaw inputs that feed the root documents. These are append-only — never edited after creation.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 3 | **Meeting Notes** | `Meeting-Notes\u002FYYYY-MM-DD-Name.md` | Decisions, action items, context from calls | After every meeting |\n| 4 | **Research** | `Research\u002FTopic-Name.md` | Deep dives, competitive analysis, technical research | As needed |\n| 5 | **Source Documents** | `Source-Documents\u002F` | Contracts, emails, vendor docs, screenshots | When received |\n\n### Category 3: Derived Documents (Outputs)\n\nGenerated from root + source documents. These go stale and need syncing.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 6 | **Presentation \u002F Deck** | `Presentations\u002FName-vN.html` | Stakeholder-facing summary | PRD changes, new meetings, new decisions |\n| 7 | **PRD Presentation** | `PRD\u002FPRD-Presentation.html` | Slide version of PRD for reviews | PRD changes |\n| 8 | **Architecture Map** | `Architecture\u002F` | System diagrams, data flows, integration maps | Design decisions, technical research |\n| 9 | **ARB Review** | `ARB\u002F` | Architecture Review Board presentation (Coco Inc 11-slide format) | Architecture changes, pre-go-live |\n\nGenerate with: `\u002Farb-review` — auto-populates from PRD + architecture + project registry data.\n\n### Category 4: Operational Documents\n\nLiving documents that track ongoing state.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 10 | **Verification \u002F Audit** | `Verification\u002F` | Data verification, gap analysis, compliance checks | Before milestones |\n| 11 | **Stakeholder Directory** | `Data\u002FStakeholder-Directory.xlsx` | Contact list with roles, groups, ownership | New people mentioned in meetings |\n| 12 | **Change Log** | `Change-Log.md` | Running log of product\u002Fplatform changes (config, users, modules) | After every change |\n| 13 | **NFR Tracker** | `.nfr-status.json` | Cross-cutting readiness dashboard — tracks status of all document types | Continuous |\n\nGenerate with: `\u002Fchange-log` (init or append) and `\u002Fnfr-tracker` (audit readiness).\n\n### Category 5: Compliance & Resilience\n\nRequired for production systems. Generated on demand as go-live approaches.\n\n| # | Document | File Pattern | Purpose | Update Trigger |\n|---|----------|-------------|---------|----------------|\n| 14 | **DR Plan** | `Operations\u002FDR-Plan.md` | Disaster Recovery — RTO\u002FRPO targets, failover, manual fallbacks | Pre-go-live, annually |\n| 15 | **IRP** | `Operations\u002FIRP.md` | Incident Response Plan — severity matrix, escalation, SOX implications | Pre-go-live, annually |\n| 16 | **Recovery Plan** | `Operations\u002FRecovery-Plan.md` | Step-by-step restoration runbooks per failure scenario | After DR + IRP created |\n\nGenerate with: `\u002Fdr-plan` → `\u002Firp` → `\u002Frecovery-plan` (in dependency order).\n\n### Category 6: Communications\n\nTemplates for stakeholder announcements. Generated on demand.\n\n| Document | File Pattern | Purpose | Generate With |\n|----------|-------------|---------|---------------|\n| **Stakeholder Comms** | `Comms\u002FStakeholder-Comms.html` | Pre-filled templates: go-live, status, onboarding, incident, SteerCo | `\u002Fstakeholder-comms` |\n\n## The Dependency Graph\n\n```\nMeeting Notes ──┬──→ PRD ──────────→ PRD Presentation\n                │     │\nResearch ───────┤     ├──→ Main Presentation\n                │     │\nSource Docs ────┘     ├──→ Architecture Map\n                      │\n                      ├──→ \u002Farb-review (ARB presentation)\n                      │\n                      ├──→ \u002Fdr-plan ────→ \u002Frecovery-plan\n                      │\n                      ├──→ \u002Firp ────────→ \u002Frecovery-plan\n                      │\n                      ├──→ \u002Fchange-log (append mode)\n                      │\n                      └──→ \u002Fstakeholder-comms\n\n\u002Fnfr-tracker ──────→ Reads ALL of the above, reports readiness\n\nAll changes ──────────→ CLAUDE.local.md\n                ──────→ Stakeholder Directory (if new people)\n```\n\n**Key rule:** Source documents (meetings, research) flow INTO root documents (PRD). Root documents flow INTO derived documents (presentations, architecture, ops docs). Never the reverse. The NFR tracker is read-only — it audits but never modifies.\n\n## Staged Generation\n\nNot all documents are needed on day one. The standard cadence:\n\n| When | Generate | Command |\n|------|----------|---------|\n| **Day 1** (project start) | Folder structure, CLAUDE.local.md, .sync-watch.json | `\u002Fproject-docs init` |\n| **Week 1** (after first meetings) | PRD, Meeting Notes, Research | `\u002Fprd-generator` |\n| **Ongoing** | Change Log, Meeting Notes | `\u002Fchange-log`, manual |\n| **Pre-kickoff** | ARB Review, Stakeholder Comms | `\u002Farb-review`, `\u002Fstakeholder-comms` |\n| **Pre-go-live** | DR Plan → IRP → Recovery Plan | `\u002Fdr-plan` → `\u002Firp` → `\u002Frecovery-plan` |\n| **Anytime** | Readiness check | `\u002Fnfr-tracker` |\n\n## Process\n\n### Step 1: Gather Project Context\n\nAsk the user these questions (skip any they've already answered):\n\n1. **Project name?** (used for folder name and CLAUDE.local.md header)\n2. **What type of project?**\n   - `product` — Building software (PRD-centric, Jira\u002FConfluence integration)\n   - `consulting` — Advisory\u002Fimplementation engagement (meeting-notes-centric, stakeholder-heavy)\n   - `implementation` — Deploying a vendor product (config-centric, vendor docs, phased rollout)\n   - `governance` — Risk, compliance, controls (framework-centric, regulatory docs)\n3. **One-line description?** (goes in CLAUDE.local.md overview)\n4. **Who are the key stakeholders?** (seeds the stakeholder directory)\n5. **What's the primary deliverable?** (determines which Tier 1 doc to scaffold first)\n6. **Is this a git repo?** (affects .gitignore recommendations)\n\n### Step 2: Scaffold Folder Structure\n\nCreate the folder structure for the chosen project type, per the layouts below.\n\n**All types get:**\n```\nProject-Name\u002F\n├── CLAUDE.local.md\n├── .sync-watch.json\n├── .nfr-status.json          # NFR tracker state (created by \u002Fnfr-tracker)\n├── Meeting-Notes\u002F\n├── Research\u002F\n├── Source-Documents\u002F\n├── Data\u002F\n├── Operations\u002F               # DR Plan, IRP, Recovery Plan (created by slash commands)\n├── Comms\u002F                    # Stakeholder communication templates\n└── _temp\u002F\n```\n\n**Product type adds:**\n```\n├── PRD\u002F\n│   ├── PRD-Name.html (or .md)\n│   └── PRD-Presentation.html\n├── Architecture\u002F\n└── Verification\u002F\n```\n\n**Consulting type adds:**\n```\n├── Presentations\u002F\n│   ├── Name-v1.html\n│   └── _archive\u002F\n├── PRD\u002F (optional)\n└── Verification\u002F\n```\n\n**Implementation type adds:**\n```\n├── PRD\u002F\n│   ├── PRD-Name.html\n│   └── PRD-Presentation.html\n├── Presentations\u002F\n│   ├── Name-v1.html\n│   └── _archive\u002F\n├── ARB\u002F                      # Created by \u002Farb-review\n├── Architecture\u002F\n├── Verification\u002F\n├── Change-Log.md             # Created by \u002Fchange-log\n└── Source-Documents\u002F\n    ├── Contracts\u002F\n    ├── Emails\u002F\n    └── Screenshots\u002F\n```\n\n**Governance type adds:**\n```\n├── Framework\u002F\n│   ├── Controls\u002F\n│   ├── Risks\u002F\n│   └── Policies\u002F\n├── Presentations\u002F\n├── Architecture\u002F\n└── Verification\u002F\n```\n\n### Step 3: Create CLAUDE.local.md\n\nUse the template from `templates\u002Fproject-memory.md`. Pre-fill:\n- Project name and description from Step 1\n- Folder structure section (document what was created)\n- Routing guide table (map \"I need X\" → \"Go to Y\")\n- Empty sections for: Key Decisions, Recent Changes, Open Questions, Commands\n\n### Step 4: Create .sync-watch.json\n\nGenerate based on project type and folder structure. Map:\n- `watch_dirs` → all source document directories (Meeting-Notes, Research, etc.)\n- `target_docs.tier1` → root + primary derived documents\n- `target_docs.tier2` → secondary derived documents\n\nRegister the project in `~\u002F.claude\u002Fsync-watch-projects.txt`.\n\n### Step 5: Create Starter Files\n\nFor each document type the user selected, create a minimal starter:\n- **Meeting Notes:** Create `Meeting-Notes\u002F` with a `_template.md` file\n- **PRD:** Trigger `\u002Fprd-generator` or create empty PRD scaffold\n- **Presentation:** Create empty `Presentations\u002FName-v1.html`\n- **Stakeholder Directory:** Create `Data\u002FStakeholder-Directory.xlsx` or `.md` with initial contacts\n\n### Step 6: Report\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n PROJECT DOCS ► SCAFFOLDED ✓\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nProject: [Name]\nType: [product\u002Fconsulting\u002Fimplementation\u002Fgovernance]\nDocuments: [N] types configured\nSync watcher: Registered\n\nFolder structure:\n[tree output]\n\nNext steps:\n1. Start capturing meeting notes in Meeting-Notes\u002F\n2. Begin your PRD: \u002Fprd-generator\n3. The doc-sync watcher will alert you when documents need updating\n```\n\n## Audit Mode\n\nWhen invoked with `\u002Fproject-docs audit`:\n\n1. Read `.sync-watch.json` (if exists) or scan folder structure\n2. Check against the standard document set\n3. Report:\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n PROJECT DOCS ► AUDIT\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n| Document Type | Status | Path | Last Updated |\n|---------------|--------|------|--------------|\n| PRD | ✓ | PRD\u002FProductB-PRD.html | 2026-03-17 |\n| Project Memory | ✓ | CLAUDE.local.md | 2026-03-17 |\n| Meeting Notes | ✓ | Meeting-Notes\u002F (3 files) | 2026-03-13 |\n| Research | ✓ | Research\u002F (4 files) | 2026-03-17 |\n| Presentation | ✓ | Presentations\u002Fv5.html | 2026-03-12 |\n| Architecture | ✓ | ProductB-Architecture-Map.html | 2026-03-13 |\n| Verification | ✓ | Verification\u002F (2 files) | 2026-03-12 |\n| Stakeholder Dir | ✗ MISSING | — | — |\n| Source Documents | ✓ | Source-Documents\u002F | 2026-03-12 |\n| Sync Config | ✓ | .sync-watch.json | 2026-03-17 |\n\nCoverage: 9\u002F10 (90%)\nMissing: Stakeholder Directory\n```\n\n## File Naming Conventions\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Meeting notes | `YYYY-MM-DD-Attendee-or-Topic.md` | `2026-03-17-{Stakeholder}-Kickoff.md` |\n| Research | `Topic-Name.md` (no date suffix) | `Access-Management-Research.md` |\n| PRD | `ProjectName-PRD.html` or `PRD-Name.html` | `ProductB-PRD-Control-Framework.html` |\n| Presentation | `Name-vN.html` | `AppName-v5.html` |\n| Source docs | Original filename | `20251215-TGT-POC-Writeup.docx` |\n| Architecture | `Architecture-Map.html` or descriptive | `ProductB-Architecture-Map.html` |\n\n## Integration with Other Skills\n\n### pm-core (Document Creation & Sync)\n\n| Skill | How project-docs connects |\n|-------|--------------------------|\n| `\u002Fprd-generator` | Called in Step 5 if user wants PRD scaffolded |\n| `\u002Fdoc-sync` | `.sync-watch.json` created in Step 4 enables automatic sync detection |\n| `\u002Fprd-mastery` | PRD folder structure follows prd-mastery's `prds\u002F` convention |\n| `CLAUDE.local.md` | Template from `core\u002Fmemory\u002Fproject-memory-template.md` |\n\n### pm-ops (Operational Documents — Generated On Demand)\n\n| Skill | What it generates | When to run |\n|-------|-------------------|-------------|\n| `\u002Fnfr-tracker` | Readiness dashboard across all 16 doc types | Anytime — audits what exists vs what's missing |\n| `\u002Fchange-log` | Running log of product\u002Fplatform changes | After project init, then ongoing |\n| `\u002Fstakeholder-comms` | Pre-filled communication templates (6 types) | Before kickoffs, go-lives, status cycles |\n| `\u002Farb-review` | Coco Inc ARB presentation (11 slides) | Pre-go-live or when architecture review required |\n| `\u002Fdr-plan` | Disaster Recovery plan with RTO\u002FRPO | Pre-go-live |\n| `\u002Firp` | Incident Response Plan with escalation matrix | Pre-go-live (after DR plan) |\n| `\u002Frecovery-plan` | Step-by-step restoration runbooks | Pre-go-live (after DR + IRP) |\n\n**Dependency chain:** `\u002Fdr-plan` → `\u002Firp` → `\u002Frecovery-plan` (each builds on the previous).\n**Meta-command:** `\u002Fnfr-tracker` checks which of the above exist and reports gaps.\n\n## Critical Rules\n\n1. **Don't over-scaffold.** Only create directories the user confirmed they need. Empty folders are noise.\n2. **Don't create placeholder content.** An empty `PRD.html` with boilerplate headers is worse than no file. Either use `\u002Fprd-generator` to make a real one, or leave it for later.\n3. **Date everything.** CLAUDE.local.md entries use `[YYYY-MM-DD]` format. Meeting notes use date-first filenames.\n4. **Archive, don't delete.** When presentations get major updates, move old version to `_archive\u002F` before creating new one.\n5. **Source docs are immutable.** Meeting notes and research files are never edited after creation. New information goes in a new file.\n",{"name":5,"domain":33,"description":7},"main","cd89f013b617f7eea982a9bbc60e992974fda2aa","skills\u002Fproject-docs",15,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco","https:\u002F\u002Fcocoresearch.org\u002Fcoco\u002F","https:\u002F\u002Fgithub.com\u002Fcoco-research","https:\u002F\u002Fcocoresearch.org","Local-first, open-source tools for people who work with AI agents: governed memory, agents that check their own work, and data that stays on your machine.","2026-11-11 12:18:13",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add coco-research\u002Fcoco --skill project-docs",{"tool":65,"command":66},"bunx","bunx skills add coco-research\u002Fcoco --skill project-docs",{"tool":68,"command":69},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill project-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fproject-docs\u002FSKILL.md",true,[73,79,83],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"templates\u002Fmeeting-note-template.md","REFERENCE","参考文档",852,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fproject-docs\u002Ftemplates\u002Fmeeting-note-template.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"templates\u002Fproject-memory.md",1522,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fproject-docs\u002Ftemplates\u002Fproject-memory.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"templates\u002Fsync-watch-configs.md",4344,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fproject-docs\u002Ftemplates\u002Fsync-watch-configs.md",[88,113,123,141,175,194],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":95,"publishedAt":44},"01M71KEJXF9KMT0BWCMRSRFA4M","trading-super-intelligence","Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Ftrading\u002FSKILL.md",[94],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"super","trading super intelligence","intelligence","trading","validator","personas","local","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":44},"01M71KEFWS3CMAP7DF1P0FWTDE","strategy-super-intelligence","Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fstrategy\u002FSKILL.md",[119],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,96,122,98,100,101,102,103,104,105,106,107,108,109,110,111,112],"strategy","strategy super intelligence",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":135,"publishedAt":44},"01M71KED56ZEPK2QE84QSQPMT0","risk-compliance-super-intelligence","Risk & Compliance (GRC) Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Frisk-compliance\u002FSKILL.md",[129,130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[136,96,137,138,139,98,100,101,102,103,140,104,105,106,107,108,109,110,111,112],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":160,"publishedAt":44},"01M71KE9A2FWSC74VA96W1EZSN","product-design-super-intelligence","Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery\u002Fresearch, growth\u002Fmetrics, design foundations\u002Fusability, design leadership\u002Fcraft, UX\u002Fcontent, design systems, and a…","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fproduct-design\u002FSKILL.md",[147,150,153,154,157],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":155,"categoryName":156,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":158,"categoryName":159,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000032","设计师",[161,40,98,162,96,163,164,165,166,167,168,105,106,169,170,110,171,172,173,174],"design","product design","product design super intelligence","foundations","product-design","decision","design systems","usability","leadership","ux","brain","craft","metrics","trust",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":183,"publishedAt":44},"01M71KE6H9FPSD9TECYFBPXZ8Y","legal-ip-super-intelligence","Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Flegal-ip\u002FSKILL.md",[181,182],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},[184,96,185,98,186,187,174,188,101,189,190,191,121,105,106,192,138,193,110,171],"ip","legal ip super intelligence","legal","sep","tech","litigation","ai governance","open","open-source","governance",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":44},"01M71KE36QRY610V6YVB9JWRND","healthcare-life-sciences-super-intelligence","Your healthcare and life sciences brain trust. 25 named personas across 7 cells covering drug discovery, medtech, biotech strategy, health policy, genomics, clinical trials, and healthcare economics.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fhealthcare-life-sciences\u002FSKILL.md",[200],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[202,96,203,204,98,187,174,205,206,101,207,208,121,105,106,209,210,211,212,110],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]