emmy-agent-marketplace

Use when planning, implementing, reviewing, or verifying CMS Hybrid Cloud infrastructure that needs Splunk integration, including CloudWatch Logs, CloudWatch Agent configuration, S3 service-log fallback, Splunk sourcetypes and indexes, EUA job code access, and efficient Splunk Search Head verification.

Draft and approval-gate FFS Jira tickets for work created by Emmy governance decisions, governance documents, ATO control findings, or implementation gaps. Use when a Confluence governance page, ATO/CFACTS control, policy decision, repo configuration, or system evidence implies follow-up engineering, remediation, evidence, decision, or CFACTS update work.

Use when interpreting, drafting, refining, or creating Emmy Jira tickets in the FFS project, especially when an agent needs to apply team ticket conventions for engineering, product, API, design, bug, spike, epic, infrastructure, or ATO-labeled work; choose issue type/labels/priority; format Jira wiki descriptions; inspect similar tickets or epics; or create Jira issues through the CMS Atlassian MCP server with explicit human approval.

Facilitate interactive development of the ideas behind a future Emmy governance document. Use when a human wants to explore, shape, pressure-test, or reason through a governance need, operating model, policy, process, decision, or obligation before drafting the Confluence governance document.

Draft or create Emmy governance documents from an already-developed system, process, policy, or operating model. Use when asked to write, draft, create, update, or publish a Confluence governance document for Emmy ATO, open source, release, state communication, or internal governance work; do not use to develop the underlying plan itself.

Review and assess Emmy governance documents from Confluence pages, pasted text, or local Markdown. Use when asked to read, assess, critique, grade, approval-check, or recommend revisions for an Emmy governance document, including ATO, open source, release, state communication, or internal governance artifacts.

Append an approved Emmy planning-session entry to the Goals Space Planning Log in Confluence. Use only when the user explicitly authorizes recording a planning session after planning context was read; never use for ambient lookup, ticket creation, or editing goals, outcomes, or principles.

Load the Emmy Goals Space as ambient planning context from Confluence. Use when Emmy work involves planning, goal alignment, ticket proposals, roadmap decomposition, outcome selection, prioritization, or checking whether work fits current strategic principles, active delivery goals, and applicable planning requirements.

Ingest Emmy Goals Space principles and goals from pasted text or local files into Confluence with a human approval gate. Use only when explicitly asked to import, ingest, add, or update Emmy planning principles, goals, outcomes, or "principals"; never use for ambient planning lookup, Jira ticket creation, or Knowledge Store ingestion.

Load active Emmy planning requirements from the Goals Space requirements layer. Use when Emmy planning, ticket proposals, release readiness, architecture decisions, or goal/outcome alignment need requirement constraints, blockers, due dates, owners, or evidence links.

Ingest Emmy planning requirements from pasted text, local files, or named Confluence pages/page IDs into the Goals Space Requirements Registry with an explicit human approval gate. Use only when asked to import, ingest, add, or update requirements, compliance obligations, ATO constraints, regulatory blockers, due dates, or evidence expectations; never use for ordinary principles/goals ingestion, ambient planning lookup, Jira ticket creation, or Knowledge Store ingestion.

Interpret Emmy requirement language without writing. Use when analyzing ATO, privacy, security, data-sharing, release, accessibility, or operational source text to distinguish true requirements from tasks, evidence, assumptions, open questions, and non-requirements.

Use only when explicitly asked to ingest knowledge into the Emmy Agent Knowledge Store from a local file, URL, external Confluence page, or Emmy GitHub repository checkout with traceable source provenance.

Use when a human wants to audit or maintain the Emmy Agent Knowledge Store as a whole: find duplicate or overlapping pages and claims, identify stale or contradictory content, recommend labels, and decide whether new child pages should be added before any Confluence cleanup or reorganization.

Use when an Emmy task may benefit from the shared Confluence knowledge store: product context, architecture, ATO, onboarding, runbooks, decisions, troubleshooting, stale context, prior team knowledge, or durable task learnings that should be captured or published through cms-atlassian-confluence.

Use when a human wants to interactively review, validate, and promote pending Emmy Knowledge Ingestion Queue entries into canonical knowledge-store content.