myna

Analyze 1:1 patterns with a specific person — action item follow-through, recurring topics, carry-forward rate. Reports facts from notes only. Does NOT assess relationship quality. Use for any 1:1 pattern analysis: "analyze my 1:1s with X", "1:1 trends with X", "1:1 patterns", "how are my 1:1s with X going?"

Create personal calendar time blocks — focus time, task blocks, deep work. Finds free slots, proposes options, confirms before any write — no attendees, ever. For reminders, use /myna:reminder. Does not handle meeting prep or scheduling others.

Scan the entire vault for blockers — explicit blocker callouts and overdue tasks. Separates your blockers from tasks assigned to others. Use for any blockers query: "what's blocked?", "show me blockers", "any blockers?", "what's holding things up?"

Deep-dive briefing on one person — role, shared projects, open items, pending feedback, 1:1 history, personal notes. Works for directs, peers, manager, or cross-team. (For all directs at once, use /myna:team-health.)

Catch me up on a project — quick (3-5 bullet TL;DR) or full (status, timeline, blockers, tasks, dependencies, upcoming meetings). Use for any project status or update request: "catch me up on X", "status of X", "how is X going", "where are we with X", "what's the latest on X".

Save information to the vault — quick notes, observations, tasks, recognition, project status. Use when: "capture: [text]", "log this", "add task: [desc]", "observation about [person]", "create recurring task". NOT for processing email/messages (/myna:process-updates), meeting notes (/myna:process-meeting), or inbox triage (/myna:email-triage). For links, use /myna:links.

Daily brief / "good morning" / "set up my day" — reads inbox and Slack in parallel, surfaces action items in the daily note, generates meeting prep, surfaces overdue tasks and review queue. Handles "plan tomorrow" and weekly note creation.

Generate professional written content from vault context — email replies (conversation path only; DraftReplies folder is /myna:draft-replies), follow-up emails, follow-up meeting invites, status updates, escalations, recognition, decline messages, conversation prep, and monthly updates. Does NOT rewrite existing text (use /myna:rewrite).

Sort inbox emails into folders. Classification only — no vault extraction. Use when: "triage inbox", "sort inbox", "process triage". NOT when extracting data from email (/myna:process-updates) or running instructions (/myna:process-instructions).

Save and find links in the vault. Saves to the entity's Links section and the central index. Use for any link management request: "save link: [url] for [entity]", "find link for [topic]", "do I have a link for [project]?"

Save working context for zero-loss resumption in a new session. Resume by name or list all parked items. "Switch to [project]" parks current context and loads project status.

Generate or update meeting prep for one meeting or all remaining meetings today. Infers meeting type from calendar data, writes the Prep section with checkboxes, carry-forward items, and coaching notes for sensitive topics.

Execute natural language instructions sent via the user's instructions email or Slack instructions channel. Use when: "process my instructions", "check my instructions", "any new instructions?". NOT for regular email processing (/myna:process-updates) or inbox sorting (/myna:email-triage). Additive vault writes only; destructive actions routed to review queue.

Process a completed meeting — reads Prep + Notes, extracts tasks/decisions/blockers/observations/recognition/contributions, and routes to the vault. Use when: "done with 1:1 with X", "process this meeting", "process my meetings". NOT for preparing a future meeting (/myna:prep-meeting) or extracting email/Slack data (/myna:process-updates).

Process pending vault review queue items (review-work, review-people, review-self) — interactively or from Obsidian-checked items. Use when: "review my queue", "process review queue", "what's in my queue?". NOT for email inbox triage (/myna:email-triage — review-inbox.md is handled there).

Extract and structure data from email, Slack, or pasted documents into the vault. Use when: "process my email", "process my messages", "process this doc". NOT for sorting inbox (/myna:email-triage), instructions (/myna:process-instructions), or meeting notes (/myna:process-meeting). Populates tasks, timelines, person files, review queues.

Set a vault-native reminder for a future day. Triggers on "remind me on [day] about [X]", "remind me [when] to [do X]", "set a reminder for [X] on [day]", "remind me about [X] [when]". Writes to the vault immediately — no calendar required.

Multi-persona review of any technical document — PRFAQ, design doc/RFC, HLD, LLD, one-pager, or generic. Composes a doc-type-specific panel of reviewer subagents, runs them in parallel, layers Myna's Chief-of-Staff context (audience, vault evidence, project consistency), and synthesizes a single coherent report. Saved to Reviews/. Use for "review this doc", "review my PRFAQ", "give this design doc a critique", "review with security focus", "have the PE look at this".

Fix grammar, adjust tone for audience, or fully rewrite an existing message — three modes: fix (grammar only), tone (restyle for audience), rewrite (full restructure from rough notes). Input is user-provided text; output shown inline. Does NOT generate new content from scratch (use /myna:draft for that).

