Create a shared workspace
Use this when work spans several repositories and there is no canonical workspace yet. The home is its own Git repository; project repositories remain independent members.
Open in your agent: The deliberately chosen workspace home, not a surrounding folder of unrelated projects.
Before you start
Install Docflow. Choose a dedicated path, home identifier, owner and purpose. Ask the agent to check Node.js 22+ and matching workspace assets in its actual environment. Resume instead if a home already exists.
Choose to show your host's invocation form.
Prompt
In your agent
Use workspace-setup to create the Acme workspace at <workspace path>, with home ID acme/workspace, owned by <owner>, for coordinating API and mobile work. Use this host. Show the exact setup plan before writing, then wait for my approval. Limit changes to that home. Start with no members. If Git initialisation is needed, include it in the plan using my branch rules. Validate with the matching installed assets at the actual UTC time and show the result.
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.
Replace the example identity and placeholders with your own values.
Expected result
After approval: a README, agent instructions and .docflow_workspace/ containing the registry, conventions, overview and empty record folders. The result should name the real target path, changed files, package revision and validator outcome. Missing assets or access should be reported explicitly.
Check it
Confirm the home identity and empty member list. No members were cloned or bootstrapped. A successful empty setup creates no execution grants or completed deliveries. Inspect the diff and any Git initialisation under your chosen rules.
Check it yourself
The agent can run the validator. If you want to inspect the mechanics, use manual scratch assembly. That disposable example does not create a ready Git-backed product workspace.
Register real members
Register existing checkouts only after checking their identities, paths and actual native instructions. See the registry example. Setting up the home does not bootstrap members.