create-agent

Automate creation and validation of dev-team subagents with canonical 7-section structure.

1|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/RohiRIK/dev-team --skill create-agent-rohirik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-agent
Source: https://github.com/RohiRIK/dev-team/tree/main/skills/create-agent
Command: npx skills add https://github.com/RohiRIK/dev-team --skill create-agent-rohirik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to automate the end-to-end creation and lifecycle management of dev-team subagents, ensuring consistent structure, tooling, and integration with the task-tracker MCP.

Core Features & Use Cases

  • Create — scaffold new agents that conform to the 7-section spec.
  • Port, Research, Validate, Update — support full lifecycle including references, tool-allowlists, and integration docs.
  • Hand-off and integration — aligns with the task-tracker ecosystem and agent onboarding workflows.

Quick Start

Invoke the Create procedure to scaffold a new agent and run Validate to ensure it conforms to the canonical model.

Frequently Asked Questions about create-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create dev-team subagents that conform to a canonical structure?

To create dev-team subagents, use the automated scaffolding procedure to generate the 7-section specification, enforce the YAML frontmatter contract, and validate shared knowledge references for lifecycle governance.

What is the best way to validate an existing subagent definition against governance rules?

Validating subagent definitions involves running the verify-agents.ts lint script to check the YAML frontmatter contract, canonical sections, and task-tracker integration for structural compliance.

Can I port existing agents into the dev-team ecosystem without rewriting them from scratch?

Yes, you can port existing agents by updating their definitions to align with the canonical 7-section spec, adding tool-allowlists, and integrating references to shared knowledge.

Do I need task-tracker integration for subagent creation and governance?

Task-tracker integration is required during subagent creation to align hand-off workflows and ensure the agent definitions conform to the ecosystem's governance and onboarding standards.

Why does my subagent validation fail when updating agent definitions?

Subagent validation fails when updated definitions breach the YAML frontmatter contract, miss canonical sections, or lack proper references to shared knowledge required by the verify-agents.ts script.

What is the canonical 7-section structure required for dev-team subagents?

The canonical 7-section structure is a standardized specification for dev-team subagents that enforces consistent YAML frontmatter, tool-allowlists, and shared knowledge references for ecosystem governance.