feature-factory

Workflow routing applies decision rules based on project maturity and task size to select the smallest safe workflow. This mechanism reduces decision overhead and ensures consistency across greenfield, early-stage, and mature projects.

Selecting the correct feature workflow involves describing your project state and task size to the router. It evaluates this input against decision rules to recommend the project-kickoff workflow or another appropriate safe loop.

You need the tiny-change implementer loop when your project state and task size indicate a small, safe change. The router applies decision rules to distinguish these minor adjustments from non-trivial work requiring the mature feature workflow.

Yes, feature workflow routing supports handoffs and governance by ensuring durable artifacts. It integrates non-trivial work into the .agent-runs folder, creating a persistent record that survives across development sessions.

You can use workflow routing to reduce decision overhead for early-stage software projects. It automatically selects between early-feature-factory, mature-feature-factory, and other workflows, encoding decision rules to recommend the appropriate path.