Technical Spike (Timeboxed)

Explore unknowns in a fixed timebox and report options with a recommendation.

Prompt

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

Run a timeboxed technical spike (assume 2–4 hours of work). Deliverable: 1. Questions we needed to answer 2. What you tried and what you learned 3. Options compared (pros/cons/constraints) 4. Recommendation with confidence level 5. Follow-up tasks if we proceed Do not productionize spike code — prototypes are disposable unless stated otherwise.

Related prompts

More prompts with similar tags or categories.

Business

Claude

RFC / Decision Record

Capture an architecture decision with context, options, and consequences.

174 copies

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.

adr

architecture

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