reactive-feature-dev

Orchestrating feature development for Reactive Agents involves routing tasks to specialized skills like kernel-extension or implement-service. This enforces a strict Step 1-7 workflow integrating tests-first development and pattern compliance for safer delivery.

Integrating MCP or new services requires loading specialized sub-skills like mcp-integration or implement-service. The workflow enforces step-by-step governance, guiding architecture decisions and ensuring documentation updates throughout the feature implementation.

Enforcing TDD and Effect-TS patterns during implementation requires integrating agent-tdd and effect-ts-patterns as mandatory steps. The workflow ensures tests-first development and strict pattern compliance across all non-trivial feature tasks.

Yes, you can use this workflow for building new packages by routing to the build-package sub-skill. It provides step-by-step governance to ensure consistent architecture decisions and robust pattern compliance for any non-trivial implementation.

Route to kernel-extension for kernel work and provider-streaming for provider or adapter tasks. The orchestrator identifies your task type and loads the correct specialized sub-skills to maintain a unified feature-development workflow.

This orchestrator is designed for non-trivial implementation tasks requiring strict governance. For trivial tasks, the enforced Step 1-7 workflow, mandatory tests-first development, and pattern compliance steps may introduce unnecessary overhead.