team-feature

Coordinate cross-functional teams through decision gates for feature delivery.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill team-feature-tranhieutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-feature
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/team-feature
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill team-feature-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents fragmented feature delivery by orchestrating every specialist from product through QA so the user story never skips a handoff.

Core Features & Use Cases

  • Decision-gated pipeline: Uses Task-based subagents and AskUserQuestion approvals at each phase transition to keep the team aligned and let the user choose proposals.
  • Parallel workstreams: Launches UX design and backend API planning in parallel while still respecting the dependency on approved specs.
  • End-to-end oversight: Covers spec writing, design validation, implementation, QA reporting, documentation updates, and final handoff so releases stay coordinated.

Quick Start

Ask the team-feature skill to orchestrate a feature by describing the user story, scope, acceptance criteria, and desired success metrics so each specialist can begin.

Frequently Asked Questions about team-feature

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

FAQPage Schema
How do I coordinate cross-functional teams for feature delivery without skipping handoffs?

You manage cross-functional feature delivery by orchestrating product, design, engineering, and QA efforts through decision gates. Task-based subagents capture each specialist's output, preventing skipped handoffs during complex implementations.

What is the best way to run parallel workstreams for UX design and backend API planning?

Parallel workstreams for UX design and backend API planning are launched simultaneously while respecting dependencies on approved specs. This ensures both design and engineering tracks progress concurrently without blocking the overall feature pipeline.

How do I enforce approvals during phase transitions in a feature team workflow?

Approvals during phase transitions are enforced using AskUserQuestion prompts at each decision gate. This requires explicit user approval of proposals before downstream tasks begin, keeping cross-functional teams aligned.

Does this feature orchestration approach cover end-to-end release from spec writing to handoff?

Yes, end-to-end feature orchestration covers spec writing, design validation, implementation, QA reporting, documentation updates, and final release handoff. This ensures complex features remain coordinated across all functional roles from start to finish.

What information do I need to provide to start orchestrating a complex feature?

To start orchestrating a complex feature, you provide the user story, scope, acceptance criteria, and desired success metrics. This input allows each specialist subagent to understand dependencies and begin processing their respective tasks.