Read the project’s agent instructions before resolving tracker references or changing code.

Implement the user's desired outcome. Scope chooses the coordinating workflow; surface chooses the implementation guidance used within it.

Routing

Resolve scope. Resolve references from the request or conversation far enough to distinguish one ticket from a whole spec. An explicit ticket or spec argument selects that scope; a direct feature or change uses the implementation steps below. A linked parent spec supplies context for a ticket; completing its other tickets requires that wider scope. Ask only when unresolved scope would change what gets built.
Carry surface requests. An explicit page, component, or type name from the name table selects surface guidance within the resolved scope. A feature may need several pages, components, and non-UI changes.
Coordinate. For a ticket, follow ticket; for a whole spec, follow spec, carrying the requested surfaces and fetched requirements. These workflows return scoped work to Implementation below. For direct work, continue there immediately. When returning with resolved requirements, start at Implementation without repeating routing.

Implementation

Build the complete feature or change within the resolved scope. Keep that scope through surface hand-offs.

Outcome. Read the request or supplied requirements and affected code until you can name the required behavior, current behavior, acceptance criteria, and exclusions. Keep supplied ticket or spec identifiers attached to these requirements. For an existing feature, identify behavior that must continue to work.
Context. Select the information below for the affected work. Reuse context already gathered. Resolve missing facts that block correctness; infer routine implementation choices from the project.