name: workmesh description: Router skill for WorkMesh. Selects CLI-first or MCP-first workflow based on available capabilities and user preference.

WorkMesh Router Skill

Use this skill to provide a Codex-first WorkMesh experience.

Mode selection

• If WorkMesh MCP tools are available, use workmesh-mcp.
• Otherwise use workmesh-cli.
• If the user explicitly requests one mode, honor it.
• When using the CLI, always pass --root <repo> unless you are already in a workflow that sets it.

Primary user intent

When the user says bootstrap workmesh (or equivalent), this skill must route into bootstrap behavior, not explain commands.

Bootstrap behavior contract

On bootstrap intent, do the following in order:

1. Detect mode (MCP or CLI).
2. Detect repository state:
   • no WorkMesh data
   • modern WorkMesh layout
   • legacy layout/deprecated structure
   • clone-based stream workflow
3. Apply state-appropriate setup:
   • initialize if missing
   • migrate if legacy
   • validate and set context if modern
   • keep work unblocked and suggest worktree consolidation if clone-based (use worktree adopt-clone + workstream create --existing)
4. Return a short summary:
   • detected state
   • actions taken
   • current context
   • next actionable tasks

Working mode contract

After bootstrap, if user asks to work on a feature, maintain WorkMesh continuously:

• create/update PRD docs
• create/maintain tasks
• keep context current
• capture durable decisions in Truth Ledger (prefer truth propose --current when a workstream is active)
• if the user is restoring after reboot / lost terminals, use workstream restore to enumerate active streams and provide deterministic resume commands per stream
• if the user wants to change defaults (worktrees/session behavior), use config show|set|unset instead of asking them to edit files by hand

Recommended workflows

Initialization (first time in a repo)

• Run bootstrap detection and setup.
• Ensure context is set (project/objective/epic/task scope) for the current work.
• If the repo is clone-based, propose consolidation via worktrees (adopt clone + workstream create --existing).

Feature setup (new feature)

• Create or select a workstream for the feature.
• Seed context (objective, tasks) and create/refresh PRD docs.
• Create tasks before coding. Use SOLID methodology when decomposing tasks.
• Define Description, Acceptance Criteria, and outcome-focused Definition of Done for every task.

Normal work procedure

• Always keep tasks in sync with the work (create/update tasks as scope changes).
• Use SOLID methodology when making design decisions or decomposing work.
• Make atomic commits per task.
• Mark tasks Done only when goals and acceptance criteria are satisfied.
• Archive completed tasks after they are Done.

Rules

• Keep task metadata complete: Description, Acceptance Criteria, Definition of Done.
• Ensure Definition of Done includes outcome-based completion criteria, not only hygiene checks.
• Move task to Done only when description goals and acceptance criteria are fully satisfied.
• Treat all status mutation paths as equivalent for Done gating (including set-field status Done and bulk variants).
• Treat Code/config committed and Docs updated if needed as hygiene checks.
• Do not commit derived artifacts like workmesh/.index/.
• Do not bypass WorkMesh storage primitives for tracking files.