The garden survived the redevelopment. It moved, briefly, to an indoor atrium, and then back under the city, transplanted with care to a new shelf in the renovated station. The tilework gleamed, and the lights were modern, but the garden continued to collect fragments of people’s lives. A plaque appeared one morning, simple and earnest: In honor of the community who cultivated life in the city’s shadows.
| Question | Why It Helps | |----------|--------------| | (e.g., web app, mobile app, API, game, hardware device, etc.) | Determines the technology stack, user interaction model, and constraints. | | Who is the target user or audience? (e.g., admin users, end‑customers, developers, etc.) | Shapes the UX, permissions, and level of detail needed. | | What problem does the feature aim to solve? (e.g., “users can’t track shipments,” “manual data entry is error‑prone,” etc.) | Gives a clear goal and helps define success criteria. | | Do you have any functional requirements? (e.g., “search by date range,” “export to CSV,” “real‑time notifications”) | Provides the core behavior the feature must exhibit. | | Any non‑functional constraints? (performance, security, accessibility, offline support, etc.) | Influences architecture and implementation choices. | | What technology stack are you using? (e.g., React + Node, Django, Flutter, .NET, Arduino, etc.) | Allows me to suggest concrete code snippets, libraries, or patterns. | | Do you need a high‑level design (user flow, UI mock‑up) or a low‑level implementation (code, database schema, API contract)? | Determines the depth of the deliverable. | | Any existing naming conventions or architecture patterns you follow? (e.g., Clean Architecture, MVC, micro‑services) | Keeps the new feature consistent with the rest of the codebase. | | Deadline or priority level? | Helps gauge how much detail to include now vs. later. | juq016