This is a fine approach at first but it is crucial that the person using this technique understands when it’s a good time to introduce real actions and reducer composition. It does not mean adding action creators but it means separating “what happened” (e.g. SAVE_DRAFT) from “what updated in response” (e.g. state.title).
Most often people associated boilerplate with action creators. That’s the part I recommend omitting until you need it. It’s surprising how often people don’t realize action creators are not an inherent part of Redux.