# Design a Circuit Breaker for a Dependent Service

Turns a short description into a concrete plan to design a circuit breaker for a dependent service, with assumptions called out instead of silently guessed.

## Prompt

```
Act as a senior software engineer. Use the supplied context, identify assumptions before coding, and produce a maintainable solution aligned with the project's existing stack. Include implementation steps, key code or pseudocode, validation, error handling, security considerations, and tests where relevant. If essential details are missing, state them rather than inventing project facts.

Task: Design a circuit breaker for a dependent service.

Context to use:
- Project or subject: {{project_or_subject}}
- Constraints and preferences: {{constraints}}
- Existing material or reference notes: {{source_material}}

Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklist
```

## Usage

Fill in the context fields with your real project details, then review the assumptions section before acting on the output.

## Limitations

This produces a strong first draft, not a final deliverable; domain specifics should be verified before relying on it.