Prompt Engineering & Structured Output

CCAR-F · 40 questions

• A city PR bot should flag comments only when claimed behavior contradicts the code. Which prompt approach improves precision?
• DevOps adds only-report-high-confidence wording, yet style nits still flood civic repos. What does that show?
• High false-positive style findings drown out real security issues in city DevOps review. What is the main risk?
• The permitting team wants clearer PR-review prompts. Which design best reduces noise?
• One PR-review category floods the clerk portal team with false positives while its prompt is being rewritten. What should they do meantime?
• Fee-logic review severity keeps drifting between reviewers. What prompt design stabilizes classification?
• Permit validators still over-flag after adding a vague be-conservative instruction. Why?
• Ambiguous 311 routing improves after adding a few worked examples showing why one tool was chosen. What technique is that?
• PR review comments for the water-billing service keep changing shape. How can few-shots help?
• Municipal code review false positives drop after examples contrast acceptable city patterns with real defects. What is being taught?
• Permit PDF extraction struggles when citations are inline in some packets and bibliographic in others. What helps?
• Public-health form extraction leaves empty fields on informal measurements and mixed table/narrative layouts. What should be added?
• Detailed instructions for clerk filing extracts still produce inconsistent fields until examples are added. What does that illustrate?
• After adding few-shots, the parcel-form extractor handles novel layouts it never saw verbatim. What capability is that?
• A clerk filing extractor must return schema-compliant JSON reliably. Which approach is preferred?
• With toolchoice set to auto, Claude sometimes chats instead of extracting permit fields. What should the team do for mandatory extraction?
• Required schema fields for optional permit attributes cause fabricated values. How should the schema change?
• Violation categories for code enforcement keep expanding beyond a fixed list. Which enum pattern helps?
• Mixed document batches for the assessor's office need metadata before enrichment. Which toolchoice pattern fits?
• Strict JSON schemas stop malformed fee extracts, yet stated totals still disagree with line items. What limitation remains?
• Scanned utility bills arrive with messy dates and amounts. What should sit beside a strict extraction schema?
• A parcel extract fails schema checks. How should the retry be framed for correction?
• Parcel retries keep failing because the needed grantor name exists only in an external deed not in the packet. What should the architect conclude?
• Code-review false positives keep recurring for the water-billing service. What structured field helps analyze dismissals?
• Fee extracts pass schema checks but stated totals may disagree with line items. What self-correction pattern helps?
• tooluse already blocks invalid JSON shapes, yet an APN lands in the wrong field. What kind of error is that?
• Multi-page permit packets sometimes list conflicting square footage. What structured signal should the extract include?
• Some extract failures are format mismatches; others lack any source for a required field. How should handling differ?
• Overnight permit-packet extraction is latency-tolerant and cost-sensitive. Which API approach fits?
• Pre-merge CI review for the permitting service must finish before merge gates. Why avoid Message Batches there?
• A batch job for assessor PDFs needs mid-request live MCP parcel lookups. What limitation applies?
• Some oversized assessor packets fail in a batch after chunking. How should failures be recovered?
• Thousands of assessor PDFs are queued for extraction. What should happen before the full batch?
• Batches may take up to about 24 hours, but the clerk SLA is 30 hours end-to-end. What must submission cadence account for?
• Generated CI patches for fee logic need a second look. Which review design is stronger?
• A large multi-file civic PR overwhelms a single review pass. What architecture helps?
• Verification passes for permit extracts need to route human review wisely. What should accompany findings?
• Self-review in the fee-logic generator session keeps defending its own choices. What limitation is showing?
• Cross-file data-flow bugs in a housing-authority PR are missed by single-file comments. Where should that analysis live?
• Subtle authorization bugs in a clerk portal patch were missed by the generating session. What often works better?