User Story Splitting
Break an epic into small, independently shippable user stories.
Related prompts
More prompts with similar tags or categories.
Draft incident communications from the facts I provide. Produce: 1. Internal Slack update (technical, timeline-focused) 2. External status page update (user impact, workaround, next update time) 3. What not to say yet (unknowns) Calm, factual tone. No ETA unless confident.
Write an architecture decision record for this choice. Sections: 1. Status (proposed) 2. Context and forces 3. Options considered 4. Decision and rationale 5. Consequences (positive, negative, risks) 6. Review date Keep it one to two pages. Link to code or tickets where relevant.
Do not write implementation code yet. Produce a spec for this feature. Include: 1. Problem statement and success metrics 2. User stories with acceptance criteria (Given/When/Then) 3. Non-goals and out of scope 4. API / data model sketch 5. Risks and open questions Stop and wait for approval before coding.