context-vigilance

Standardize context-v/ directories with YAML frontmatter and four-part versioning.

4|Updated May 4, 2026
One-click install
npx skills add https://github.com/lossless-group/lossless-agent-skills --skill context-vigilance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-vigilance
Source: https://github.com/lossless-group/lossless-agent-skills/tree/main/context-vigilance
Command: npx skills add https://github.com/lossless-group/lossless-agent-skills --skill context-vigilance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the pervasive problem of lost, unstructured context across AI co-development sessions and cross-team collaboration, which leads to duplicated work, inconsistent project knowledge, and hours of wasted time re-explaining project context to new agents or collaborators.

Core Features & Use Cases

  • Standardized context-v/ structure: Enforces a consistent six-folder directory layout aligned with cognitive modes (Prep, Reflective, Journey) for organizing living specifications, implementation prompts, architecture blueprints, AI guardrails, research explorations, and debugging issue logs.
  • Consistent context conventions: Defines baseline YAML frontmatter rules, four-part epoch.major.minor.patch versioning, wikilink cross-reference standards, and status discipline to make all context docs loadable and discoverable for both humans and AI agents.
  • Use Case: A team building a suite of Astro sites can use this framework to keep implementation specs, architecture blueprints, and debugging journeys organized, so any agent or new team member can quickly orient to the project without rework.

Quick Start

Ask your AI agent to set up a standardized context-v/ directory structure for your current project, following the six-folder convention and baseline frontmatter rules outlined in the Skill.

Frequently Asked Questions about context-vigilance

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

FAQPage Schema
How do I maintain consistent project context across multiple AI co-development sessions?

Standardizing project context organization eliminates context loss across AI co-development sessions by enforcing a consistent context-v/ directory layout, YAML frontmatter rules, and wikilink cross-references so agents can load project history quickly.

What is the best way to structure project documentation for AI agents to read?

Structuring project documentation for AI agents requires a six-folder directory layout aligned with cognitive modes (Prep, Reflective, Journey) to organize living specifications, implementation prompts, architecture blueprints, and debugging logs into loadable context.

How does semantic versioning work for project documentation and living specifications?

Semantic versioning for project documentation applies a four-part epoch.major.minor.patch format within YAML frontmatter to track the evolution of living specifications, ensuring both humans and AI agents reference the correct context state.

Do I need to use wikilinks for cross-referencing project architecture blueprints and implementation prompts?

Wikilinks are required for cross-referencing project architecture blueprints and implementation prompts within the context-v/ directory, making context docs discoverable and loadable for both humans and AI agents navigating the project knowledge base.

Can I use this context management framework for cross-team collaboration on any software project?

Yes, this context management framework applies to any software project using a context-v/ directory for cross-team collaboration, preventing duplicated work and inconsistent project knowledge when new team members or agents join the workflow.

Why does my AI agent lose track of debugging issue logs and research explorations between sessions?

AI agents lose track of debugging issue logs and research explorations between sessions due to unstructured context, which is solved by standardizing all project context into a consistent directory structure with baseline frontmatter rules for reliable loading.