Summary

This is an orchestration skill that delegates the end-to-end feature development workflow to other specialized agents (research, planning, implementation, review, commit). It acts as a coordinator that determines project scope, selects which phases to run, and adds security reviewers when needed. The skill is a thin wrapper over a shared `orch-pipeline` engine with custom phase sequencing (0 → 1 → 2 → 4 → 5 → 6, skipping the MVP-only Scaffold phase).

Detected Capabilities

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

Use Cases

• Add a net-new OAuth2 integration to an existing application
• Implement a new payment processor that does not currently exist
• Build a notification system from scratch for an application
• Add a new authentication method (OAuth, SAML, etc.) to an existing codebase
• Coordinate development of a brand-new feature across research, planning, testing, and review phases

Quality Notes

• Skill clearly distinguishes its scope from related skills (orch-fix-defect, orch-change-feature) with explicit criteria
• Phase mask notation (0 → 1 → 2 → 4 → 5 → 6) is precise and well-documented
• Security trigger detection for auth features is explicitly mentioned, improving safety
• Gate checkpoints (Gate 1: plan approval, Gate 2: pre-commit) are clearly documented
• Example demonstrates end-to-end flow with realistic OAuth2 use case
• Documentation assumes reader familiarity with orch-pipeline engine — link provided but no inline explanation of phases
• Does not describe how size classification works (e.g., what criteria determine small vs. standard)