workflow-guide

Explains which workflow command and editor mode to use now and why.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill workflow-guide-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-guide
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/workflow-guide
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill workflow-guide-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New users of a file-based AI engineering workflow often do not know which command or editor mode fits the current task phase, and guessing leads to skipped gates or premature implementation. This Skill reads the active task state and explains the current phase, the right command, the right mode, and the next 2-3 steps. ## Core Features & Use Cases - Phase-aware guidance: Reads TASK_STATE.md and task artifacts to identify the current workflow phase before recommending anything. - Command and mode recommendation: Names the best next command (only official command names) and the fitting editor mode, plus why nearby modes are less appropriate. - Onboarding-oriented teaching: Provides a short 2-3 step sequence for users still learning the workflow, with a no-op fallback that routes to what-next when guidance would be redundant. - Use Case: A developer in their first sessions with the workflow finishes a decision record and asks what to do next; the Skill explains they are in the planning phase, recommends implementation-plan, and outlines the following two steps. ## Quick Start Ask the assistant to use the workflow-guide skill to explain which command and editor mode fit the current task state and what the next few steps should be.

Frequently Asked Questions about workflow-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know which workflow command to run next?▼

Use what-next for a fast single-command answer, or workflow-guide when you want the reasoning explained. workflow-guide reads TASK_STATE.md, identifies the current phase, and recommends the command, editor mode, and next 2-3 steps.

What is the difference between workflow-guide and what-next?▼

what-next gives one quick next-command answer with low overhead. workflow-guide is a heavier teaching helper that explains the current phase, why the command and mode fit, and a short sequence, intended for users still learning the workflow.

When should I not use workflow-guide?▼

Skip it when you only want a fast next-step answer (use what-next), when you are already fluent in the workflow phases, or when the task is stuck and needs im-stuck instead. Redundant runs return a no-op and route onward.

Does workflow-guide modify code or task files?▼

No. It updates no task repository files and does not implement code. Its output is advisory only: current phase, best command, best mode, rationale, and next steps, ending with a standard handoff block.

Can workflow-guide recommend commands that do not exist?▼

No. It reads the commands directory inventory first and may only recommend basenames of existing command files. The only exception is an explicit 'Run now: none' when the chain has honestly ended.