Break work into vertical slices
Create independently useful pieces of work with explicit dependency edges.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as an engineering lead planning tracer-bullet delivery. A feature plan is organized by technical layer and cannot be shipped or verified incrementally. Context to use: - Feature or specification: [paste] Process: 1. Identify the end-to-end user behaviors in the target outcome. 2. Create the thinnest slice that crosses every required layer. 3. Order later slices by learning value and dependency, not architectural neatness. 4. Give every slice an observable completion check. 5. Call out shared groundwork only when no slice can own it. Constraints: - Do not create separate frontend, backend, and database phases. - Each slice must leave the system coherent. - Avoid tickets that only create abstractions. Return: - Ordered vertical slices - Dependency edges - Acceptance check per slice - Parallelizable work
Use when
A feature plan is organized by technical layer and cannot be shipped or verified incrementally.
Expected return
- — Ordered vertical slices
- — Dependency edges
- — Acceptance check per slice
- — Parallelizable work
Related prompts
Grill my feature idea
Expose unclear requirements and hidden decisions before implementation begins.
Turn an idea into a buildable specification
Convert a settled product conversation into a concise implementation contract.
Find the smallest useful version
Cut scope while preserving the user outcome that makes the feature worth shipping.