Run any Skill in Manus with one click

doc-config-router

Stars2

Forks0

UpdatedJune 29, 2026 at 19:46

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

michaelwclark

michaelwclark/genomes_agentic_os

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

Doc Config Router

Use this skill before writing or moving documentation in Agentic OS, especially when a request is phrased broadly like "Add this to Notion."

Routing Loop

Load the nearest Agentic OS route layer: ROUTER.md, CONTEXT.md, RULES.md, TOOLS.md, and active work item files.
Read 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.
Run a dry plan:

agentic-os doc-config plan --root <root> --request "<request>" [--domain <domain>] [--project <project>] [--work-item <work_item>] [--questions-present]

Follow the returned search methods in priority order.
Verify Genome's Notion before any Notion write.
Search existing destinations before creating a new page/folder.
Write source-of-truth content to filesystem/work-item files first when a routed work item exists.
Use Notion color variation and rich blocks from doc-config.yml when creating or updating Notion pages.

Bucket Convention

Use SPEC for raw concept, user language, scope, behavior contracts, and acceptance criteria.
Use PLAN/PLANS for implementation sequence and validation.
Use WORKLOGS for timestamped receipt-backed progress. Per-work packets still use WORKLOG.md.
Use QUESTIONS whenever unresolved questions exist.
Use DECISIONS, ARTIFACTS, and CONVENTIONS only when enabled or clearly useful.

Guardrails

Do not create fallback pages in the wrong Notion workspace.
Do not create a child FEATURES bucket inside a spec page by default; Specs is the namespace.
Do not disable filesystem authority unless an explicit local config says another system owns the source of truth.
Do not store secrets, raw tokens, or private connector payloads in doc config or routing artifacts.

More from this repository

same repository

spec-groomer

michaelwclark/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.

2026-07-082

add-env

michaelwclark/genomes_agentic_os

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.

2026-07-052

commitall

michaelwclark/genomes_agentic_os

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.

2026-07-052

composio-cli

michaelwclark/genomes_agentic_os

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.

2026-07-052

los-fast-workon

michaelwclark/genomes_agentic_os

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.

2026-07-052

los-quiet-workon

michaelwclark/genomes_agentic_os

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.

2026-07-052

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.

Doc Config Router

Use this skill before writing or moving documentation in Agentic OS, especially when a request is phrased broadly like "Add this to Notion."

Routing Loop

Load the nearest Agentic OS route layer: ROUTER.md, CONTEXT.md, RULES.md, TOOLS.md, and active work item files.
Read 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.
Run a dry plan:

agentic-os doc-config plan --root <root> --request "<request>" [--domain <domain>] [--project <project>] [--work-item <work_item>] [--questions-present]

Follow the returned search methods in priority order.
Verify Genome's Notion before any Notion write.
Search existing destinations before creating a new page/folder.
Write source-of-truth content to filesystem/work-item files first when a routed work item exists.
Use Notion color variation and rich blocks from doc-config.yml when creating or updating Notion pages.

Bucket Convention

Use SPEC for raw concept, user language, scope, behavior contracts, and acceptance criteria.
Use PLAN/PLANS for implementation sequence and validation.
Use WORKLOGS for timestamped receipt-backed progress. Per-work packets still use WORKLOG.md.
Use QUESTIONS whenever unresolved questions exist.
Use DECISIONS, ARTIFACTS, and CONVENTIONS only when enabled or clearly useful.

Guardrails

Do not create fallback pages in the wrong Notion workspace.
Do not create a child FEATURES bucket inside a spec page by default; Specs is the namespace.
Do not disable filesystem authority unless an explicit local config says another system owns the source of truth.
Do not store secrets, raw tokens, or private connector payloads in doc config or routing artifacts.