devlyn:team-resolve

Orchestrate a cross-functional agent team to investigate and implement fixes.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fysoul17/one-query-v1 --skill devlyn-team-resolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devlyn:team-resolve
Source: https://github.com/fysoul17/one-query-v1/tree/main/onequery/.claude/skills/devlyn%3Ateam-resolve
Command: npx skills add https://github.com/fysoul17/one-query-v1 --skill devlyn-team-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a structured, multi-disciplinary agent team to investigate, reason, and fix complex issues—bridging root-cause analysis and actionable implementations.

Core Features & Use Cases

  • Phase-driven intake, investigation, synthesis, and plan resulting in concrete implementation tasks.
  • Role distribution: Root Cause Analyst, Implementation Planner, Test Engineer, Security Auditor, UX/Product reviewers, and Architecture/Accessibility/Performance considerations as needed.
  • Formal Phase gates (INTAKE, ANALYSIS, SYNTHESIS, PLAN, EXECUTION) with defined deliverables and done criteria.

Quick Start

Spawn a cross-functional agent team, investigate the issue across perspectives, then synthesize a concrete implementation plan.

Frequently Asked Questions about devlyn:team-resolve

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

FAQPage Schema
How do I coordinate a cross-functional agent team for complex bug investigation?

Coordinate a cross-functional agent team by spawning role-based agents that handle intake, investigation, synthesis, and planning phases to resolve complex bugs spanning multiple modules.

What is the best way to perform root-cause analysis across multiple software modules?

Root-cause analysis across multiple modules is best handled by orchestrating specialized roles like a Root Cause Analyst and Implementation Planner to investigate, reason, and synthesize findings into a concrete fix plan.

How does a phase-driven agent team implement bug fixes?

A phase-driven agent team implements bug fixes by progressing through formal gates: INTAKE, ANALYSIS, SYNTHESIS, PLAN, and EXECUTION, ensuring defined deliverables and done criteria are met at each step.

Can I use a multi-perspective agent team for feature implementations requiring diverse expertise?

Yes, you can use a multi-perspective agent team for feature implementations requiring diverse expertise, leveraging roles like Security Auditor, UX/Product reviewers, and Test Engineer to ensure comprehensive coverage.

Does this cross-functional issue resolution approach require specific framework dependencies?

This cross-functional issue resolution approach requires no external dependencies, as it is implemented entirely via the Agent Teams framework to define roles, checklists, and formal done criteria.

When should I not use a multi-agent team for root-cause analysis?

You should avoid using a multi-agent team for root-cause analysis when issues are simple or isolated to a single module, as the formal phase gates and diverse role distribution add unnecessary overhead.