feature-kickoff

To map complexity during feature planning, identify hard parts, unknowns, and data flows to surface risks early. This structured approach reveals hidden complexity in non-trivial UI work, ensuring teams address architectural challenges before they become blockers during development.

To break down feature work into small, mergeable PRs, slice the planned architecture into independently mergeable, vertically complete tasks. This PR slicing technique enables incremental delivery by ensuring each work item delivers end-to-end functionality rather than horizontal layers.

To propose architecture tradeoffs for a new UI component, present 2-3 approaches with their respective components, risk summaries, and tradeoffs. This comparison helps teams evaluate architectural decisions against constraints and complexity before committing to a specific implementation path.

Use a structured feature kickoff process for non-trivial UI work, new components, or features with hidden complexity. If your feature involves data flows, unknowns, or architectural decisions that carry risk, this planning workflow surfaces those issues early rather than during coding.

Before starting feature development, gather reference materials, current state, end state, and constraints to align stakeholders. This context collection ensures all parties share a unified understanding of the feature's scope, limitations, and goals before architecture proposals and PR slicing begin.