@sandrinio/vdoc 3.7.0 → 3.8.0

package/README.md

@@ -28,6 +28,24 @@ Then type: **`/vdoc-init`**
 
 ---
 
+## The Process
+
+### Step 1 — Run `/vdoc-init`
+
+vdoc explores your codebase and produces a documentation plan.
+
+### Step 2 — Review the plan
+
+Open `_DOCUMENTATION_PLAN.md` and make any changes — add, remove, rename, or reorder docs.
+
+### Step 3 — Tell the AI to proceed
+
+The AI takes your approved plan and generates documentation one by one, saving each to the `vdocs/` folder.
+
+That's it. Three steps: **init → review → approve**.
+
+---
+
 ## Supported Platforms
 
 | Platform | Install Command | `/vdoc` Command | Invocation |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sandrinio/vdoc",
-  "version": "3.7.0",
+  "version": "3.8.0",
   "description": "Documentation skills for AI coding agents",
   "type": "module",
   "bin": {

package/skills/agents/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `.agents/vdoc/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/agents/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/claude/references/create-workflow.md

@@ -10,6 +10,7 @@ Use the user's description to find the relevant source files:
 2. Otherwise, search the codebase with Glob and Grep to find files matching the user's description
 3. Read ALL relevant source files — not just the main file, but helpers, types, middleware, tests, API routes, components
 4. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
+5. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
 
 Do not skim. Understand how the feature actually works before writing.
 

package/skills/claude/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in [manifest-schema.json](./manifest-schema.json).
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/claude/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/cline/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `references/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/cline/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/continue/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `references/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/continue/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/cursor/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `references/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/cursor/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/gemini/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `.gemini/vdoc/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/gemini/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/jetbrains-ai/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `.aiassistant/vdoc/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/jetbrains-ai/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/junie/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `.junie/vdoc/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/junie/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/vscode/references/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in [manifest-schema.json](./manifest-schema.json).
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/vscode/references/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",

package/skills/windsurf/resources/init-workflow.md

@@ -42,6 +42,15 @@ After exploring, write `vdocs/_exploration_log.md` documenting what you found:
 | Prisma schema with 8 models | prisma/schema.prisma | DATA_MODEL_DOC.md |
 | ... | ... | ... |
 
+## Cross-Feature Dependencies
+After identifying all feature signals, grep for imports/references between features to map which features consume each other's data, types, or APIs. This prevents missing secondary workflows during doc generation.
+
+| Feature A | Feature B | Connection | Impact |
+|-----------|-----------|------------|--------|
+| Azure DevOps Integration | Google Sheets Export | Sheets exports work items fetched by Azure module | Azure doc must cover the export workflow |
+| Auth (NextAuth) | All API routes | Every route uses auth middleware | Auth doc must list all protected routes |
+| ... | ... | ... | ... |
+
 ## Ambiguities / Open Questions
 - Could not determine why Redis is in dependencies — no usage found. Ask user.
 - Payments folder exists but appears incomplete / WIP.
@@ -58,6 +67,12 @@ Use this format:
 ```markdown
 # Documentation Plan
 
+## Fingerprint
+- **Language(s):** e.g., TypeScript, Python
+- **Framework(s):** e.g., Next.js 14, FastAPI
+- **Archetype(s):** e.g., Full-stack Framework
+- **Scope:** e.g., ~85 files, medium
+
 ## Proposed Documents
 
 1. **PROJECT_OVERVIEW_DOC.md** — Tech stack, architecture, project structure, dev setup
@@ -85,10 +100,11 @@ Then generate docs **one at a time, sequentially**. For each approved doc:
 
 1. Read ALL relevant source files for that feature — not just the main file, but helpers, types, middleware, tests
 2. **Trace the end-to-end flow** — pick the primary user action and follow it through every layer: frontend → API route → service/lib → database → external service → response. Read each file in the chain. Don't stop at the service layer.
-3. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
-4. Confirm the file was written before moving to the next doc
+3. **Search for consumers** — grep for the feature's key types, table names, API endpoints, and module imports across the entire codebase. This catches secondary workflows (exports, scheduled jobs, webhooks, notifications, external automation) that live in different directories but depend on this feature. If you find consumers, read them and include those workflows in the doc.
+4. Write `vdocs/FEATURE_NAME_DOC.md` following the template exactly
+5. Confirm the file was written before moving to the next doc
 
-Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → write doc → next.
+Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle: read sources → trace flows → search consumers → write doc → next.
 
 **Writing rules:**
 
@@ -107,17 +123,30 @@ Do NOT attempt to generate multiple docs from memory. Each doc is a fresh cycle:
 
 Create `vdocs/_manifest.json` using the schema in `resources/manifest-schema.json`.
 
+**Transfer the Fingerprint** from the exploration log into the manifest's top-level `fingerprint` object. This preserves the project identity metadata alongside the documentation inventory.
+
 The `description` field is critical — write it rich enough that you can route any user question to the right doc by matching against descriptions. Include specific technology names, patterns, and concepts.
 
 Example:
 
 ```json
 {
-  "filepath": "AUTHENTICATION_DOC.md",
-  "title": "Authentication - OAuth2 & JWT",
-  "version": "1.0.0",
-  "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
-  "tags": ["oauth2", "jwt", "session-management", "rbac"]
+  "project": "my-project",
+  "fingerprint": {
+    "languages": ["TypeScript"],
+    "frameworks": ["Next.js 14", "Prisma", "NextAuth"],
+    "archetypes": ["Full-stack Framework"],
+    "scope": "~85 files, medium"
+  },
+  "documentation": [
+    {
+      "filepath": "AUTHENTICATION_DOC.md",
+      "title": "Authentication - OAuth2 & JWT",
+      "version": "1.0.0",
+      "description": "OAuth2 flow with Google/GitHub providers, JWT token lifecycle, session management via NextAuth.js, route protection middleware, and role-based access control.",
+      "tags": ["oauth2", "jwt", "session-management", "rbac"]
+    }
+  ]
 }
 ```
 

package/skills/windsurf/resources/manifest-schema.json

@@ -4,6 +4,12 @@
   "created_at": "<ISO-8601>",
   "last_updated": "<ISO-8601>",
   "last_commit": "<short-sha>",
+  "fingerprint": {
+    "languages": ["<language>"],
+    "frameworks": ["<framework>"],
+    "archetypes": ["<archetype>"],
+    "scope": "<file-count-and-size-category>"
+  },
   "documentation": [
     {
       "filepath": "FEATURE_NAME_DOC.md",