teammode

Coordinate multi-thread Codex team sessions with shared state and scoped members.

5|Updated May 17, 2026
One-click install
npx skills add https://github.com/islee23520/lfg --skill teammode-islee23520
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teammode
Source: https://github.com/islee23520/lfg/tree/main/skills/teammode
Command: npx skills add https://github.com/islee23520/lfg --skill teammode-islee23520

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you coordinate multi-thread Codex work when a task benefits from parallel investigation, clear ownership, and durable shared state instead of a single isolated agent.

Core Features & Use Cases

  • Team Setup and Membership: Create a named team, add members with concrete ownership slices, and keep scopes non-overlapping.
  • Thread Coordination: Bind real Codex threads to team members so the leader can track active work, progress, and hand-offs.
  • Persistent Team State: Generate team.json and an auto-built guide.md, support worktree isolation, and archive or delete teams safely.
  • Use Case: Use it for a repository audit where one member reviews scripts, another reviews documentation, and the leader synthesizes the findings.

Quick Start

Use the teammode skill to create a named Codex team with at least two members, assign each member a concrete slice of work, and generate the team state and guide in the shared workspace.

Frequently Asked Questions about teammode

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

FAQPage Schema
How do I coordinate parallel Codex threads for cross-file changes?▼

Coordinate parallel Codex threads by creating a named team with at least two members, assigning non-overlapping scopes, and binding threads to generate shared team.json state for tracking active work and hand-offs.

Can I use git worktrees to isolate parallel code investigation across team members?▼

Yes, durable Codex team sessions support worktree isolation to separate parallel code investigation scopes. This ensures each member works within a distinct worktree while maintaining safe atomic persistence with symlink guards.

What is the best way to manage state across multiple Codex team members?▼

Manage shared state across Codex team members by generating a team.json file and an auto-built guide.md. This durable state management approach tracks thread binding, member status, and safe archiving or deletion workflows.

Does parallel Codex teamwork require strict member scope separation?▼

Yes, strict member scope separation is required for parallel Codex teamwork. Each member must have a concrete, non-overlapping ownership slice to prevent conflicts during cross-file changes and parallel code investigation.

How do I safely archive or delete a Codex team session?▼

Safely archive or delete a Codex team session using workflows that apply safe atomic persistence with symlink guards. The durable state management process removes the team.json and guide.md while protecting the shared workspace.