intake

Structured intake routes new engineering work by classifying the work type and enforcing a hard gate before any downstream execution. This produces an intake-brief, a phase-recommendation, and a workflow-recommendation to anchor routing and accountability.

A hard gate in intake workflows prevents any downstream execution until an intake decision is explicitly approved. This gatekeeping mechanism enforces observable handoffs and documents routing rationale before teams select workflows.

Generate an intake brief by describing your new feature, migration, or triage scenario to the intake process. It evaluates the request and outputs the brief alongside phase and workflow recommendations to guide next steps.

Yes, the intake routing applies across the entire lifecycle from initial discovery through final workflow selection. It classifies the work type and orchestrates handoffs to the next skill needed for execution.

The best way to document routing rationale is through a controlled intake decision that outputs a structured intake-brief. This enforces accountability and explicitly records the routing path and next skills before handoff.

Downstream work is blocked because the intake process enforces a hard gate that prevents execution until routing is approved. This gatekeeping ensures accountability and observable handoffs before any workflow begins.