| id | SKL-problem-PROBLEMFRAMING |
| name | Problem Framing |
| description | Problem framing is the critical first step before any implementation, teaching agents to detect vague or incomplete requirements, pause execution, and ask clarifying questions. This skill reduces hall |
| version | 1.0.0 |
| status | active |
| owner | @cerebra-team |
| last_updated | 2026-02-22 |
| category | Backend |
| tags | ["api","backend","server","database"] |
| stack | ["Python","Node.js","REST API","GraphQL"] |
| difficulty | Intermediate |
Problem Framing
Skill Profile
(Select at least one profile to enable specific modules)
Overview
Problem framing is the critical first step before any implementation, teaching agents to detect vague or incomplete requirements, pause execution, and ask clarifying questions. This skill reduces hallucinations, prevents wasted effort, and improves first-shot success rate by ensuring the agent understands the problem before attempting to solve it. It provides systematic methods for ambiguity detection, question formulation, and problem restatement to establish clear understanding between humans and AI agents.
Why This Matters
- Increases First-shot Success: Prevents wasted time on incorrect implementations by clarifying requirements upfront
- Reduces Re-work: Saves significant time by avoiding work on misunderstood requirements
- Improves User Satisfaction: Delivers outputs that match actual needs rather than assumptions
- Enhances Communication: Reduces back-and-forth by establishing clear understanding early
- Supports AI-Human Collaboration: Enables more effective collaboration between AI agents and human users
Core Concepts & Rules
1. Core Principles
- Follow established patterns and conventions
- Maintain consistency across codebase
- Document decisions and trade-offs
2. Implementation Guidelines
- Start with the simplest viable solution
- Iterate based on feedback and requirements
- Test thoroughly before deployment
Inputs / Outputs / Contracts
- Inputs:
- User task or request
- Available context (code, files, error messages)
- Previous clarifications or discussions
- Entry Conditions:
- Task received from user
- Initial context available
