kickoff

Launch a background Claude agent for end-to-end feature development via tmux or containers.

27|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/forecast-bio/ferray --skill kickoff-forecast-bio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kickoff
Source: https://github.com/forecast-bio/ferray/tree/main/.claude/skills/kickoff
Command: npx skills add https://github.com/forecast-bio/ferray --skill kickoff-forecast-bio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegates end-to-end feature development tasks to a background Claude agent by orchestrating worktree creation, prompt assembly, and session launch via tmux or container runtimes, simplifying repetitive feature implementation workflows.

Core Features & Use Cases

  • Launch a background Claude agent to handle feature development end-to-end.
  • Delegate worktree creation, prompt generation, and session management to the kickoff workflow.
  • Use cases include starting a feature, iterating, and tracking status across sessions.

Quick Start

Describe the feature you want to implement and trigger the kickoff workflow to spawn a background Claude agent.

Frequently Asked Questions about kickoff

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

FAQPage Schema
How do I launch a background Claude agent for feature development?

To launch a background Claude agent for feature development, trigger the kickoff workflow to automatically create a worktree, generate implementation prompts, and start a session via tmux or container runtimes.

What is the best way to automate feature implementation workflows with Claude?

Automating feature implementation workflows with Claude involves orchestrating worktree creation, prompt assembly, and session launch via tmux or container runtimes to delegate end-to-end tasks to a background agent.

How do I manage a Claude agent session lifecycle in tmux for software development?

Managing a Claude agent session lifecycle in tmux for software development is handled by the kickoff workflow, which delegates session execution, tracks status across sessions, and applies configurable runtime options.

Do I need a specific environment setup to run an automated feature development agent?

Yes, running an automated feature development agent requires a properly configured environment to handle prerequisites and safety constraints before delegating execution to the crosslink kickoff run CLI.

Can I use container runtimes to launch background agents for code generation?

Yes, background agents for code generation can be launched using container runtimes, with the kickoff workflow managing the session lifecycle, prompt assembly, and configurable verification options.

What are the limitations of delegating feature development to a background agent?

Limitations of delegating feature development to a background agent include the requirement for a properly configured environment and adherence to safety constraints, with execution contingent upon the crosslink kickoff run CLI handling prerequisites.