genomes_agentic_os

Groom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.

Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.

Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.

Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.

Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.

Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.

Orchestrated GitHub PR review skill. Use when the user provides a PR link or asks for a senior, blocker-focused pull request review with Jira acceptance, tests, docs, security, architecture, memory, and copy/paste GitHub markdown comments.

Use when LOS implementation needs multi-agent fan-out, several work units, risk-routed quality holdouts, full PR lifecycle management, pre-commit blocked CI fallback, or mandatory Copilot comment resolution with chat kept to receipt-backed milestones only. The orchestrator plans, decomposes, dispatches worker and explorer subagents, verifies returns, and routes gates; evidence lives in the Agentic OS work item and durable PR/Jira summaries. NOT for single-agent quiet edits; use los-quiet-workon. NOT for worktree or stack setup alone; use los-fast-workon. Triggers include "orchestrate this ticket quietly", "fan this out with subagents", resuming noisy orchestration, or long-running LOS work that burns context with status chatter.

Use when an agent needs to monitor GitHub pull request checks without repeatedly printing polling output into the conversation. Starts or uses a file-based PR watcher that writes status artifacts under a specified output folder, usually the task's durable artifact folder, and then the orchestrator inspects those files on a schedule.

Operate Genome's Agentic OS runtime registries, heartbeats, schedules, run queues, and guarded Notion runtime tracking from file-backed state.

Run a Jira or Linear tracker item through project-aware SDLC orchestration, state-machine receipts, mandatory finishing review, PR/CI/Copilot loops, and safe merge or merge-blocked closeout. LOS Work Plan rows are a queue adapter.

Groom Agentic OS self-improvement proposals into spec packets and Linear issues. Use for AOS Product Orchestrator or Auto Groom.

Compatibility alias for auto-spec-intake. Use auto-spec-intake for new long OS-shaping requests; keep this skill callable for legacy /auto-add-feature requests.

Automatically create or update a local Agentic OS spec packet for long OS-shaping requests before implementation work continues. Use when the user gives a multi-part Agentic OS feature/rules/conventions request or says /auto-add-spec.

Capture lightweight Agentic OS or project bug reports through doc-config, project work-items, and optional Notion projection. Use when the user says /add-bug or reports broken behavior, missing logs, routing drift, or missed OS enforcement.

Compatibility alias for spec-intake-router. Use spec-intake-router for new future-work, proposed-feature, and spec intake; keep this skill callable for legacy /new-feature and /add-feature requests.

Create or update Agentic OS spec intake using doc-config routing, project work items, and optional Notion projection. Use when the user asks for /add-spec, a new spec, proposed feature, future plan, rough request, or where to put future work in Agentic OS or Notion.

Use when creating, resuming, or maintaining a long-running initiative or subproject in any Agentic OS domain; builds a durable context pack, project index entries, active-work handoff, and validation trail so future agents can discover the right context quickly.

Inspect unified-memory retrieval analytics — summary, recent runs, method rollups, current-vs-grep-sidecar comparison, health, and markdown/JSON export from the live Atlas memory_ops store. Read-only and redacted.

Coordinate Agentic OS subagents, verification, and integration. Use when the user asks for /orchestrate, delegation, fan-out, parallel agents, implementation planning, or verified merge/integration work.

Inspect Mac host speed risks and Agentic OS generated-artifact hygiene with observe-only reports and approval-gated cleanup classes.

Drive a Kanban-backed implementation queue through orchestrate, producing local worklog artifacts, verified worktree merges, holdout QA, worklog rollups, and board writeback. Use when READY cards should be built in prefix order with tracking notes left on the source board.

Route document captures to configured Agentic OS filesystem and Notion destinations. Use when the user says to add something to Notion, save a note/spec/plan/question/worklog, reorganize docs, or decide where a new page belongs.

Apply compact Agentic OS authoring rules when creating or updating commands, skills, workflows, automations, tools, registries, runtime templates, project worktrees, or reusable OS conventions.

Use when a command, test suite, Docker setup, PR check, watcher, or external wait is expected to run longer than a normal interactive turn and should write artifact-backed state instead of keeping chat alive with polling.

Keep Agentic OS worktree and work-item state clean after Jira terminal statuses or merged pull requests.

Generate a recent Agentic OS status report from Claude/Codex logs, OS state, source status, and Notion projection state.

Prepare runtime integrations such as Orgo.io, Composio, AgentMail, Granola, and Genome's Notion with setup tasks, health checks, approval gates, and tracking fields.