agent-selector

Generate agent configuration JSON from PRD technical architecture mappings.

Updated Aug 23, 2026

Search Tags:#automation #tech stack #agent selection #PRD #mapping

Ready to run

npx skills add https://github.com/turbobeest/dev-system --skill agent-selector-turbobeest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-selector
Source: https://github.com/turbobeest/dev-system/tree/main/skills/agent-selector
Command: npx skills add https://github.com/turbobeest/dev-system --skill agent-selector-turbobeest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Selects and configures agents from the agents repo based on the PRD's tech stack, executed after task decomposition and before specification generation.

Core Features & Use Cases

Tech-to-agent mapping: Maps languages, frameworks, databases, and infra to appropriate agents.
Security & scale considerations: Picks auditors and scale-focused agents based on PRD sections.
Config generation: Produces agent-config.json with a local/ upstream strategy.

Quick Start

Trigger with [ACTIVATE:AGENT_SELECTOR_V1] after Phase 5 completion to populate agentConfig.

Frequently Asked Questions about agent-selector

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

FAQPage Schema

How do I automate agent selection based on my project's tech stack?▼

Agent selection automates mapping your PRD's technical architecture—languages, frameworks, databases, and infrastructure—to specialized agents. Trigger the Skill after Phase 5 task decomposition to generate agent-config.json and populate your .claude/agents/ directory with matched configurations.

What information from my PRD does agent selection require?▼

Agent selection reads PRD Section 8 Technical Architecture to extract your tech stack details. It analyzes languages, frameworks, databases, infrastructure components, plus security and scalability requirements to map each to appropriate agents.

Can agent selection handle security and scaling requirements?▼

Yes. Agent selection evaluates security and scalability demands from your PRD and selects auditor and scale-focused agents accordingly. The generated config reflects both functional requirements and non-functional constraints.

What does agent selection output after running?▼

Agent selection generates two outputs: .claude/agent-config.json with local and upstream agent strategy, and a populated .claude/agents/ directory with agent configurations ready for Phase 6 specification generation.

When should I run agent selection in my workflow?▼

Run agent selection after Phase 5 task decomposition completes and before Phase 6 specification generation starts. Activate with [ACTIVATE:AGENT_SELECTOR_V1] to enforce phase-gate sequencing and deployment readiness.

Does agent selection work with any tech stack?▼

Agent selection works with tech stacks defined in your PRD's technical architecture section. It maps common languages, frameworks, databases, and infrastructure types to agents; the explicit tech-stack mapping in your repository determines supported combinations.