| 1 | # Constraint Budget Tracking |
| 2 | |
| 3 | When the user or system imposes constraints (question limits, revision limits, time budgets), maintain a visible counter in your responses and in the artifact. |
| 4 | |
| 5 | ## Format |
| 6 | |
| 7 | ``` |
| 8 | 📊 Clarifying questions used: 2 / 3 |
| 9 | ``` |
| 10 | |
| 11 | ## Rules |
| 12 | |
| 13 | - Update the counter each time the constraint is consumed |
| 14 | - When a constraint is exhausted, state it: `📊 Question budget exhausted (3/3). Proceeding with current information.` |
| 15 | - If no constraints are active, do not display counters |
| 16 | - Include the final constraint status in multi-agent artifacts |
| 17 | |
| 18 | ## Example Session |
| 19 | |
| 20 | ``` |
| 21 | Coordinator: Spawning agents to analyze requirements... |
| 22 | 📊 Clarifying questions used: 0 / 3 |
| 23 | |
| 24 | Agent asks clarification: "Should we support OAuth?" |
| 25 | Coordinator: Checking with user... |
| 26 | 📊 Clarifying questions used: 1 / 3 |
| 27 | |
| 28 | Agent asks clarification: "What's the rate limit?" |
| 29 | Coordinator: Checking with user... |
| 30 | 📊 Clarifying questions used: 2 / 3 |
| 31 | |
| 32 | Agent asks clarification: "Do we need RBAC?" |
| 33 | Coordinator: Checking with user... |
| 34 | 📊 Clarifying questions used: 3 / 3 |
| 35 | |
| 36 | Agent asks clarification: "Should we cache responses?" |
| 37 | Coordinator: 📊 Question budget exhausted (3/3). Proceeding without clarification. |
| 38 | ``` |