Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
From bmad-pro-skillsnpx claudepluginhub bmad-code-org/bmad-method --plugin bmad-method-lifecycleThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Facilitates interactive brainstorming sessions using diverse creative techniques and ideation methods. Activates when users say 'help me brainstorm' or 'help me ideate'.
Help the user understand where they are in their BMad workflow and what to do next. Answer BMad questions when asked.
When this skill completes, the user should:
{project-root}/_bmad/_config/bmad-help.csv — assembled manifest of all installed module skillsconfig.yaml and user-config.yaml files in {project-root}/_bmad/ 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"bmad-create-prdOrdering: Show optional items first, then the next required item. Make it clear which is which.
{communication_language}