Adopt existing repositories
Use this when several existing repositories cooperate but have no shared Docflow workspace. An ordinary parent folder of repositories fits this path too.
Open in your agent: Start at the selected parent folder for read-only inventory; switch to the chosen workspace home before setup.
Before you start
Have the permitted repository paths and their owners ready. Install Docflow. Preserve each member’s Git history, instructions, identifiers, branches, queues and completion rule.
Choose to show your host's invocation form.
Prompt
In your agent
Use workspace-setup to propose a separate workspace home at <home path> for <shared purpose>, owned by <owner>. First read <member paths> and their native instructions without changing them. Inventory real identities, aliases, paths, roles, revisions and claim sources. Show a file-by-file preservation plan and wait for approval before writing. Do not initialise the surrounding container or clone members. After approval, register the actual checkouts, validate at current UTC and list missing evidence.
How to invoke this skill
Claude Code: /workspace-setup (or /docflow:workspace-setup when exposed). pi / omp: /skill:workspace-setup. Codex: $workspace-setup or find it in /skills. OpenCode, Grok, Cursor and Copilot: select the discovered workspace-setup skill. Add the task text above. These are agent inputs, not terminal commands.
Expected result
A proposed home and registry linking the independent repositories. Docflow members keep their decision catalogues and queues; issue-led or other members keep their existing method. After approval, only the selected home changes.
Check it
- Confirm each path resolves from the execution host, and instruction files really exist. Sibling or absolute paths work; an ignored
repos/directory is optional. - Keep unavailable members registered with diagnostics. A remote URL is not proof of a local checkout; remote-only entries are references, not future writable deliveries.
- Inspect Git state and the diff: no member history or native queue was moved into the home.
- Run
workspace-statusfor a read-only overview. Useworkspace-scopeonly for genuinely shared outcomes, linked to native tasks. Imported past runs need native evidence and cannot authorise future work.
If your folder already has .docflow_workspace/, resume that existing home before proposing another identity.