feature-development

Coordinate parallel module development with assigned components and a designated integrator.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/labrinyang/team-ochestractor --skill feature-development-labrinyang
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: feature-development
Source: https://github.com/labrinyang/team-ochestractor/tree/main/skills/feature-development
Command: npx skills add https://github.com/labrinyang/team-ochestractor --skill feature-development-labrinyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables parallel module development by allowing teammates to own separate components while maintaining integration through a dedicated integrator and contract-driven workflows.

Core Features & Use Cases

  • Independent module ownership with defined interfaces
  • Parallel implementation followed by integration testing
  • Phase-driven process (Forming, Storming, Performing, Integration, Adjourning)

Quick Start

Assign each feature component to a separate teammate and designate an integrator to ensure cross-module consistency.

Frequently Asked Questions about feature-development

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

FAQPage Schema
How do I coordinate parallel module development across a team?โ–ผ

Parallel module development is coordinated by assigning independent components to teammates while designating an integrator to maintain cross-module consistency through defined interfaces and contract-driven workflows.

What is a contract-driven workflow and when do I need it for feature development?โ–ผ

A contract-driven workflow uses defined interfaces to enable independent module ownership and parallel builds. You need it when feature work can be split into two or more modules requiring eventual integration testing.

What team roles are needed for parallel feature builds?โ–ผ

Parallel feature builds require five specific team roles: coordinator, architect, implementer, reviewer, and integrator, ensuring phase gates are managed and cross-module consistency is maintained.

How do I manage integration testing after independent module implementation?โ–ผ

Integration testing follows a phase-driven process where an assigned integrator checks cross-module consistency after teammates complete independent module implementation, validating that parallel builds merge correctly.

Can I use this approach for features that cannot be split into clear interfaces?โ–ผ

This approach applies to feature work that can be split into two or more modules with clear interfaces. Features lacking clear module boundaries or independent component ownership are not suitable for this contract-driven workflow.

What are the phase gates in a contract-driven feature development process?โ–ผ

The phase gates in contract-driven feature development are Forming, Storming, Performing, Integration, and Adjourning, which structure parallel implementation through to final integration testing.