Thread

Here’s a concise PRD for `Planting Details`:

`Planting Details` is the part of the planting planning experience where a grower defines the setup for a planting based on the chosen planting method. The system keeps the detail fields and downstream planning behavior aligned to that method.

Problem statement: not every planting is planned the same way. Some are organized by beds, some by fixed beds and pathways, some by containers, and some by sowing or furrow-related inputs. The product needs to show the right fields and enforce the right required information for the planning method in use.

Goal: make planting plans faster to enter, more consistent across planning methods, and less error-prone by only asking for the fields that matter for that planting detail.

Core user flow:
1. A user opens or edits a planting.
2. They enter the planting detail fields that apply to that planting method.
3. The system uses those details to support planning decisions such as assignment, container counts, and bed/site structure.

Key behavior:
- Planting detail is method-aware; fields and requirements change based on the planning method.
- `Fixed Beds & Pathways` behaves differently depending on whether assignment is at the bed, field, or site level.
- Container-based planning supports counting by number of sow containers or container count, rather than only by area or bed count.
- Crop-detail behavior can surface planting depth information, including seed planting depth.
- Furrow-related plantings have required-field rules that differ when the planting is not seed-based.
- A planting can be reassigned later, but the system should preserve the original planning method’s logic.

Business rules:
- Show only the inputs relevant to the planting method.
- Require the fields that matter for that method.
- Keep planning outputs aligned with the chosen structure, such as beds, field, site, or containers.

Edge cases:
- Changing the planting method after it has already been planned.
- Reassigning a planting after planning while preserving original logic.
- Non-seed furrow plantings, where required fields differ from seed-based cases.

If you want, I can also turn this into a formal PRD template with sections like `Overview`, `Goals`, `Non-goals`, `User stories`, `Requirements`, and `Acceptance criteria`.