Spec Before Code

Write a short spec with acceptance criteria before implementation.

Prompt

Copy the prompt, then replace the placeholders with your own context.

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.

Related prompts

More prompts with similar tags or categories.

Business

Any model

User Story Splitting

Break an epic into small, independently shippable user stories.

206 copies

Split this epic into user stories small enough for a 1–3 day PR each. Each story needs: - Title - Acceptance criteria - Dependencies noted - MVP vs follow-up label Vertical slices over horizontal layers. First story should demo something user-visible.

agile

planning

by prompts!

View

Research

Claude

Literature Summary for Decision

Summarize approaches from docs and threads to inform an architecture decision.

143 copies

Summarize research to inform a decision on [topic]. Include: - Common approaches and when each fits - Tradeoffs (complexity, cost, operability) - What our codebase already assumes - Recommendation with reversible vs one-way door flagged Link to official docs where possible. Mark uncertain claims.

research

architecture

by prompts!

View

Research

Any model

Root Cause — Five Whys

Walk from incident symptom to systemic fix with the five whys.

154 copies

Analyze this incident using five whys. Output: 1. Timeline of events 2. Five whys chain from symptom to root cause 3. Contributing factors (not just one root) 4. Corrective actions (immediate vs systemic) 5. What we should monitor to detect recurrence Blameless tone. Focus on process and systems.

incident

postmortem

by prompts!

View