em-copilot v0.5.0 Foundation · Assistant

qira - one natural-language front door to the entire EM skill library. The EM speaks plainly and the right skills run, with confirmation gates and memory - and now answers EM questions straight from the EM Library.

Problem it solves: you don't have to remember which skill does what. Say what you want and qira matches intent, builds a plan, confirms before any write, and routes to the correct downstream skill.

qiraUser skillHeavy · ~80-300k

A formal-English assistant with structured output that orchestrates the whole library via natural-language intent. Triggered by /qira …, "hey qira, …", or "qira, …". It is the voice layer - all routing logic lives in the shared core.

When to use it
hey qira, close the quarter for Acme Roboticsrun my weekly sweepreview risks and check-in OKRs for Acme
Reference - what it brings, its process, and what it needs
BringsA single entry point that routes any request (risks, OKRs, feedback, 1:1s, briefings, audits) to the right skill, with greppable skill names, neutral tone and verbatim error preservation.
Process
  1. Load the seven _assistant-core references.
  2. Read its voice guide for register.
  3. Translate each core event (plan_ready, await_confirm, complete, error) into voiced output.
Needs_assistant-coreNotion MCPdownstream skills
_assistant-coreWorkerHeavy · ~80-300k

The voice-agnostic orchestration brain qira is built on - never invoked directly. Defines the intent router, skill catalog, confirmation contract, memory model and multi-step plan composition. Emits structured events; contains zero voice strings.

Reference - what it brings, its process, and what it needs
BringsA reusable routing / planning / confirmation / memory engine that drives the toolkit safely - enforcing write-gates, audit discipline and a 5-step plan cap.
Process
  1. Read auto-memory, match intent, resolve scope.
  2. Build a plan, emit plan_ready.
  3. On confirm, execute sequentially, waiting on each write-gate.
  4. Write last-context back to memory.
NeedsNotion MCPskill-catalog
em-askUser skillLight · ~5-20k

The EM Library coach. Answers a how-do-we / what's-our-policy / coach-me-on question strictly from the EM Library (templates, Big Mac, references, FAQs), with citations - never general or model knowledge. On a miss it declines and logs the question to the EM Library Gaps backlog. Reached by just asking qira.

When to use it
how do we run 1:1swhat does the library say about OKR scoringcoach me on giving feedback
Reference - what it brings, its process, and what it needs
BringsGrounded, cite-or-decline answers about how Qualitara does engineering management - so the library becomes something you can ask, not just read - with every unanswered question captured as a documentation gap.
Process
  1. Load the generated library-index and match the question to 1-3 entries.
  2. Fetch their live Notion content and answer strictly from it, with a Sources line.
  3. If nothing covers it, decline and log one deduped Open row to the Gaps DB.
NeedsNotion MCPlibrary-indexmanifest library block
em-howtoUser skillMedium · ~20-80k

The toolkit usage coach. Answers "how do I use skill X" and "which skill is right for Y" strictly from the docs corpus, with citations - never model knowledge. On a miss it declines and logs an Open row to the Qira Docs Gaps DB. Distinct from em-ask (EM practice questions): em-howto is tooling questions only.

When to use it
how do I use the toolkitwhich skill / workflow is right for Xhow do I use em-boardwhich skill logs a 1:1what do I use to close the quarterhow does the daily routine work
Reference - what it brings, its process, and what it needs
BringsGrounded, cite-or-decline answers about how to use the EM toolkit - so the docs console becomes something you can ask, not just read - with every unanswered tooling question captured as a documentation gap.
Process
  1. Load the manifest and read the generated docs-index.md.
  2. Match the question to 1-3 corpus units; read their docs-corpus files.
  3. Answer grounded in the corpus (or a SKILL.md fallback), with a Sources line.
  4. If nothing covers it, decline and log one deduped Open row to the Qira Docs Gaps DB.
NeedsNotion MCPdocs-indexmanifest docs.gaps_db