ticket-flow

ticket-flow

A Claude Code plugin that ports the HumanLayer / CodeLayer methodology: a plan-stage-reviewed ticket-to-PR workflow. Works with GitHub Issues or Linear.

Review and alignment happen at the plan stage, not the PR stage.

📋 Ticket ──/research──▶ 🗺️ Map ──/plan──▶ 📝 Plan ──★ YOU APPROVE ──▶ 💻 Code ──/validate──▶ 🔀 PR
   you                  agent             agent        (one human gate)     agent          agent

Install (local dev)

claude --plugin-dir ./ticket-flow

Then run /reload-plugins after edits. Skills are namespaced under ticket-flow:.

Trackers

The workflow auto-detects which tracker to use from the ticket reference:

Reference	Tracker	Status tracked via
#123, owner/repo#123, GitHub URL	GitHub Issues	tf:* labels (one at a time)
ENG-123, Linear URL	Linear	workflow states

See references/trackers.md for the exact operations and the logical-status → label/state mapping. GitHub needs gh authenticated; Linear needs the linear MCP server (authenticate via /mcp).

Usage

/ticket-flow:ship #123           # GitHub issue — whole pipeline, stops for approval after the plan
/ticket-flow:ship ENG-123        # Linear ticket — same pipeline

Or run a single phase:

/ticket-flow:ticket    a rough idea          # capture -> GitHub issue or Linear ticket (needs a "Problem to solve")
/ticket-flow:research  how does auth work    # parallel read-only sub-agents -> thoughts/shared/research/
/ticket-flow:plan      #123                  # phased plan + success criteria -> thoughts/shared/plans/
/ticket-flow:worktree  #123                  # isolated git worktree (#123 -> issue-123), thoughts/ synced in
/ticket-flow:implement thoughts/shared/plans/foo.md
/ticket-flow:validate  thoughts/shared/plans/foo.md

What's inside (the mapping)

Plugin piece	CodeLayer equivalent
skills/*	the .claude/commands/*.md playbooks (research, plan, implement, validate, …)
skills/ship	the orchestrator that chains them and enforces the human gate
references/trackers.md	the GitHub-Issues / Linear abstraction (status mapping + commands)
agents/codebase-researcher.md	the parallel research sub-agents the research command spawns
.mcp.json (Linear)	the optional Linear MCP integration
bin/create-worktree.sh	hack/create_worktree.sh — MULTICLAUDE worktree isolation
hooks/hooks.json	scaffolds the thoughts/ durable-memory directory at session start
thoughts/shared/	research + plans persisted outside the context window

Requirements

• GitHub Issues: the gh CLI, authenticated (gh auth status). Used for issues and PRs.
• Linear (optional): the linear MCP server (authenticate via /mcp).
• git, rsync for worktrees.