Analyzes current state and user query to answer Rihal questions or recommend the next skill(s) to use. Use when user asks for help, Rihal help, what to do next, or what to start with in Rihal.
Help the user understand where they are in their Rihal workflow and what to do next. Answer Rihal questions when asked.
When this skill completes, the user should:
{project-root}/.rihal/catalog.json — assembled manifest of all installed module skillsconfig.yaml and user-config.yaml files in {project-root}/.rihal/ and its subfolders — resolve output-location variables, provide communication_language and project_knowledgeoutputs patterns at resolved output-location paths reveal which steps are possibly completed; their content may also provide grounding context for recommendationsproject_knowledge resolves to an existing path, read it for grounding context. Never fabricate project-specific details.The catalog uses this format:
module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
Phases determine the high-level flow:
anytime — available regardless of workflow state1-analysis, 2-planning, etc.) flow in order; naming varies by moduleDependencies determine ordering within and across phases:
after — skills that should ideally complete before this onebefore — skills that should run after this oneskill-name for single-action skills, skill-name:action for multi-action skillsRequired gates:
required=true items must complete before the user can meaningfully proceed to later phasesCompletion detection:
outputs patternsDescriptions carry routing context — some contain cycle info and alternate paths (e.g., "back to DS if fixes needed"). Read them as navigation hints, not just display text.
For each recommended item, present:
[menu-code] Display name — e.g., "[CP] Create PRD"rihal-create-prdOrdering: Show optional items first, then the next required item. Make it clear which is which.
{communication_language}