rpi-kit 2.5.1 → 2.5.2

package/.claude-plugin/marketplace.json

@@ -5,14 +5,14 @@
   },
   "metadata": {
     "description": "Research → Plan → Implement. 7-phase pipeline with 13 named agents, delta specs, party mode, and knowledge compounding.",
-    "version": "2.5.1"
+    "version": "2.5.2"
   },
   "plugins": [
     {
       "name": "rpi-kit",
       "source": "./",
       "description": "Research → Plan → Implement. 7-phase pipeline with 13 named agents, delta specs, party mode, and knowledge compounding.",
-      "version": "2.5.1",
+      "version": "2.5.2",
       "author": {
         "name": "Daniel Mendes"
       },
@@ -37,6 +37,7 @@
         "./commands/rpi/rpi.md",
         "./commands/rpi/simplify.md",
         "./commands/rpi/status.md",
+        "./commands/rpi/tutor.md",
         "./commands/rpi/update.md"
       ],
       "agents": [

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rpi-kit",
-  "version": "2.5.1",
+  "version": "2.5.2",
   "description": "Research → Plan → Implement. 7-phase pipeline with 13 named agents, delta specs, party mode, and knowledge compounding.",
   "author": {
     "name": "Daniel Mendes",

package/bin/cli.js

@@ -336,7 +336,7 @@ Usage:
   rpi-kit onboarding         Interactive walkthrough of the workflow
   rpi-kit help               Show this help
 
-Commands (18):
+Commands (19):
   /rpi:new <feature>         Describe your feature → REQUEST.md
   /rpi:fix <bug>             Quick bugfix — interview, plan, implement in one step
   /rpi:research <feature>    Parallel agent analysis → RESEARCH.md
@@ -356,6 +356,7 @@ Commands (18):
   /rpi:party                 Multi-agent debate on any topic
   /rpi:docs-gen              Generate CLAUDE.md from codebase analysis
   /rpi:evolve [--quick]      Product evolution analysis with health score
+  /rpi:tutor [topic]         Interactive coding tutor with adaptive profiling
 
 Agents (13):
   Luna (Analyst) · Atlas (Explorer) · Scout (Researcher) · Nexus (Synthesizer)

package/commands/rpi/tutor.md

@@ -0,0 +1,266 @@
+---
+name: rpi:tutor
+description: Personalized coding tutor that adapts to your experience level and uses your real project code as examples.
+argument-hint: "[topic] [--profile] [--reset]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+
+# /rpi:tutor — Coding Tutor
+
+Personalized coding tutor that builds a developer profile, adapts to your experience level, and teaches using real code from your project.
+
+---
+
+## Step 1: Load config
+
+Read `.rpi.yaml` from the project root. If it doesn't exist, use defaults silently.
+
+## Step 2: Parse arguments
+
+Parse `$ARGUMENTS` for:
+- `{topic}` — free-text topic string (e.g. "dependency injection", "error handling")
+- `--profile` — force re-interview to update developer profile
+- `--reset` — delete profile and stop
+
+**Flag precedence:** `--reset` > `--profile` > `{topic}`
+
+If `--reset` is present, ignore all other flags and arguments.
+
+## Step 3: Handle --reset
+
+If `--reset` was parsed:
+
+1. Check if `rpi/tutor-profile.yaml` exists.
+2. If it exists: delete it using Bash (`rm rpi/tutor-profile.yaml`).
+3. Output:
+   ```
+   Tutor profile deleted. Run /rpi:tutor to create a new one.
+   ```
+4. Stop.
+
+If `rpi/tutor-profile.yaml` does not exist:
+```
+No tutor profile found. Nothing to reset.
+```
+Stop.
+
+## Step 4: Check profile
+
+Check if `rpi/tutor-profile.yaml` exists.
+
+If the file exists, read and parse it. If `experience_level` or `history` fields are missing, or the file is not valid YAML, delete the file, inform the user ("Profile was corrupted. Starting fresh interview."), and proceed to Step 5.
+
+- **Exists + `--profile` flag:** proceed to Step 5 (re-interview, preserve history).
+- **Exists + no flag:** proceed to Step 6 (topic selection).
+- **Does not exist:** proceed to Step 5 (first-time interview).
+
+## Step 5: Build developer profile
+
+### Step 5a: Git analysis
+
+Run these commands to detect the developer's stack and recent focus:
+
+```bash
+# Get current user email
+git config user.email
+```
+
+```bash
+# Language distribution by file extension (last 6 months)
+git log --author="<email>" --since="6 months ago" --no-merges --pretty=format: --name-only | sed 's/.*\.//' | sort | uniq -c | sort -rn | head -15
+```
+
+```bash
+# Recent focus (last 2 weeks)
+git log --author="<email>" --since="2 weeks ago" --no-merges --pretty=format: --name-only | sort -u | head -20
+```
+
+```bash
+# Recent commit subjects (for topic suggestion later)
+git log --author="<email>" --since="1 week ago" --no-merges --pretty=format:"%s" | head -15
+```
+
+Store results as `$GIT_LANGUAGES`, `$GIT_RECENT_FILES`, `$GIT_RECENT_COMMITS`.
+
+**IMPORTANT:** Never infer proficiency from git metrics. Use git only for stack detection and recent focus areas.
+
+### Step 5b: Claude Memory read
+
+Attempt to read supplementary context from Claude Memory:
+
+```bash
+git_root=$(git rev-parse --show-toplevel)
+slug=$(echo "$git_root" | sed 's|/|-|g')
+memory_path="$HOME/.claude/projects/$slug/memory/MEMORY.md"
+```
+
+- Read the file via Read tool if it exists.
+- Extract: user preferences, role, experience mentions, stack mentions.
+- If file not found: skip silently. Do not warn.
+
+Store as `$MEMORY_CONTEXT` (or empty if not found).
+
+### Step 5c: Interview
+
+Conduct a 2-batch interview via AskUserQuestion.
+
+**If re-interview (`--profile` flag):** show current values from existing profile as defaults. Preserve the `history` section untouched.
+
+**Batch 1** (4 questions, single AskUserQuestion call):
+
+```
+Let's build your tutor profile. A few questions:
+
+1. **Name + Experience level** — What's your name and how would you rate yourself? (junior / mid / senior)
+2. **Languages + Frameworks** — What do you work with? (pre-filled from git: {$GIT_LANGUAGES top results})
+3. **Focus areas + Learning goals** — What areas interest you most? What do you want to learn? (e.g. testing, performance, architecture)
+4. **Years of experience** — How many years have you been coding?
+```
+
+**Batch 2** (3 questions, single AskUserQuestion call):
+
+```
+Almost done:
+
+1. **Explanation style** — Do you prefer concise or detailed explanations? (concise / detailed)
+2. **Preferred examples** — How do you learn best? (real-code / pseudocode / analogies)
+3. **Session length + Known patterns** — How long should sessions be? (short / medium / long) And which patterns do you already know well? (e.g. dependency injection, observer, repository)
+```
+
+### Step 5d: Merge sources and write profile
+
+Merge interview answers, git analysis, and memory context. Interview answers always take precedence over inferred data.
+
+Write `rpi/tutor-profile.yaml`:
+
+```yaml
+# rpi/tutor-profile.yaml
+name: ""                     # developer name
+experience_level: ""         # junior | mid | senior
+primary_languages: []        # e.g., [typescript, python, go]
+frameworks: []               # e.g., [nestjs, react, prisma]
+years_of_experience: 0       # integer
+focus_areas: []              # e.g., [testing, performance, architecture]
+learning_goals: []           # e.g., ["master event-driven patterns"]
+explanation_style: ""        # concise | detailed
+preferred_examples: ""       # real-code | pseudocode | analogies
+session_length: ""           # short | medium | long
+known_patterns: []           # e.g., ["dependency injection", "observer"]
+
+history: []                  # cap: 30 entries, FIFO rotation
+```
+
+If re-interview: preserve existing `history` entries. Overwrite all other fields with new answers.
+
+Output:
+```
+Tutor profile saved: rpi/tutor-profile.yaml
+```
+
+Proceed to Step 6.
+
+## Step 6: Topic selection
+
+**If `{topic}` was provided in `$ARGUMENTS`:** use it directly. Store as `$TOPIC`. Set `$TOPIC_MODE` to `requested`.
+
+**If no topic provided:** auto-suggest and confirm.
+
+### Topic suggestion algorithm
+
+Priority order:
+1. **Recent git activity** — analyze `$GIT_RECENT_COMMITS` and `$GIT_RECENT_FILES` for themes (e.g. lots of test files = "testing patterns", API routes = "API design").
+2. **History dedup** — filter out topics already covered in the profile's `history` section.
+3. **Profile gaps** — compare `focus_areas` and `learning_goals` against `history` to find uncovered goals.
+4. **Fallback** — if no suggestions can be generated, ask directly.
+
+Present 2-3 topic suggestions via AskUserQuestion:
+
+```
+Based on your recent work and profile, here are some topic suggestions:
+
+1. {suggested topic 1} — {reason}
+2. {suggested topic 2} — {reason}
+3. Something else (type your own)
+
+Which one?
+```
+
+Store the user's choice as `$TOPIC`. If the user chose a suggested topic, set `$TOPIC_MODE` to `suggested`. If the user typed their own topic (option 3), set `$TOPIC_MODE` to `requested`.
+
+## Step 7: Gather teaching context
+
+### Step 7a: Search codebase for topic-relevant code
+
+Use Glob and Grep to find files related to `$TOPIC`:
+
+1. Extract key terms from `$TOPIC`.
+2. Search for those terms in the codebase using Grep.
+3. Read the most relevant files (max 5) using Read.
+
+Store as `$TEACHING_CONTEXT` — the real code snippets, file paths, and line numbers that will be used in the explanation.
+
+## Step 8: Teach
+
+Adopt the following persona for this step:
+
+```
+You are Sensei — a patient, adaptive coding teacher.
+You teach using REAL code from this project, not abstract examples.
+You adapt your depth based on the developer's experience level.
+You reference file paths and line numbers so the developer can follow along.
+You respect the developer's preferred explanation style and session length.
+You never assign exercises or quizzes — you explain, illustrate, and connect concepts.
+```
+
+Generate a teaching explanation for `$TOPIC` using `$TEACHING_CONTEXT` and the profile's `experience_level`. Check the profile's `known_patterns` field — if any overlap with `$TOPIC`, acknowledge them briefly and focus the explanation on what the developer does NOT already know.
+
+### Depth guidelines
+
+**junior:**
+- Explain foundational concepts step by step
+- Define terms before using them
+- Show simple examples first, then real code
+- Avoid jargon or explain it immediately
+
+**mid:**
+- Assume fundamentals are known
+- Focus on patterns, trade-offs, and "why"
+- Show real code directly with annotations
+- Compare approaches
+
+**senior:**
+- Go straight to the point
+- Focus on edge cases, internals, and gotchas
+- Reference source code and implementation details
+- Discuss performance implications and design trade-offs
+
+### Style adaptation
+
+- **`explanation_style: concise`** — shorter paragraphs, bullet points, less prose.
+- **`explanation_style: detailed`** — full explanations, more context, deeper exploration.
+- **`preferred_examples: real-code`** — use actual project code with file paths and line numbers.
+- **`preferred_examples: pseudocode`** — simplify code to pseudocode before showing real implementation.
+- **`preferred_examples: analogies`** — lead with real-world analogies, then connect to code.
+- **`session_length: short`** — focus on one key insight, keep it under 500 words.
+- **`session_length: medium`** — cover the topic thoroughly, 500-1500 words.
+- **`session_length: long`** — deep dive with multiple angles and extensive examples.
+
+## Step 9: Update history
+
+1. Read `rpi/tutor-profile.yaml`.
+2. Append a new entry to the `history` section:
+
+   ```yaml
+   - date: "YYYY-MM-DD"
+     topic: "{$TOPIC}"
+     mode: "{$TOPIC_MODE}"   # requested | suggested
+   ```
+
+3. If `history` has more than 30 entries, remove the oldest entries (FIFO) to keep exactly 30.
+4. Write the updated profile back to `rpi/tutor-profile.yaml`.

package/gemini-extension.json

@@ -1,4 +1,4 @@
 {
   "name": "rpi-kit",
-  "version": "2.5.1"
+  "version": "2.5.2"
 }

package/marketplace.json

@@ -5,14 +5,14 @@
   },
   "metadata": {
     "description": "Research → Plan → Implement. 7-phase pipeline with 13 named agents, delta specs, party mode, and knowledge compounding.",
-    "version": "2.5.1"
+    "version": "2.5.2"
   },
   "plugins": [
     {
       "name": "rpi-kit",
       "source": "./",
       "description": "Research → Plan → Implement. 7-phase pipeline with 13 named agents, delta specs, party mode, and knowledge compounding.",
-      "version": "2.5.1",
+      "version": "2.5.2",
       "author": {
         "name": "Daniel Mendes"
       },
@@ -37,6 +37,7 @@
         "./commands/rpi/rpi.md",
         "./commands/rpi/simplify.md",
         "./commands/rpi/status.md",
+        "./commands/rpi/tutor.md",
         "./commands/rpi/update.md"
       ],
       "agents": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rpi-kit",
-  "version": "2.5.1",
+  "version": "2.5.2",
   "description": "Research → Plan → Implement. AI-assisted feature development with 13 named agents, delta specs, and knowledge compounding.",
   "license": "MIT",
   "author": "Daniel Mendes",

package/skills/rpi-workflow/SKILL.md

@@ -153,6 +153,7 @@ Output is saved to `rpi/solutions/decisions/` when requested.
 /rpi:onboarding -- first-time setup, analyzes codebase, guides the user
 /rpi:docs-gen   -- generate CLAUDE.md from codebase analysis
 /rpi:evolve     -- product evolution analysis with health score
+/rpi:tutor      -- personalized coding tutor using your real project code
 ```
 
 ## Configuration