session-spawn

Create per-session git worktrees, briefs, and agent spawns.

3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/willietran/autoboard --skill session-spawn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-spawn
Source: https://github.com/willietran/autoboard/tree/main/skills/session-spawn
Command: npx skills add https://github.com/willietran/autoboard --skill session-spawn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the setup of per-session worktrees, briefs, and agent spawns for a given feature layer.

Core Features & Use Cases

  • Create per-session git worktrees for each session in a layer.
  • Generate session briefs and spawn dedicated agents, enabling parallel, isolated progress.
  • Support resume by reusing existing worktrees and preserving session state across layers.

Quick Start

Invoke the session-spawn skill to generate worktrees for each session, create their briefs, and spawn the corresponding agents for the current layer.

Frequently Asked Questions about session-spawn

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

FAQPage Schema
How do I automate git worktree creation for parallel agent sessions?

Automate per-session git worktree creation by spawning dedicated agents and generating individual briefs for each session in a feature layer, ensuring parallel and isolated progress across your workflow.

What is the best way to orchestrate multi-session workflows across layers?

Orchestrate multi-session workflows by coordinating environment symlinks, permissions resolution, and progress directories using manifest-driven configuration to ensure deterministic, parallel sessions across layers.

Can I resume a multi-session workflow after stopping it?

Resume multi-session workflows by reusing existing git worktrees and preserving session state across layers, allowing dedicated agents to continue progress without losing prior configuration or briefs.

How do I generate session briefs for isolated feature development?

Generate session briefs by invoking the session-spawn process, which creates per-session worktrees and spawns corresponding dedicated agents to enable isolated, parallel feature development.

Does this session orchestration approach work with manifest-driven configuration?

Manifest-driven configuration coordinates environment symlinks, permissions resolution, and progress directories to ensure deterministic, parallel sessions across layers without manual environment setup.

Why do I need per-session worktrees for parallel agent spawns?

Per-session worktrees provide isolated git branches for each dedicated agent, preventing file conflicts and enabling deterministic, parallel progress across multiple sessions within the same feature layer.