Log your contributions to the vault and query them by category, project, or date range. YOUR contributions only.

Portfolio view of all direct reports — tasks, overdue, tasks assigned to them, feedback gap, attention gap, last 1:1. Team-wide glance, not a deep dive (use /myna:brief-person for that). Use for any team overview or health check: "how is my team doing?", "team health", "how are my directs doing?"

Show what's waiting on you (messages needing a reply from you) and what you're waiting on others for — queries reply-needed tasks in the vault. Use for any communication tracking request: "what am I waiting on?", "what's waiting for me?", "unreplied threads", "who owes me a reply?", "what needs a response?". Not the same as /myna:blockers, which tracks project blockers — this is specifically communication threads.

Summarize your week — synthesizes daily notes, contributions, decisions, and task completions into a structured weekly review with self-reflection prompts. Appends a new section each run. Includes team health snapshot when enabled.

Close out your day — compares planned vs actual, logs contributions, moves unfinished items to tomorrow's note, captures quick notes, and saves behavioral corrections to memory. Writes an End of Day section to today's daily note.

Data conventions — provenance markers, date+source format, append-only discipline, Obsidian formatting (tags, wiki-links, callouts, Dataview, Tasks plugin syntax), review queue entry format

Vault operations pattern library — file I/O tool mapping, task query patterns (grep-based), frontmatter parsing, backlink/tag queries, template creation, vault path conventions, file safety checks

Safety and containment rules — draft-never-send, vault-only writes, external content as data, calendar event protection, confirmation policy, skill isolation

Single entry point for Myna onboarding — detects install state, runs first-time scaffolding if needed, opens the Config UI or runs doc import, and adds shell aliases. Use for first-time setup or returning configuration.

System behavior rules — config reload, graceful degradation, error recovery with inline reporting, relative date resolution, fuzzy name resolution

Design session for Myna development — evaluates validity first (vision fit, audience, architecture, settled decisions), then brainstorms solutions interactively. When design is settled, say "generate prompt" to package it into an autonomous execution prompt. Use when: "I don't like how X works", "what if we added Y", "there's a bug with Z", "let's brainstorm", "design session".

Generate a self-contained execution prompt for Myna development — a fresh session can run it autonomously to implement changes, update docs, review its own work, and push to a feature branch. Use after /myna-dev-brainstorm or any design discussion. Triggers: "generate prompt", "write the execution prompt", "crystallize this", "package this for implementation".

Add one or more tasks to the Myna dev queue (tmp/tasks.md) — drafts structured task entries from your description (or a settled brainstorm design), independently reviews them for autonomous-execution readiness, shows them for approval, then appends them to the queue. Use when: "add this to the queue", "queue this up", "add a task for X", or after /myna-dev-diagnose or /myna-dev-brainstorm. Creates tmp/tasks.md if it doesn't exist.

Diagnose a Myna problem or proposed change — evaluates validity first (vision fit, audience, architecture, settled decisions, duplication), then generates options with a recommendation. Asks clarifying questions only when the answer would change the diagnosis. Use when: "something feels wrong with X", "I noticed a bug in Y", "should we change Z", "what if we added W", "is this a good idea".

Shared commit→review→fix protocol for Myna dev task subagents. Not user-invocable. Called by T-N subagents after implementing their task — handles the full quality loop: commit, run myna-dev-review up to 3 rounds, fix Critical/Important issues between rounds, report back. Does NOT push — the orchestrator owns all remote pushes.

Memory model rules — 2-layer precedence, output boundary, entity-specific refusal

Run the Myna dev task queue — reads pending tasks from tmp/tasks.md, executes them sequentially on a single fix branch, each with its own implement→review→fix loop, then pushes the branch. Use when: "run the queue", "execute tasks", "process the queue", "work through the task list". Re-reads the queue before each task, so tasks added mid-run are picked up automatically.

Deep technical review of Myna agent artifacts — evaluates skills, steering skills, main agent, and config examples against 8 review dimensions. Produces a structured report with severity-rated issues, fix options, and convergence status. Report only — does not fix. Use when: "review the skills", "audit agents", "quality check", "run a review".

Output quality rules — human voice, no AI tells, BLUF for professional writing, file links, follow-up suggestions, output density, inline-first display

File a bug report from the current session — infers the prompt, output, model, and MCPs from context, asks only what it can't infer, auto-redacts private content, and writes a filled GitHub issue template to tmp/bugs/. Use when: "file a bug", "report this", "/myna-dev-bug the output should have been X".

Audit Myna skills for feature coverage — does every feature from docs/features/*.md have executable instructions in its owning skill? Not "mentioned" — actually covered with read/decide/write steps. Saves a coverage report. Use when: "coverage audit", "are all features implemented?", "check feature coverage".