メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | doc-config-router |
| description | 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. |
Use this skill before writing or moving documentation in Agentic OS, especially when a request is phrased broadly like "Add this to Notion."
ROUTER.md, CONTEXT.md, RULES.md, TOOLS.md, and active work item files.harness/rules/os-authoring-rules.md when the request creates or
changes spec/worklog mirrors, workflows, automations, commands, skills, tools,
project worktrees, or reusable convention policy. Use
harness/shared_factory/05-knowledge/references/os-conventions.md only when
deeper background is needed.agentic-os doc-config plan --root <root> --request "<request>" [--domain <domain>] [--project <project>] [--work-item <work_item>] [--questions-present]
doc-config.yml when creating or updating Notion pages.SPEC for raw concept, user language, scope, behavior contracts, and acceptance criteria.PLAN/PLANS for implementation sequence and validation.WORKLOGS for timestamped receipt-backed progress. Per-work packets still use WORKLOG.md.QUESTIONS whenever unresolved questions exist.DECISIONS, ARTIFACTS, and CONVENTIONS only when enabled or clearly useful.FEATURES bucket inside a spec page by default; Specs is the namespace.