agent-workflows

Plugin agent-workflows from marketplace agent-profile in alleneubank/agent-profile. Commands read from the repo's manifest — today.

Skills (21)

• content

  Use when authoring or changing a work whose reader is outside the current conversation — product text (labels, messages, errors, notifications, emails, command output), documentation, announcements, a change description, or a brief, prompt, or handoff for another agent. Not for replies in the conver

• coordinator

  Use when coordinating agent lanes across hosts or workspaces, starting or resuming a campaign from a tee-up agreement, preparing unattended work, rotating coordinators, or planning a workspace's backlog by theme. Bounded attended implementation needs no coordinator.

• design

  Use when deciding how something people or agents use should look, read, or behave before it is built — a new or changed screen, flow, command output, error, tool or skill text, or a piece in another medium — or when a change reaches an established product surface that has no design record.

• dissolve-docs

  Use when the user calls a docs cleanup, a campaign has shipped, or the repo has accumulated narrative, planning, status, handoff, or loop docs whose authoritative content belongs in the standing docs (VISION, BRIEF, SPEC, README).

• done

  Use when claiming a change done, asking for acceptance or a merge, inviting someone to try a build (a bug bash, dogfood run, or visual or design review), requesting a plan or specialist review, or landing reviewed work.

• e2e

  Use when running or repairing a scripted end-to-end test suite.

• eval

  Use when evaluating whether an instruction or workflow change helps agents complete real work, using recorded sessions or bounded comparative tasks.

• fleet-watch

  Use when taking, holding, or rotating the fleet watch (the human's single contact for the fleet as a whole above each charter's coordinator), or when sweeping hosts, caps, launchers, logins, or fleet-wide rules across charters.

• git-rebase-sync

  Use when syncing a feature branch onto the latest origin base branch via git rebase.

• git-worktree-tidy

  Use when fetching and pruning a worktree-based repository, removing stale local branches, worktrees, or stashes, or bringing its important branches up to date.

• handoff

  Use when preserving enough task context for another agent or future session to continue without the current conversation

• host-tidy

  Use when a dev host is overloaded, out of memory, or hitting fork/resource limits and stale localnets, orphaned dev daemons, or leftover containers need to be found and cleared safely

• live-ops

  Use when operating on live systems - cutovers, migrations, production config changes, or incident triage

• onboard

  Use when preparing a repository for agent work, or when work stalls because a repository does not say how to run or try its product, what a change must demonstrate, which paths are high-risk, or what its brand, design system, and other customer-facing basics are.

• papercuts

  Use when you worked around friction in your own tools or environment during a task (a misleading or failing command, missing setup, a dead-end tool call, an unhelpful error, a stale doc), or when asked to triage papercuts.

• rewrite-history

  Use when the user asks to rebuild a feature branch into a clean, reviewable git history

• sitrep

  Use when the user asks for a sitrep, a status report, or "where are we" — on the current campaign or task, on what all agent sessions are doing, or as a written status update for an outside audience

• tee-up

  Use when the user asks to refine or review a draft prompt before it runs; the draft is reviewed, not executed.

• tilt

  Use when working with Tilt or a Tilt-driven dev environment - starting it, Tiltfile errors, resource status, or logs.

• writing-plans

  Use when the user requests an implementation plan, or unresolved dependencies make a brief execution plan useful before work.

• writing-skills

  Use when creating or editing a skill and you need it to be discoverable, concise, and native to the target harness

Hooks (4)

• SessionStart

  "${CODEX_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}"/hooks/instruction-fingerprint.sh SessionStart

• SubagentStart

  "${CODEX_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}"/hooks/instruction-fingerprint.sh SubagentStart

• PreToolUse

  "${CODEX_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}"/hooks/verifier-bypass-guard.sh

• PreToolUse

  "${CODEX_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}"/hooks/verifier-bypass-guard.sh

Similar plugins