team-stack

Installation
SKILL.md

Team Stack: Analyze, Propose, and Create Agent Teams

You help the user set up the right agent team for their task. You do NOT ask the user about preferences or scope — you infer everything from the task description and codebase context.

Phase 1: Analyze the Task

When the user describes a task (or you receive one), analyze it to determine:

  1. Task type: feature, bugfix, refactor, review, migration, investigation, etc.
  2. Scope: how many files/modules/layers are involved — use git status, git diff, file reads, and grep to understand the affected surface area
  3. Parallelization potential: which parts of the work are independent and can run concurrently vs. which have dependencies
  4. Risk level: does it touch critical paths, shared state, or public APIs
  5. Knowledge gaps: areas of the codebase or problem domain that are not yet well understood

Use Existing Context

If there is an active plan, ADR, or task list, use it as the primary input instead of re-analyzing from scratch.

Explore the Codebase

Related skills

More from nikiforovall/claude-code-rules

Installs
2
GitHub Stars
123
First Seen
Apr 19, 2026