vcx-history-digest

Digest VCX prompt logs into dated history.md sections with affected files.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/sangmokang/valueconnectx --skill vcx-history-digest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcx-history-digest
Source: https://github.com/sangmokang/valueconnectx/tree/main/.claude/skills/vcx-history-digest
Command: npx skills add https://github.com/sangmokang/valueconnectx --skill vcx-history-digest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ValueConnect X raw prompt logs are digested into a concise history narrative stored in history.md, enabling traceable requirements changes across VCX products.

Core Features & Use Cases

  • Digest raw prompt logs into a readable history digest for sprint reviews and product updates.
  • Maintain a single source of truth for requirements changes across VCX components like invitations, CoffeeChat, AI Brief, directories, positions, community, and Galaxy 360.
  • Automatically append new digests to history.md with per-date sections and clear attribution.

Quick Start

Run the digest process to update history.md with the latest raw prompts.

Frequently Asked Questions about vcx-history-digest

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

FAQPage Schema
How do I convert raw prompt logs into a readable history digest?

To convert raw prompt logs into a history digest, this Skill processes your prompt logs to filter change requests and improvements, then generates a concise narrative record organized by dated sections in a history.md file.

What is the best way to track requirements changes across VCX product components?

Tracking requirements changes across VCX products is done by reading raw prompt logs and appending a summarized narrative of affected files to a central history.md file, maintaining a single source of truth for updates.

How do I generate a narrative record from raw prompt logs for sprint reviews?

Generating a narrative record for sprint reviews involves digesting raw prompt logs from .omc/state/user-prompts.raw.jsonl, filtering for specific change requests, and outputting a structured history.md file with clear attribution.

Can I maintain a single source of truth for VCX product updates using prompt logs?

Yes, you can maintain a single source of truth by processing VCX product prompt logs, such as those for CoffeeChat and AI Brief, into a concise history.md digest that automatically appends new changes with per-date sections.

Does this digest process work with raw JSONL prompt logs?

Yes, the digest process works directly with raw JSONL prompt logs, specifically reading from .omc/state/user-prompts.raw.jsonl to filter change requests and update your history.md file with a summary of affected files.

What limitations exist when digesting raw prompt logs into a history.md file?

A limitation when digesting raw prompt logs is that the process specifically filters for change requests and improvements within VCX product prompts, meaning unrelated prompt data in the JSONL logs will not be included in the history.md digest.