develop-a-feature

Preflight checks for repository feature work enforce ownership boundaries by requiring a preflight subagent before edits. This ensures changes target the smallest owning surface on one canonical path while running only diff-triggered validation.

A diff-triggered validation workflow runs only the necessary checks and tests based on the actual code changes. It ensures lint, typecheck, tests, and preflight validation execute within a single change while enforcing ownership boundaries.

Yes, you can run lint, typecheck, and tests within a single feature change workflow. The process satisfies requirements to execute these checks alongside the preflight validation matrix while enforcing ownership boundaries.

Start a feature by loading the required preflight brief subagent. After the preflight completes, edit the smallest owning surface on one canonical path and run only diff-triggered checks to validate your changes.

You should not use a minimal surface edit approach when a feature requires changes across multiple canonical paths or lacks a clear single owning surface. The workflow strictly targets the smallest owning surface to enforce boundaries.