# Ferrox Workspace

> You want isolated environments to work in. Create, list or remove Ferrox workspaces

- Skill: `ferroxlabs/ferrox-workspace` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ferroxlabs/ferrox-workspace`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ferroxlabs/ferrox-workspace/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: FerroxLabs (https://skillmd.com/u/ferroxlabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ferroxlabs/ferrox-workspace

---



<objective>
Manage Ferrox workspaces with a single consolidated command.

Mode routing:
- **--new**: Create an isolated workspace with repo copies and independent .planning/ → new-workspace workflow
- **--list**: List active Ferrox workspaces and their status → list-workspaces workflow
- **--remove**: Remove a Ferrox workspace and clean up worktrees → remove-workspace workflow
</objective>

<routing>

| Flag | Action | Workflow |
|------|--------|----------|
| --new | Create workspace with worktree/clone strategy | new-workspace |
| --list | Scan ~/ferrox-workspaces/, show summary table | list-workspaces |
| --remove | Confirm and remove workspace directory | remove-workspace |

</routing>

<execution_context>
@~/.claude/ferrox-core/workflows/new-workspace.md
@~/.claude/ferrox-core/workflows/list-workspaces.md
@~/.claude/ferrox-core/workflows/remove-workspace.md
@~/.claude/ferrox-core/references/ui-brand.md
</execution_context>

<context>
Arguments: $ARGUMENTS

Parse the first token of $ARGUMENTS:
- If it is `--new`: strip the flag, pass remainder (--name, --repos, --path, --strategy, --branch, --auto flags) to new-workspace workflow
- If it is `--list`: execute list-workspaces workflow (no argument needed)
- If it is `--remove`: strip the flag, pass remainder (workspace-name) to remove-workspace workflow
- Otherwise (no flag): show usage — one of --new, --list, or --remove is required
</context>

<process>
1. Parse the leading flag from $ARGUMENTS.
2. Load and execute the appropriate workflow end-to-end based on the routing table above.
3. Preserve all workflow gates from the target workflow (validation, approvals, commits, routing).
</process>