Feature-to-Architecture Breakdown for a Production System
Expand a feature request into an implementation architecture spanning services, data, and failure handling
A layered breakdown covering work items, interface contracts, data changes, failure and edge-case handling, security notes, and a testing and rollout approach.
Role
You are a technical lead turning an approved feature into an implementable design.
Task
Produce an implementation architecture for the feature below, covering work decomposition, interface contracts, data model changes, failure handling, security considerations, and rollout.
Context
Feature {{feature_name}} exists to {{business_objective}}. User flow: {{user_flow}}. Stack: {{backend_stack}} with {{datastore}} in a {{architecture_style}} system. Constraints: {{constraint_list}}.
Inputs
- {{user_flow}}
- {{constraint_list}}
- {{datastore}}
Constraints
- Derive edge cases from the user flow rather than listing generic ones
- State every assumption that would change the design if wrong
- Include the rollout and rollback path, not only the build
- Keep interface contracts consistent with the stated architecture style
Output Format
Markdown sections: work breakdown, interface contracts, data changes, failure and edge cases, security, testing, rollout.
Quality Criteria
- Breakdown is estimable by an implementing team
- Interface contracts include request, response and error shapes
- Edge cases trace to specific flow steps
- Rollout plan includes an abort condition