using-supernemawashi

name	using-supernemawashi
description	Use when starting any conversation - establishes how to find and use interpersonal communication skills

Using supernemawashi

You have access to interpersonal communication skills. These help you navigate workplace dynamics, craft strategic replies, and prepare for meetings.

Available Skills

All skills are verb-first under the nemawashi- prefix.

Skill	Use When
supernemawashi:nemawashi-collect	User wants to create or update someone's profile
supernemawashi:nemawashi-update	User wants to refresh one or more profiles end-to-end (collect + analyze in one invocation)
supernemawashi:nemawashi-analyze	User wants to analyze someone's behavioral patterns
supernemawashi:nemawashi-show	User wants to view, list, or display existing profiles (read-only)
supernemawashi:nemawashi-discover	User wants to find people they interact with but haven't profiled yet
supernemawashi:nemawashi-check	User wants to check which profiles are stale or need re-analysis
supernemawashi:nemawashi-note	User wants to manually record one observation about a person — typically from an off-MCP interaction (1:1, phone, hallway) that adapters can't see
supernemawashi:nemawashi-reply	User needs help replying to someone or deciding what to say
supernemawashi:nemawashi-issue	User wants to file a GitHub issue against this repo from feedback or an idea surfaced in conversation

Updating a profile is normally a 2-step pipeline: nemawashi-collect (pull from MCP sources — slow, rate-limited) → nemawashi-analyze (local-only — fast). They are kept as separate skills so re-analysis without re-collection is cheap.

Skill Routing

When the request is ambiguous, use this decision tree:

"create profile for X" / "collect <new person>" (no existing profile)
  → nemawashi-collect (then suggest nemawashi-analyze)

"update <existing>" / "refresh <existing>" / "X を update して" / single-shot collect+analyze
  → nemawashi-update

"analyze X" / "what kind of person is X?"
  → nemawashi-analyze

"show X" / "view X's profile" / "X見せて" / "Xのprofile" / "list profiles" / "誰がいる?"
  → nemawashi-show

"update all profiles" / "全員 update" / "--all" / "refresh everyone"
  → nemawashi-update --all (parent skill handles the 5-concurrent throttle)

"check profiles" / "which are stale?" / "who needs re-analysis?"
  → nemawashi-check (can launch parallel agents to re-analyze)

"discover people" / "who am I missing?"
  → nemawashi-discover

"note that X said / did Y" / "メモっといて Xが…" / "1:1 で X が…"
  → nemawashi-note (manual one-line fact entry, off-MCP observation)

"how should I reply to X?" / "what should I say?"
  → nemawashi-reply

"issue にしといて" / "FB として残しといて" / "this should be an issue" / "file that"
  → nemawashi-issue (drafts a house-style body, confirms, files via gh)

Key disambiguations:

• Specific person → nemawashi-collect or nemawashi-analyze. Multiple/all people → dispatch parallel agents (see Bulk Operations).
• "Check" or "status" → nemawashi-check (read-only by default; can dispatch agents to re-analyze if the user opts in).
• "Show" / "view" / "見せて" / "見たい" → nemawashi-show (read-only display, no analysis or modification).

Bulk Operations

For multi-person operations ("update all profiles", "batch update", "re-analyze everyone"), dispatch parallel agents — one per person — each invoking the appropriate skill. Aggregate results in the main session.

• nemawashi-analyze is local-file-only, so parallelism is unconstrained.
• nemawashi-collect hits MCP sources (Slack/Gmail/Calendar/GitHub); for 5+ profiles, stagger dispatch in batches of 5 to avoid rate limits.

To triage first (find stale profiles, then re-analyze only those), use nemawashi-check.

The Rule

Invoke relevant skills BEFORE any response or action. If a user mentions replying to someone, preparing for a meeting, or dealing with a person — check for applicable skills.

Migration Nudge

If a <MIGRATION_AVAILABLE> block appears in the SessionStart system-reminder, your first reply of the session must include a one-line proactive aside — before addressing the user's actual request — pointing them at the migrate skill. Suggested format:

Note: pending profile migrations detected (<ids>). Run /supernemawashi:nemawashi-migrate when you have a moment.

This is a passive nudge. Do not block the user's request, do not push if they decline, and do not repeat on subsequent turns of the same session.

Variables

These variables are referenced by all supernemawashi skills. Do not redefine in individual skills.

• PROFILE_DIR = ~/.local/share/supernemawashi/profiles

Profile Data

Profiles are stored in PROFILE_DIR/<person-name>/:

• profile.md — Slim index: Basic Info, Communication Patterns, Active Channels, Work Patterns (manual) + Core Pattern + Framework Summary table (analysis)
• relationship.md — Your relationship and approach strategies
• facts.jsonl (newer) / facts.md (legacy) — Chronological record of statements and actions
• contradictions.md — Detected contradictions
• frameworks/<slug>.md — One file per psychological framework, each with Classification + Evidence + situation-indexed DO/DON'T rules

Always check if a profile exists before advising on communication with someone. If no profile exists, suggest running nemawashi-collect first.

Situation Categories

DO/DON'T rules live in frameworks/<slug>.md under ## Rules → ### <situation>, organized by these 4 situation categories. nemawashi-analyze generates them (one file per framework, in parallel); nemawashi-reply consumes them selectively (load only the 2-3 framework files relevant to the situation). Do not redefine in individual skills.

1. When Requesting — you need something from them
2. During Conflict — disagreement or tension
3. When Reporting — delivering news (good or bad)
4. Routine Collaboration — day-to-day interaction

Coexistence with superpowers

supernemawashi handles interpersonal communication. superpowers handles software engineering workflows. They do not overlap.