evolutionary-design

Incremental feature planning uses a constraint-driven approach to start with a minimal, end-to-end slice before expanding. This reduces risk and rework by ensuring a single working capability is completed first.

A thin slice approach builds one end-to-end minimal capability before adding subsequent features. It provides a formal constraint block to guide planning sessions, ensuring the foundational design satisfies core requirements first.

You generate a constraint block by applying a frontmatter-driven description to guide implementation. Paste the generated block into the session's context section to direct the planning logic for your feature integration.

Evolutionary design works for API and module integrations by applying a repeatable constraint-driven approach. It ensures you build a minimal end-to-end integration slice before expanding into broader feature sets.

Incremental design planning may not suit projects requiring comprehensive upfront architecture rather than iterative expansion. It focuses on building minimal end-to-end slices, which might constrain contexts needing immediate full-scale feature delivery.