ok-workspaces

Creates and tears down isolated per-job git worktrees with dedicated runtime stacks.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill ok-workspaces-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ok-workspaces
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/families/ok-workspaces/skills/ok-workspaces
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill ok-workspaces-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Parallel agent or developer work in one repository causes branch collisions, shared runtime state, and leaked artifacts. This Skill enforces workspace hygiene: one worktree per job, one isolated runtime stack per worktree, and per-run artifact tags that never outlive the run. ## Core Features & Use Cases - Workspace creation (/open): Creates a job's isolated workspace — a git worktree on its own branch per the committed naming profile, ephemeral local config carried over, and a namespaced runtime provisioned. - Safety-gated teardown (/close): Refuses to close on uncommitted work or an unmerged branch, then stops the runtime, removes the worktree, and deletes the branch. - Per-run artifact tagging: Ships a POSIX sh run-tag script that prints a fresh run-<12 hex> tag per invocation, so verification runs build every artifact under one ephemeral tag. - Use Case: An agent starting a feature job runs /open to get an isolated worktree and runtime, verifies changes under a fresh run tag, then runs /close which blocks teardown until work is committed and merged. ## Quick Start Ask the assistant to open a new isolated workspace for the current job using the /open command.

Frequently Asked Questions about ok-workspaces

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

FAQPage Schema
How do I create an isolated git worktree for a parallel job?▼

Run the /open command, which creates a worktree on its own branch following the naming rules in the committed stack profile, carries over ephemeral local config, and provisions a namespaced runtime stack for that job.

How do I safely remove a git worktree after a job finishes?▼

Run the /close command, which performs a safety-gated teardown: it refuses if there is uncommitted work or an unmerged branch, then stops the runtime, removes the worktree, and deletes the branch.

Does ok-workspaces activate automatically during conversation?▼

No. The skill's frontmatter states it is only activated by explicit slash commands (/open, /close) and is never auto-triggered by conversation content. Subagents dispatched for specific tasks are instructed to skip it.

What dependencies does the run-tag script require?▼

The run-tag script is POSIX sh with no dependency beyond a POSIX userland, so it runs in environments where node and git are absent. Each invocation prints a fresh run-<12 hex> tag for per-run artifact naming.

Where do job worktrees live and are they committed?▼

By default worktrees live under .ok-workspaces/worktrees/ inside the project root, kept untracked by a suite-owned .gitignore. A project can redirect them via the worktrees.dirPrefix setting in the committed config profile.