process-maintenance

name	process-maintenance
description	Update Harrison's shared .dot process DSL or Codex/Claude process context. Use when asked to create, revise, compact, translate, or audit Codex AGENTS guidance, Claude/Codex workflow processes, process references, or language/tooling process mappings.

Process Maintenance

Use this skill when maintaining Harrison's shared process DSL.

Source Of Truth

Edit the Graphviz DOT files under ~/.dotfiles-harrison/claude/.

Primary shared DSL files:

• ~/.dotfiles-harrison/claude/main_processes.dot
• ~/.dotfiles-harrison/claude/claude_processes.dot
• ~/.dotfiles-harrison/claude/claude_tools_management.dot
• ~/.dotfiles-harrison/claude/style_guide.dot
• ~/.dotfiles-harrison/claude/language_shell.dot
• ~/.dotfiles-harrison/claude/language_golang.dot
• ~/.dotfiles-harrison/claude/language_python.dot
• ~/.dotfiles-harrison/claude/language_javascript.dot

Codex adapter files:

• ~/.dotfiles-harrison/codex/AGENTS.md.template
• ~/.dotfiles-harrison/codex/skills/process-maintenance/SKILL.md

Generated files:

• ~/.dotfiles-harrison/compiled/dsl/*.md
• ~/.dotfiles-harrison/compiled/AGENTS.md

Do not edit generated files directly.

Workflow

1. Read the relevant .dot source before editing it.

2. If writing or restructuring DOT, follow style_guide.dot.

3. Keep shared process logic in .dot; keep Codex-only translation details in codex/AGENTS.md.template.

4. Remove duplicated hand-written Codex process text instead of maintaining it beside the DSL.

5. Regenerate outputs with:

   $ ~/.dotfiles-harrison/bin/compile-model-context
   

6. Verify generated Markdown exists under compiled/dsl/.

7. Report the .dot source changes and generated output status.

Guardrails

• Do not fork the process into separate Claude and Codex manuals.
• Do not preserve Graphviz styling details in Codex prose manually; let the compiler expose structure.
• Do not introduce rules that conflict with active Codex system/developer instructions; put runtime translations in the Codex adapter.