claude

ticket-flow

Plan-stage-reviewed ticket-to-PR workflow: capture -> research -> plan -> APPROVE -> implement -> validate -> PR. Ports the HumanLayer/CodeLayer methodology to Claude Code. Works with GitHub Issues or Linear, plus parallel research sub-agents and worktree isolation.

1 on GitHubby Alexander Opalicv0.1.0MITupdated 4 months ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin ticket-flow in alexanderop/ticket-flow. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (7)

  • implement

    Implement an approved plan from thoughts/shared/plans/ phase-by-phase, ticking checkboxes and stopping when reality diverges from the plan. Use after a plan is approved, or via /ticket-flow:implement.

  • plan

    Create a detailed, phased implementation plan with explicit success criteria, saved to thoughts/shared/plans/. Interactive and skeptical. Use after research, or via /ticket-flow:plan.

  • research

    Document the codebase as it exists today to answer a research question, by spawning parallel read-only sub-agents and synthesizing their findings into thoughts/. Use before planning any non-trivial change, or via /ticket-flow:research.

  • ship

    Run a ticket end-to-end through the plan-stage-reviewed workflow (capture -> research -> plan -> human approval -> implement -> validate -> PR). Works with GitHub Issues or Linear. Use when the user says "ship this ticket", "run the workflow on #123" or "on ENG-123", or invokes /ticket-flow:ship.

  • ticket

    Create or refine a tracker ticket (GitHub Issue or Linear) from a rough idea or a thoughts document. Enforces a clear "Problem to solve" before the ticket can be created. Use for "make an issue", "file this ticket", or /ticket-flow:ticket.

  • validate

    Validate that an implementation matches its plan — verify every success criterion, run tests/checks, and report deviations. Use after implementation, or via /ticket-flow:validate.

  • worktree

    Create an isolated git worktree for a ticket so multiple agents can work in parallel without colliding, syncing the thoughts/ context into it. Use before implementing, or via /ticket-flow:worktree.

Subagents (1)

  • codebase-researcher

    Read-only researcher that maps one focused area of the codebase and returns findings with file:line citations. Spawned in parallel by the research skill. Never edits files.

MCP servers (1)

  • linear

    runs: npx -y mcp-remote https://mcp.linear.app/sse

Hooks (1)

  • SessionStart

    mkdir -p thoughts/shared/research thoughts/shared/plans thoughts/shared/prs 2>/dev/null; true

View source on GitHub

Maintain ticket-flow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted