agent-flow

Plugin agent-flow from marketplace josix-plugins in josix/agent-flow. Commands read from the repo's manifest — 17 days ago.

Skills (11)

• agent-behavior-constraints

  This skill should be used when handling agent model selection, tool access permissions, behavioral guardrails, MCP tool preferences, or any question about what agents can/cannot do.

• agentsview-usage

  Search prior session history to recall how similar work was handled before. Use when you want to leverage a past approach, check prior experience on a topic, answer "how was this handled before", or cross-verify current handling against precedent from earlier sessions.

• evidence-driven-work

  Ground work in what the system actually did, then tell people about it so they get it at a glance. Use when investigating why something is slow, failing, or ignoring a setting; choosing what to measure, which tool or view can show it, or what access to ask the user for; a hypothesis or estimate was

• explainer-design-system

  Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'tu

• exploration-strategy

  This skill should be used when exploring codebases, finding patterns, searching for code, gathering context, or understanding code structure before planning or implementation.

• graphify-usage

  This skill should be used when querying the graphify knowledge graph for structural codebase information, choosing between graph tools and grep, or interpreting graph query results.

• personal-kb-usage

  This skill should be used when querying the user's personal knowledge base (cross-project personal knowledge graph) for prior learnings, notes, or decisions that apply across projects.

• prompt-refinement

  This skill should be used when the user provides a vague request, asks to clarify requirements, structure a task, or refine a prompt for multi-agent orchestration.

• skill-agent-mapping

  This skill should be used when looking up which agents own or consume specific skills, understanding skill-agent relationships, or routing tasks based on skill ownership.

• task-classification

  This skill should be used when classifying tasks, routing to agents, determining complexity, or handling task routing, agent selection, verification requirements, and multi-component changes.

• verification-gates

  This skill should be used when handling verification steps, quality gates, pre-commit checks, test failures, lint errors, build verification, or mandatory validation before task completion.

Slash commands (5)

• /agent-flow:analyze

  Analyze Claude Code transcripts to surface subagent behavior and improvement opportunities

• /agent-flow:deep-dive

  Gather comprehensive codebase context using parallel exploration agents

• /agent-flow:explain

  Generate an interactive one-module explainer for a topic — Riko gathers code scope, Senku plans a 3-5 screen teaching arc, Speedwagon authors the HTML, assembler produces explain-out/index.html

• /agent-flow:orchestrate

  Orchestrate a complex multi-step task using the multi-agent system

• /agent-flow:team-orchestrate

  [DEPRECATED — use /orchestrate] Former Agent Teams variant of /orchestrate

Subagents (6)

• Alphonse

  Use this agent when running tests and validation, verifying builds, checking type compilation, or performing final quality gates.

• Lawliet

  Use this agent when reviewing code for quality, running static analysis, checking security, or verifying adherence to patterns.

• Loid

  Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.

• Riko

  Use this agent when exploring the codebase for information, finding files, understanding patterns, or gathering context.

• Senku

  Use this agent when planning implementation strategy, analyzing requirements, designing approaches, or creating task breakdowns.

• Speedwagon

  Use this agent when authoring interactive explainer modules from a curriculum plan — transforms Riko's scope + Senku's teaching arc into a module brief and an HTML fragment for the /explain course. NEVER use for exploration, planning, or general code changes.

MCP servers (2)

• graphify

  runs: ${CLAUDE_PLUGIN_ROOT}/scripts/start-graphify-mcp.sh

• agentsview

  runs: ${CLAUDE_PLUGIN_ROOT}/scripts/start-agentsview-mcp.sh

Hooks (9)

• UserPromptSubmit

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refine-prompt-gate.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/validate-changes.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/log-event.sh" preToolUse

• PostToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/log-event.sh" postToolUse

• SubagentStop

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/log-event.sh" subagentStop

• SessionEnd

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/log-event.sh" sessionEnd

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/load-project-context.sh"

• SessionStart

  bash -c 'GRAPH_PATH="${CLAUDE_PROJECT_DIR:-$(pwd)}/graphify-out/graph.json"; if [ -f "$GRAPH_PATH" ] && [ -n "${CLAUDE_ENV_FILE:-}" ]; then printf "export AGENT_FLOW_GRAPH_PATH=%q\n" "$GRAPH_PATH" >>

• Stop

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/verify-completion.sh"

Similar plugins