supernemawashi

Analyzes ONE psychological framework for ONE profiled person and writes the result to PROFILE_DIR/<name>/frameworks/<slug>.md. Use when dispatched by nemawashi-analyze. Each invocation handles exactly one framework; the parent dispatches one per framework defined in skills/nemawashi-analyze/FRAMEWORKS.md, in parallel. <example> Context: nemawashi-analyze running for profile "alice" parent: dispatches one framework-analyzer agent per row in skills/nemawashi-analyze/FRAMEWORKS.md, in parallel </example> <example> Context: migration 03-frameworks-split applies to one profile migration-applier (intermediate parent): dispatches one framework-analyzer agent per registry framework for the profile </example>

Applies ONE on-disk migration to ONE profile directory. Use when dispatched by nemawashi-migrate for parallel application across N profiles. <example> Context: nemawashi-migrate is running 03-frameworks-split across 16 profiles parent: dispatches 16 migration-applier agents in parallel, each receiving the migration markdown + one profile name </example> <example> Context: nemawashi-migrate is running 01-facts-md-to-jsonl across 15 legacy profiles parent: dispatches 15 migration-applier agents </example>

Collects facts about ONE target person from available MCP sources (Slack, Gmail, Calendar, GitHub) and writes them to PROFILE_DIR/<name>/. Use when dispatched by nemawashi-collect for one target. The parent filters which adapters are usable; this agent executes their recipes against the target. <example> Context: nemawashi-discover finds 5 untracked people the user wants profiled parent: dispatches 5 profile-collector agents in parallel, one per target </example> <example> Context: user runs "/nemawashi-collect Alice" and the parent chooses to dispatch (e.g. when work would otherwise pollute the main context) parent: dispatches profile-collector with target=Alice </example>

Runs the full profile refresh pipeline (collect → analyze) for ONE target person. Use when dispatched by nemawashi-update for parallel application across N profiles. <example> Context: user runs "/nemawashi-update Alice Bob Carol" parent: dispatches 3 profile-updater agents in parallel, one per target </example> <example> Context: user runs "/nemawashi-update --all" across 15 profiles parent: dispatches 15 profile-updater agents, batched 5 concurrent to respect MCP rate limits </example>

Use when user wants to analyze a person's behavioral patterns - reads profile data and adds psychological analysis with actionable DO/DON'T communication rules

Use when user wants to check which profiles need re-analysis - scans all profiles for staleness and new unanalyzed data

Use when user wants to create or update a person's profile - collects data from available MCP sources (Slack, Gmail, Calendar, GitHub, and any other discoverable sources via the adapter pattern) and writes to PROFILE_DIR

Use when user wants to find people they interact with but haven't profiled yet - scans available MCP sources (Slack, Gmail, Calendar, GitHub, and any other discoverable sources via the adapter pattern) for untracked contacts

Use when the user wants to file a GitHub issue against this repo from free-form feedback or an idea surfaced in conversation — drafts a house-style body, surfaces duplicates, and files via gh after explicit confirmation.

1 hook across 1 event