narrative-compact

Consolidate active chunks into a single narrative under docs/narratives.

3|1|Updated Jan 8, 2026

Search Tags:#workflow #documentation #narrative #consolidation #chunk #backreferences

Ready to run

npx skills add https://github.com/netguy204/vibe-engineer --skill narrative-compact

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: narrative-compact
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/narrative-compact
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill narrative-compact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidate multiple chunks into a narrative to reduce backreference clutter and improve traceability across the codebase and docs.

Core Features & Use Cases

Clusters related chunks into a single narrative to reduce duplication.
Preserves historical references for archaeology while simplifying navigation.
Stores the generated narrative under docs/narratives/[name]/OVERVIEW.md and updates backreferences accordingly.

Quick Start

Run ve narrative compact on a set of active chunks to create a unified narrative under docs/narratives.

Frequently Asked Questions about narrative-compact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I consolidate documentation chunks into a single narrative?▼

Consolidating chunks automatically clusters related pieces across your project to produce a single narrative. This process reduces backreference clutter and simplifies navigation while preserving historical traceability for codebase archaeology.

What is the best way to reduce backreference clutter in project documentation?▼

The best way to reduce backreference clutter is by clustering related chunks into a unified narrative. This enforces that only subsystem backreferences remain, simplifying navigation while preserving historical references for traceability across the codebase and docs.

How does narrative consolidation handle historical references and traceability?▼

Narrative consolidation preserves historical references for archaeology while simplifying navigation. By merging related chunks into a unified narrative and updating backreferences, it maintains full traceability across the codebase and docs without losing prior context.

Where are consolidated documentation narratives stored?▼

Consolidated narratives are stored under docs/narratives/[name]/OVERVIEW.md. Storing the generated output in this specific directory structure ensures the unified documentation remains organized and accessible while backreferences are updated accordingly.

Can I automatically cluster related documentation chunks across my project?▼

Yes, the system automatically clusters related chunks across your project during the narrative consolidation process. This automatic clustering groups active chunks together to produce a single narrative, reducing duplication and simplifying navigation across the codebase.