Consolidating Repositories into One agenteq Remote Source

1. What this produces

• Every source repository, refactored to agenteq's canonical structure first, if it was not already. Its own scattered per-agent files are gone. Its own canonical source directory holds its guidelines, skills, commands, and MCP servers.
• A destination repository with mcp/<name>/config.json, commands/**, skills/**, and GUIDELINES.md at its root. This is agenteq's remote source layout. It holds the shared content from every source repository, generalized so no single repository owns it. The destination is a pure content source. It never runs agenteq. It has no .ai/, no agenteq.json, and no per-agent generated files.
• Each source repository keeps only its own content. Shareable content moves to the destination. Nothing shareable stays duplicated in two places.
• Every source repository has a named remote source in its canonical source directory's remote-sources.json, pointing at the destination. The real agenteq CLI does the sync.
• A consolidation report. It lists everything that could not be safely generalized, and how the user resolved each one.

Every path in this document is a placeholder. Replace it with what the user gives you.

2. Collect the source repositories

Ask the user for the path to one source repository. Verify it is a git repository: run git rev-parse --show-toplevel inside it. Ask for another path. Repeat until the user confirms the list is complete. Do not stop after one repository unless the user confirms that is all of them.

Keep the confirmed list for the rest of this skill. A step that says "for each source repository" iterates over this list, in order.

Track each source repository's progress: agenteq-ready, classified, generalized, consolidated, wired, hooked. Use the session's task or todo tool if one is available. Otherwise, use a plain checklist. A consolidation can span many repositories across steps 5 through 13. The checklist stops one from being silently skipped.