--- title: Here’s How to “Slice” a Redesign the Agentic Way | daily.dev description: A team rebuilding a mobile app's order customization workflow avoided a massive, unwieldy PR by splitting the work into seven vertical slices, each with its... canonical: https://daily.dev/posts/here-s-how-to-slice-a-redesign-the-agentic-way-33abkpp3g twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Here’s How to “Slice” a Redesign the Agentic Way | daily.dev og:description: A team rebuilding a mobile app's order customization workflow avoided a massive, unwieldy PR by splitting the work into seven vertical slices, each with its... og:url: https://daily.dev/posts/here-s-how-to-slice-a-redesign-the-agentic-way-33abkpp3g og:image: https://api.daily.dev/og/posts/33abkpP3G.png og:image:alt: Here’s How to “Slice” a Redesign the Agentic Way og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Here’s How to “Slice” a Redesign the Agentic Way **[Atomic Spin](https://daily.dev/sources/atomicobject)** · 3 min read · 0 upvotes · 0 comments ## Summary A team rebuilding a mobile app's order customization workflow avoided a massive, unwieldy PR by splitting the work into seven vertical slices, each with its own PR that could merge out of order. Three key practices made this work: writing Markdown specs per slice with a 'sequencing note' describing dependencies, predicting merge conflicts in advance and keeping a changelog, and leaving labeled comments in code for handoff points that didn't yet exist. This approach, combined with AI agent assistance, accelerated delivery and simplified testing without requiring sequential merges or painful rebases. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is a sequencing note in a vertical slice spec and why is it useful? A sequencing note is a paragraph in a per-slice Markdown spec that states what the current slice assumes already exists and what to do if it does not. It explicitly names the branch point, identifies any broken behavior that will temporarily exist, and assigns responsibility for fixing it to a specific other slice. This prevents ambiguity when slices are developed in parallel and merged out of order. _Teams shipping features in parallel slices track these coordination patterns on daily.dev._ ### How do you handle merge conflicts when multiple feature branches touch the same file? Predict conflicts before they happen by noting them directly in the slice spec with a single sentence: name both slices that touch the same file and state that whichever lands second rebases. When the first slice merges, the second rebases onto it and the changelog records the event. This gives any developer or AI agent a clear, pre-planned resolution path rather than an unexpected collision. _Developers managing parallel feature branches find conflict-handling strategies like this on daily.dev._ ## Similar posts on daily.dev - [Build Wide, Ship Narrow](https://daily.dev/posts/build-wide-ship-narrow-ubltyfimm) · Hacker News · 0 upvotes · 0 comments - [The one thing every experienced engineer gets wrong](https://daily.dev/posts/the-one-thing-every-experienced-engineer-gets-wrong-qx6sxnvvh) · swizec.com · 35 upvotes · 5 comments - [Designers’ workflow for shipping code](https://daily.dev/posts/designers-workflow-for-shipping-code-cfgb2npmc) · Atlassian · 0 upvotes · 0 comments --- Tags: [#mobile](https://daily.dev/tags/mobile), [#spec-driven-development](https://daily.dev/tags/spec-driven-development) [View this post on daily.dev](https://daily.dev/posts/here-s-how-to-slice-a-redesign-the-agentic-way-33abkpp3g) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Here’s How to “Slice” a Redesign the Agentic Way","url":"https://daily.dev/posts/here-s-how-to-slice-a-redesign-the-agentic-way-33abkpp3g","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/here-s-how-to-slice-a-redesign-the-agentic-way-33abkpp3g"},"datePublished":"2026-08-07T12:08:35.118Z","dateModified":"2026-08-07T12:08:59.354Z","description":"A team rebuilding a mobile app's order customization workflow avoided a massive, unwieldy PR by splitting the work into seven vertical slices, each with its...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d10a0cfacbb01ac9f2b904eecbaf7be1?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d10a0cfacbb01ac9f2b904eecbaf7be1?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Atomic Spin","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Atomic Spin","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/e2af5ce3adaa403a8cf029268b62419f","url":"https://daily.dev/sources/atomicobject"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/here-s-how-to-slice-a-redesign-the-agentic-way-33abkpp3g","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,spec-driven-development","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Atomic Spin","item":"https://daily.dev/sources/atomicobject"},{"@type":"ListItem","position":3,"name":"Here’s How to “Slice” a Redesign the Agentic Way"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/here-s-how-to-slice-a-redesign-the-agentic-way-33abkpp3g#faq","mainEntity":[{"@type":"Question","name":"What is a sequencing note in a vertical slice spec and why is it useful?","acceptedAnswer":{"@type":"Answer","text":"A sequencing note is a paragraph in a per-slice Markdown spec that states what the current slice assumes already exists and what to do if it does not. It explicitly names the branch point, identifies any broken behavior that will temporarily exist, and assigns responsibility for fixing it to a specific other slice. This prevents ambiguity when slices are developed in parallel and merged out of order. Teams shipping features in parallel slices track these coordination patterns on daily.dev."}},{"@type":"Question","name":"How do you handle merge conflicts when multiple feature branches touch the same file?","acceptedAnswer":{"@type":"Answer","text":"Predict conflicts before they happen by noting them directly in the slice spec with a single sentence: name both slices that touch the same file and state that whichever lands second rebases. When the first slice merges, the second rebases onto it and the changelog records the event. This gives any developer or AI agent a clear, pre-planned resolution path rather than an unexpected collision. Developers managing parallel feature branches find conflict-handling strategies like this on daily.dev."}}]} ```