team-design

Route operator intent to team-design sub-skills and present a unified dashboard.

18|4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/botminter/botminter --skill team-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-design
Source: https://github.com/botminter/botminter/tree/main/profiles/scrum/roles/chief-of-staff/coding-agent/skills/team-design
Command: npx skills add https://github.com/botminter/botminter --skill team-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduce the friction of day-2 team design by triaging broad operator intent, surfacing recent agreements and action items, and routing requests to the precise sub-skill so operators don't have to manually gather context or run multiple commands.

Core Features & Use Cases

  • Intent routing: Classifies operator requests and dispatches to retrospective, role-management, member-tuning, or process-evolution sub-skills.
  • Context gathering: Summarizes recent decisions, norms, and pending retro action items from repository agreements to hand off relevant state to sub-skills.
  • Dashboard & retro-first flow: Presents roles, recent agreements, pending action items, and process summaries; recommends running a retro when scope is broad and routes resulting action items to the correct handlers.
  • Robust handoff: Briefs the operator with findings, uses ralph tools skill load to invoke sub-skills, and prompts for follow-up actions or clarification when needed.

Quick Start

Ask the team-design hub to show the current team overview including roles, recent agreements, and any pending action items.

Frequently Asked Questions about team-design

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

FAQPage Schema
How do I run a team retrospective using existing repository agreements?

The hub triages broad operator intent and summarizes pending retro action items from repository agreements, recommending a retrospective when scope is broad and routing resulting items to correct handlers.

How does intent routing work for day-2 team design operations?

Intent routing for team design classifies operator requests and dispatches them to retrospective, role-management, member-tuning, or process-evolution sub-skills using the ralph tools skill loader.

What do I need to access before managing team roles and process evolution?

Managing team roles and process evolution requires repository access to agreements, role definitions, PROCESS.md, and the ralph tools skill loader to gather context and invoke sub-skills.

Can I view pending action items and recent norms in a single team dashboard?

The unified team design dashboard presents roles, recent agreements, pending action items, and process summaries in a single view to support day-2 team overview and triage scenarios.

What's the best way to handle member tuning across multiple team design sub-skills?

Handling member tuning across sub-skills is best done through the hub's robust handoff, which briefs the operator with context findings and invokes the member-tuning sub-skill via ralph tools skill load.

When should I not use a unified hub for team design triage?

Avoid using the team design hub for operations outside day-2 scope, such as initial team setup, since it specifically triages retrospectives, role management, member tuning, and process evolution.