chunks-resolve-references

Update cross-chunk references in active GOAL files, flagging ambiguities for operator review.

3|1|Updated Jan 8, 2026

Search Tags:#automation #workflow #documentation #consistency #goals #references #chunk

Ready to run

npx skills add https://github.com/netguy204/vibe-engineer --skill chunks-resolve-references

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update cross-chunk references across all active chunks and notify the operator about ambiguities to maintain consistency.

Core Features & Use Cases

Scan for ACTIVE chunks and identify cross-chunk reference points across GOAL.md and related files.
Coordinate sub-agents to update references for GOALs, ensuring consistency across the docs/chunks structure.
Notify operators when ambiguities or conflicts are detected, enabling manual review and resolution.

Quick Start

Run the reference update workflow for all active chunks to refresh GOAL references.

Frequently Asked Questions about chunks-resolve-references

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

FAQPage Schema

How do I update cross-chunk references across all active goals?▼

To resolve cross-chunk references, the system parses ACTIVE chunks in docs/chunks/*, locates GOAL.md files, and runs /chunk-update-references on each path via parallel sub-agents to refresh links and maintain consistency.

What are cross-chunk references and when do I need to resolve them?▼

Cross-chunk references are links between ACTIVE documentation chunks and GOAL.md files. You need to resolve them when updates create ambiguities or conflicts that break documentation consistency across the repository.

How do I handle ambiguities in GOAL.md references during a workflow update?▼

Handling ambiguities in GOAL.md references requires scanning ACTIVE chunks to detect conflicts, then notifying the operator for manual review and resolution after parallel sub-agents complete their updates.

Can I automate reference updates for all active chunks without manual intervention?▼

You can automate reference updates for ACTIVE chunks by running the workflow, which uses parallel sub-agents to refresh GOAL.md references, though operator intervention is required when ambiguities are detected.

What limitations exist when resolving cross-chunk references in documentation?▼

Limitations include only processing chunks with ACTIVE status in docs/chunks/*, requiring manual resolution for detected ambiguities, and depending on successful sub-agent execution for updating GOAL.md files.