shu-ha-ri

Diagnose Shu-Ha-Ri mastery stages through behavioral questioning and stage criteria.

6|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kouko/monkey-skills --skill shu-ha-ri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shu-ha-ri
Source: https://github.com/kouko/monkey-skills/tree/main/philosophers-toolkit/skills/shu-ha-ri
Command: npx skills add https://github.com/kouko/monkey-skills --skill shu-ha-ri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps users and teams who are uncertain about their true level of practical mastery in a specific skill domain by diagnosing behavior patterns rather than relying on self-labels, and provides stage‑appropriate coaching to avoid stagnation or premature leaps.

Core Features & Use Cases

  • Behavioral diagnosis: Uses structured, domain-specific questions to infer whether a practitioner is in Shu, Ha, or Ri based on observable practices (rule-following, problem-solving approach, teaching style, handling exceptions).
  • Stage-specific guidance: Generates concrete, actionable coaching for each stage (practice drills for Shu, principled experiments for Ha, partnership-style prompts for Ri) and transition signals to indicate readiness to advance.
  • Use case: A developer unsure about their TDD practice can be guided through targeted questions, diagnosed as Shu/Ha/Ri for TDD independently of their general programming experience, and given a concrete practice plan.

Quick Start

Ask the agent to diagnose your Shu-Ha-Ri stage for a specific skill (for example: "Diagnose my Shu-Ha-Ri stage in TDD by asking about how I write, run, and refactor tests").

Frequently Asked Questions about shu-ha-ri

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

FAQPage Schema
How do I assess my skill mastery stage to know if I am ready to advance?

Behavioral questioning assesses your skill mastery stage by inferring your level from observable practices like rule-following, problem-solving approach, and handling exceptions, rather than relying on self-labels. This diagnostic approach prevents premature advancement.

What is the difference between Shu, Ha, and Ri in skill acquisition?

In skill acquisition, Shu, Ha, and Ri represent stages of mastery where Shu involves strict rule-following, Ha focuses on principled problem-solving and experiments, and Ri indicates intuitive mastery and teaching. Stage-specific coaching guides progression through these phases.

How do I get stage-specific coaching for my team's TDD practice?

To get stage-specific coaching for your team's TDD practice, a diagnostic tool asks targeted questions about how you write, run, and refactor tests. It then generates actionable coaching like practice drills for Shu or partnership-style prompts for Ri.

Can I diagnose skill progression for onboarding developers in specific technical domains?

Yes, you can diagnose skill progression for onboarding developers across technical, design, and methodological domains. The diagnosis requires per-domain scope confirmation, ensuring a developer's TDD stage is evaluated independently of their general programming experience.

How do I avoid stagnation or premature leaps when learning a new methodology?

You avoid stagnation or premature leaps when learning a new methodology by applying stage-specific guidance and transition signals. This approach ensures you receive concrete practice drills before advancing to principled experiments and intuitive mastery.

What are the limitations of using behavioral diagnosis for skill assessment?

A limitation of behavioral diagnosis for skill assessment is the need for strict safeguards against premature advancement. It requires sequential diagnostic questions and per-domain scope confirmation to ensure accurate stage evaluation across different technical and methodological contexts.