context-mode-ops
SolidManage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- mksglu
- Repository
- mksglu/context-mode
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- NOASSERTION
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
context-mode-ops
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
orchestrator
Run as a lean-context ORCHESTRATOR — route, synthesize, and decide, while every unit of heavy work goes to a concurrent subagent with a deliberately chosen model. Use whenever the user says "act as orchestrator", "you are the orchestrator", "delegate to subagents", "keep your context lean", "spawn agents for this", or kicks off a multi-part build / review / migration / deploy task that should be run by a fleet rather than inline. Covers delegation rules, per-agent model selection, task naming, scratchpad handoff, wave execution, resume-after-limits, and approval gates. For BMAD-Method sessions use orchestrator-bmad instead.
agent-conduct
Use when starting a new task or session in this repository and deciding what to load first and in what order (AGENTS, README, manifests, active process/stage definitions, role competencies); when a stage step names an execution role and its competencies need resolving; when deciding whether to ask a clarifying question versus proceed; when a different execution role should run as an isolated sub-agent rather than continuing in the current context; when choosing which capability and provider to reach for (semantic, structural, or text search; knowledge retrieval; execution; context optimization) and in what order; when checking whether another installed plugin already owns a rule before writing a new one; or when deciding how verbose to be, whether to read a whole file versus a ranged slice, or how to point at a large existing artifact instead of re-pasting it. Covers `agent-conduct.md` (the canonical capability model, provider mapping, search strategy, and tool-agnostic contributor behavior rules) and `ai-con