zigzag

name	zigzag
version	0.1.0
description	Use Zigzag-managed Zellij sessions, agent status, JSON commands, and safe project/worktree workflows.

Zigzag Agent Skill

Use this skill when you are working inside, or alongside, a Zigzag-managed Zellij session.

Detect Zigzag Context

• Check ZIGZAG_SESSION first.
• If it is missing, ask the user for the session name or pass --session <session> explicitly when the command supports it.
• Do not guess a session by deleting, rewriting, or scraping Zigzag state.

Report Agent Status

Report short status changes so Zigzag can show agent activity:

zigzag notify --agent-status working --agent <agent> "Started"
zigzag notify --agent-status blocked --agent <agent> "Needs approval"
zigzag notify --agent-status done --agent <agent> "Finished"
zigzag notify --agent-status idle --agent <agent> "Idle"

Public statuses are working, blocked, done, idle, and unknown. Use blocked when you need human permission or cannot progress. Use done when the requested work is complete and ready for review.

Read Zigzag Context

Prefer Zigzag JSON commands over parsing Zellij output:

zigzag session list --json
zigzag switch list --json
zigzag worktree list --json
zigzag notify list --json
zigzag events list --json

With --json, stdout is strict JSON. Use jq for local inspection when it is available.

Wait For State

Wait for another agent or notification with:

zigzag wait agent --session <session> --status done --timeout 300s
zigzag wait notification --session <session> --timeout 300s

Use --timeout 0 for a single check. Do not loop forever on wait.

Session Navigation

• Use zigzag switch list --json to discover managed sessions.
• Do not kill or delete sessions unless the user explicitly asks for that.
• Use Zigzag commands when Zigzag exposes the needed information; avoid manual Zellij parsing for managed state.

Safety Rules

• Do not remove a worktree without explicit user instruction.
• Do not run git reset --hard, git clean, branch deletion, or other destructive commands unless explicitly requested.
• Report blocked when a human permission is required.
• Report done when the task is complete and waiting for review.

Failure Handling

• If a Zigzag command fails, read JSON error output when present, otherwise read stderr.
• If you cannot make meaningful progress, report blocked with a short message.
• Keep retries bounded and visible.