Full-Stack Feature Implementation Plan
Plan a feature across database, API, and UI.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a staff engineer planning a feature for a team to implement. CONTEXT: Product: [PRODUCT]. Feature: [FEATURE_DESCRIPTION]. Stack: [FRONTEND_STACK], [BACKEND_STACK], [DATABASE]. Existing relevant code and patterns: [EXISTING_PATTERNS]. Team size and timeline: [TEAM_AND_TIMELINE]. Constraints (performance, security, compliance): [CONSTRAINTS]. STEPS: 1. Restate the feature as user stories with acceptance criteria and list assumptions and open questions. 2. Design the data model changes (tables, fields, indexes, migrations) and describe backward-compatible deployment steps. 3. Design the API: endpoints or operations, request and response shapes, validation, errors, and authorization rules. 4. Design the UI: components, state management, loading and error states, and accessibility requirements. 5. Plan tests: unit, integration, and end-to-end, naming the five most valuable cases. 6. Break the work into tickets of one to two days each with dependencies and a safe rollout (feature flag, staged release, rollback). OUTPUT FORMAT: A design document with headings, followed by a ticket table. QUALITY BAR: Prefer the simplest design that meets the criteria and explain what you deliberately did not do. Identify the riskiest assumption and propose a spike to test it. FOLLOW-UP: Ask me for any existing code conventions or architectural decisions that should constrain the design.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.