c-08-ar-coordination-context-resolver

Resolve Agents Remember coordination context for a target repository.

27|4|Updated Mar 21, 2026

Search Tags:#worktree #topology #resolve #coordination-context #agents-remember #memory-root

Ready to run

npx skills add https://github.com/Foxfire1st/agents-remember --skill c-08-ar-coordination-context-resolver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: c-08-ar-coordination-context-resolver
Source: https://github.com/Foxfire1st/agents-remember/tree/main/.cursor/skills/c-08-ar-coordination-context-resolver
Command: npx skills add https://github.com/Foxfire1st/agents-remember --skill c-08-ar-coordination-context-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve the active Agents Remember context for a target repository, including topology, coordination root, memory root, settings, storage, pathRules, worktree contract facts, ledger path, and branch-gated cross-repo allowances.

Core Features & Use Cases

Detects topology and resolves memory roots (internal vs external), coordination root, onboarding root, settings, task/worktree namespaces, and ledger paths to produce a single, usable coordination context.
Satisfies downstream dependency needs for c-02-memory-quality-control, c-03-repo-bootstrap, c-04-retrieval-strategy-router, c-05-create-or-update-onboarding-files, and c-09-git-worktree-manager.
Works with optional inputs (workspace_root, onboarding_root, code_repository_root, contract_path, task_name, worktree_name) to produce the full context for the repository.

Quick Start

Provide the repository name and optional inputs to resolve and return the complete Agents Remember coordination context for that repository.

Frequently Asked Questions about c-08-ar-coordination-context-resolver

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

FAQPage Schema

How do I resolve the Agents Remember coordination context for a target repository?▼

To resolve the Agents Remember coordination context, provide the code_repository_name along with optional inputs like workspace_root and task_name to detect topology, resolve memory roots, and return a single usable context.

What coordination context paths are needed for downstream memory and worktree workflows?▼

Downstream workflows require resolved paths for code_repository_root, onboarding_root, task_root, memory, ledger paths, and branch-gated cross-repo allowances to function correctly across the repository topology.

How do I set up memory roots and worktree namespaces for multi-repo agent coordination?▼

Setting up memory roots and worktree namespaces requires providing the repository name and optional overrides such as coordination_root and worktree_name, which the resolver uses to detect topology and generate namespaces.

Can I use custom overrides for workspace and onboarding roots when resolving repository topology?▼

Yes, you can supply optional overrides including workspace_root, onboarding_root, code_repository_root, and contract_path to customize how the topology and coordination context are resolved for the target repository.

Why does my cross-repo workflow fail to locate the correct ledger and memory paths?▼

Cross-repo workflows fail when the coordination context is unresolved, meaning the system cannot locate the correct memory roots, ledger paths, or branch-gated allowances without the target repository name and proper overrides.

What inputs are required to generate a worktree contract for task-specific agent memory?▼

Generating a worktree contract requires the code_repository_name, while optional inputs like task_name, worktree_name, and contract_path allow you to define task-specific namespaces and resolve the exact memory and ledger paths.