workflow-help

The repository workflow routing system uses a router to classify incoming requests and direct them to the appropriate agents or skills. It reads actual SKILL.md and agent files to determine where a request should be sent.

To use the brainstorm, plan, and execute workflow phases, you follow a structured progression: first generate ideas, then formulate a concrete plan, and finally carry out the execution. The system explains this workflow sequence and how to apply each phase effectively.

Direct and subagent-driven execution modes dictate how workflow tasks are processed within the repository system. The system clarifies the distinction between these modes and provides guidance on when to use each execution pattern based on your specific task requirements.

Yes, you can list available skills, agents, hooks, and their purposes within the workflow system. The interactive guide reads the actual configuration files to describe what each specific component does and how they contribute to the overall repository operations.

You should use a workflow guide when you need to understand how the system works or what commands are available, rather than for actually executing workflows. For active execution, a dedicated workflow orchestrator is required to process the tasks.