dev-manager
Manages coordination between multiple dev agents working on a single project feature or goal.
Install
mkdir -p .claude/skills/dev-manager && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12021" && unzip -o skill.zip -d .claude/skills/dev-manager && rm skill.zipInstalls to .claude/skills/dev-manager
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Orchestrate multiple dev agents (spawned subagents OR human-driven worktrees) against ONE story-level outcome — hold the e2e vision, decompose into non-overlapping linked tasks with freeze/secrets guardrails baked in, monitor the tasks for movement, and intervene only on collision or drift. Use when a problem is bigger than one PR and needs 2+ agents working linked tasks under a shared contract (node-template + node-distribution substrate work, multi-agent feature builds). Triggers: "manage these devs", "coordinate subagents", "split this into tasks for N agents", "hold the story while agents work the tasks", "dev manager".Key capabilities
- →Decompose a story into non-overlapping linked tasks
- →Inject guardrails into every task
- →Monitor linked tasks for movement
- →Intervene on collision or drift between tasks
- →Route finished tasks to done
How it works
This skill holds the end-to-end vision for a story, decomposes it into linked tasks with guardrails, and monitors task progress. It intervenes only when tasks collide or drift from their contract.
Inputs & outputs
When to use dev-manager
- →Coordinate multiple dev agents
- →Manage complex feature implementation
- →Split tasks across agents
About this skill
dev-manager
The contract lives in the hub entry dev-manager-contract. This file only triggers it. The loaded session cognition agent-contract owns all normal communication.
Read the full body before acting, using the current node's origin (operator: https://cognidao.org) and the COGNI_NODE_API_KEY saved in .env.cogni:
curl -fsS -H "Authorization: Bearer $COGNI_NODE_API_KEY" \
"https://cognidao.org/api/v1/knowledge/dev-manager-contract" | jq -er .content
Its lifecycle table is the checklist every task must pass. Also read cicd-e2e-required-sequence the same way; it holds the operator calls for review, flight, merge and promote.
If the fetch fails, retry once. If it still fails, report the failure and do not improvise the lifecycle.
When not to use it
- →Problems smaller than one PR
- →When only one agent is working
- →When a human wants to implement directly
Limitations
- →No manager-authored, dev-readable, free-text direction field for pre-PR decision points
- →Work item GET requests do not return body or summary
- →Claims do not appear in assignees or status
How it compares
This workflow coordinates multiple agents on linked tasks under a shared contract, rather than individual agents working in isolation.
Compared to similar skills
dev-manager side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dev-manager (this skill) | 0 | 5mo | Caution | Advanced |
| chief-architect | 6 | 11mo | No flags | Advanced |
| ralplan | 1 | 6mo | Review | Intermediate |
| moai-workflow-thinking | 2 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by cogni-dao
View all by cogni-dao →You might also like
chief-architect
ananddtyagi
PERSONAL APP ARCHITECT - Strategic development orchestrator for personal productivity applications. Analyzes project context, makes architectural decisions for single-developer projects, delegates to specialized skills, and ensures alignment between user experience goals and technical implementation. Optimized for personal apps targeting 10-100 users.
ralplan
Yeachan-Heo
Iterative planning with Planner, Architect, and Critic until consensus
moai-workflow-thinking
modu-ai
Sequential Thinking MCP and UltraThink mode for deep analysis, complex problem decomposition, and structured reasoning workflows
agent-migration-plan
ruvnet
Agent skill for migration-plan - invoke with $agent-migration-plan
granola-reference-architecture
jeremylongshore
Enterprise meeting workflow architecture with Granola. Use when designing enterprise deployments, planning integrations, or architecting meeting management systems. Trigger with phrases like "granola architecture", "granola enterprise", "granola system design", "meeting system", "granola infrastructure".
phased-migration-plan
kaladron
Author or update a phased plan-*.md document for a multi-step migration or refactor. Use when a change is too large for a single commit, when coordinating database/architecture migrations across many call sites, or when the user asks for a "plan" before implementation. Covers the standard plan struc