Remove the anti-MEMORY.md clause from a project that already ran vanilla bd init, on the paths that actually reach Claude Code — the CLAUDE.md BEADS INTEGRATION block and bd's runtime bd prime output. Idempotent. Invoke as /ticket-flow:bd-detox (default: strip the clause, append the Coexistence Policy to CLAUDE.md…
Render a read-only KANBAN.md snapshot of the beads tracker — invoke when the user asks for a board file or a written overview; never part of the workflow. --stdout previews, --check reports drift against bd state.
Scan the current repository for tech-stack, conventions, test setup, and anti-patterns. Writes .claude/rules/project-conventions.md, which Claude Code loads into every session, so spec generation and implementation work from the project's own conventions. Run once per project, re-run when stack changes.
Internal phase 3 of ticket-flow, normally invoked by ticket-flow:flow — verify (tests, review, proven vs. residual ACs), optional deploy, merge to main behind the merge guard, ticket → Testing or Done, worktree cleanup. Invoke directly only to finish an already-implemented ticket whose flow run ended early.
Orchestrator for Ticket-Flow — default is --local (all phases in this session with user checkpoints). --parallel works multiple ready tickets at once via worktree-isolated subagents in this session; --serial (one subagent at a time, merge+deploy+cleanup per ticket) and --loop (re-query the ready queue after every…
Internal phase 2 of ticket-flow, normally invoked by ticket-flow:flow — execute the plan for the claimed ticket inside its worktree: incremental commits, typecheck/test after each major step. Invoke directly only to continue implementing a ticket that is already picked up.
Scaffold a ticket-flow project — one-time setup; trigger on "setz ticket-flow auf", "richte das Projekt für ticket-flow ein", "set up ticket-flow here". Runs bd init with tf's agents template (keeps Claude Code's own memory system), scaffolds spec dirs and worktree settings, migrates an existing KANBAN.md into beads.…
Use when a prompt contains a new bug/feature/change not yet tracked, or when an item's status changes — capture and maintain it in the project's beads tracker (Inbox→Backlog with Definition of Ready, priorities, the pipe-separated note format).
Internal phase 1 of ticket-flow, normally invoked by ticket-flow:flow — validate Definition of Ready, create (or adopt) the ticket's isolated worktree, set the branch lock, claim the item atomically → In Progress. Invoke directly only for recovery, or when the user explicitly wants just the claim+worktree step. Args…
Everything that makes this repository more public than it is — and the inspection that must run first. Report the publication state (local, private, public), run the offline preflight over the whole history, perform the guarded transition to public, or create the remote repo in the first place (first-time gh repo…
Push the local main branch to origin — invoke when the user asks in plain words to push ("push das", "lad das hoch", "push to origin"). finish/flow deliberately leave commits local; this runs from the controller session (never a dispatched subagent) so auth prompts and errors stay visible.
Draft a spec document for a tracked ticket before implementation — the entry point when the user describes a need in prose: "ich brauche …", "mach die spec", "schreib eine Spec für X", "wir sollten X bauen", "draft a spec". Captures the WHAT plus acceptance criteria and proposes open decisions with recommendations.…
Diagnose where this ticket-flow project stands and recommend the next action — trigger on "wo steht das Projekt", "wie ist der Stand", "was ist offen", "what's the state here", after a compaction, or when picking a project up cold. Inspects scaffolding, in-flight worktrees, stale branch locks, beads counts and…