tackle-epic

Tackle Epic

You are given an epic identifier and optional flags: $ARGUMENTS

Codex: if the invocation text above is not populated, use the text after the skill name. If it is unavailable, infer the epic identifier and optional flags from the current request.

Parse the arguments:

• The epic identifier is the first argument (everything before any -- flags)
• If --here is present, work on the current branch/worktree instead of creating a new one

Step 1: Find the Epic

First, locate the epic in beads:

1. If the argument looks like an ID (e.g., buddy-cli-98w), run: bd show <epic-id>
2. If it's a name/search term, run: bd list --type=epic --title="<search-term>" to find matching epics

If no epic is found, report the error and stop.

Step 2: Understand the Epic

Once you have the epic:

1. Run bd show <epic-id> to get full details
2. Run bd show <epic-id> --children to see all child tasks
3. Understand the scope and requirements from the epic description

Step 3: Set Up Working Environment

If --here flag is set: Skip worktree creation, then:

1. Record the current directory as worktree_path.
2. Resolve the active branch with branch_name="$(git branch --show-current)".
3. Stop if branch_name is empty; a detached HEAD cannot be pushed safely by this workflow.
4. Resolve base_ref from the PR base branch when one exists, otherwise from the repository's default remote branch.

Otherwise (default): Create a worktree for this epic:

1. Generate a branch name from the epic title/context (lowercase, hyphenated, max 50 chars)
   • Format: feature/<epic-id>-<short-description>
   • Example: feature/buddy-cli-98w-webhook-management
2. Record that value as branch_name, resolve a concrete worktree_path, and create it: git worktree add "<worktree_path>" -b "$branch_name"
3. Resolve base_ref from the repository's default remote branch.

For every command in the remaining steps, explicitly use worktree_path as the working directory. Do not rely on shell cd state persisting between tool calls.