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.
Plan a feature across database, API, and UI. Feature description and acceptance criteria: [FEATURE_AND_CRITERIA]. Stack: [STACK]. Existing architecture notes: [ARCHITECTURE_NOTES]. Team and deadline: [TEAM_AND_DEADLINE]. Non-functional needs (performance, security, accessibility, privacy): [NON_FUNCTIONAL_NEEDS]. Return tables: 1. Slices: Slice | User-visible outcome | Layers touched | Depends on | Estimate in days | Risk. Cut the feature into thin vertical slices that can ship independently, starting with the smallest valuable one. 2. Data changes: Table or collection | Change | Migration approach (backward compatible, expand then contract) | Rollback. 3. API changes: Endpoint | Request and response | Auth | Validation | Error cases | Versioning. 4. UI changes: Screen or component | States (loading, empty, error, success) | Accessibility notes. 5. Testing: Level | What | Owner. 6. Release: feature flag, staged rollout, monitoring, and a rollback trigger. 7. Risks and open questions. Add a sequence diagram in text and a definition of done. Ask for clarification on any ambiguous acceptance criteria rather than guessing.
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.