system-docs-agent

Generate and update .codex/system_docs entries for agents and skills.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/pelchers/MockTrialGame --skill system-docs-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-docs-agent
Source: https://github.com/pelchers/MockTrialGame/tree/main/.claude/skills/system-docs-agent
Command: npx skills add https://github.com/pelchers/MockTrialGame --skill system-docs-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps system-level documentation aligned with evolving agents and skills by automatically generating and updating entries in the .codex/system_docs/ directory.

Core Features & Use Cases

  • Automated documentation creation: generates system_docs entries after new agents or skills are created.
  • Centralized mapping: maintains a reference mapping of systems, components, and integration points.
  • Sync and maintenance: updates existing documentation when architectures or relationships change.

Quick Start

Create or update system documentation entries for the newly created agents or skills.

Frequently Asked Questions about system-docs-agent

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

FAQPage Schema
How do I automate system documentation updates when new agents or skills are added?

Automated system documentation updates occur by scanning the project structure and generating entries in the .codex/system_docs directory. This ensures centralized mapping of agents, skills, and integration points remains consistent with actual project changes.

When do I need to update centralized system docs for agents and skills?

Centralized system docs require updates whenever new agents or skills are created, existing ones are renamed, or components are deprecated. This maintains an accurate reference mapping of purpose, architecture, and integration points across the project.

Can I sync existing READMEs and system_docs files automatically after architecture changes?

Yes, system documentation can sync automatically. The process updates existing .codex/system_docs files and related READMEs to ensure the master index stays consistent with the actual project structure after architectural relationships change.

What is the best way to maintain a centralized mapping of agents and integration points?

The best way to maintain centralized mapping is using automated documentation generation that updates .codex/system_docs entries. This preserves a consistent reference mapping of systems, components, and integration points as the project evolves.

Does automated system documentation work without external dependencies or components?

Yes, automated system documentation generation operates without external dependencies or components. It directly updates .codex/system_docs files and related READMEs based on the current project structure and architectural changes.