Name: docs
Author: OTM-Cyber

Imported from OTM-Cyber/screenconnect-mcp (docs/AGENTS.md). Install upstream with npx skills add OTM-Cyber/screenconnect-mcp --skill docs. Copyright stays with the author.

Documentation Router

Use docs/ only as a router. Do not create generated files directly in this directory. For lifecycle order or skip/reorder/revisit decisions, read docs/assets/references/lifecycle.md and surface departures from the default arc.

Source Markdown NEVER uses semantic line breaks
For path and link hygiene, use project-relative paths and relative Markdown links, and read docs/assets/references/path-and-link-hygiene.md when auditing or deciding whether an absolute path is warranted.
For design docs, read docs/assets/references/design-workflow.md, docs/assets/references/design-contract.md, and docs/assets/templates/design.md, then continue in docs/designs/.
For plans, read docs/assets/references/planning-workflow.md and the selected plan template in docs/assets/templates/, then continue in docs/plans/.
For PRD or work generation, read docs/assets/references/execution-workflow.md, docs/assets/references/output-contract.md, and the selected template in docs/assets/templates/, then continue in docs/prd/ or docs/work/; work phase tasks use - [ ] t1: ... checkbox items and acceptance criteria use plain bullets.
For requirement changes, also read docs/assets/references/prd-change-management.md before choosing change templates or delta outputs.
For gaps, drift, unresolved questions, risks, decisions, or closeout findings, first update docs/prd/03-open-questions-and-risk-register.md when it exists; do not create separate questions, decisions, risks, gaps, or architecture-decision files unless the user explicitly asks.
For guides, continue in docs/guides/; for playbooks, continue in docs/library/playbooks/. Before guide or playbook coverage work, read docs/assets/references/coverage-pass-contract.md; before guide writing, also read docs/assets/references/guide-contract.md, inspect existing guides for overlap, choose the verdict and target persona(s), and use the matching guide template.
After guide work, reconcile overlapping existing guides with reciprocal links, related frontmatter, or concise supplemental context when it improves discoverability.
Use ## Future Coverage inside guides for downstream-dependent guide updates. Do not create design docs, architecture decisions, or PRD risk-register items solely to remember future guide work.
For history records, continue in docs/assets/history/ — read docs/assets/references/history-record-contract.md and docs/assets/templates/history-record.md before writing.
For reusable prompt starters, use docs/assets/prompts/; prompts are optional starters, not authority.

{ "ocm": "1", "id": "otm-cyber-screenconnect-mcp-docs", "kind": "skill", "name": "docs", "description": "Use `docs/` only as a router. Do not create generated files directly in this directory. For lifecycle order or skip/reorder/revisit decisions, read `docs/assets/references/lifecycle.md` and surface departures from the default arc.", "publisher": "OTM-Cyber", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use `docs/` only as a router. Do not create generated files directly in this directory. For lifecycle order or skip/reorder/revisit decisions, read `docs/assets/references/lifecycle.md` and surface departures from the default arc." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/OTM-Cyber/screenconnect-mcp", "path": "docs/AGENTS.md", "ref": "d554f27ea37e90269c361ac41d1b0e5b86f73829", "url": "https://github.com/OTM-Cyber/screenconnect-mcp/blob/d554f27ea37e90269c361ac41d1b0e5b86f73829/docs/AGENTS.md", "key": "OTM-Cyber/screenconnect-mcp/docs/AGENTS.md" } }, "instructions": "\n# Documentation Router\n\nUse `docs/` only as a router. Do not create generated files directly in this directory. For lifecycle order or skip/reorder/revisit decisions, read `docs/assets/references/lifecycle.md` and surface departures from the default arc.\n\n- Source Markdown NEVER uses semantic line breaks\n- For path and link hygiene, use project-relative paths and relative Markdown links, and read `docs/assets/references/path-and-link-hygiene.md` when auditing or deciding whether an absolute path is warranted.\n- For design docs, read `docs/assets/references/design-workf", "cost": { "context_tokens": 671 } }

docs

About

Documentation Router

Use it

Manifest

Reviews