Skip to main content
Back to Prompt Library
Build the complete application

Implementation brief

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Build an Account Research Briefing Agent

Format
Code-aware
Lines
55
Sections
11
Linked challenge
Build an Account Research Briefing Agent

Prompt source

Original prompt text with formatting preserved for inspection.

55 lines
11 sections
No variables
1 code block
## Who Uses It
An account executive preparing for a first customer meeting.

## What You Will Build
Build an agent that turns company documents and dated announcements into a cited account brief. Separate verified facts from sales hypotheses and let the user inspect evidence before exporting the briefing.

## Inputs
- Company profile
- Dated company documents
- User research questions

## Workflow
1. Retrieve relevant document sections.
2. Resolve dates and conflicting facts.
3. Draft the company summary and evidence-backed meeting questions.
4. Export a briefing with citations and explicitly labeled hypotheses.

## Interface
A research workspace with a source viewer, editable briefing, citations, and document export.

## Working Demo
Create a cited briefing about the planned expansion, identify Person A as current director, and label the automation opportunity as a hypothesis.

## Deliverables
- A working local application with the specified review interface.
- Source code, dependency lockfile, and setup commands.
- A recorded end-to-end demo using the supplied starter data.
- Example outputs, action logs, and automated tests.

## Starter Data
These fictional records are a small development fixture, not a production dataset. Implement the mock services described in the brief.

```json
{
  "company": "Example Support Ltd",
  "as_of": "2026-09-19",
  "documents": [
    {
      "id": "D1",
      "date": "2026-08-01",
      "text": "The company operates two support centers and plans a third."
    },
    {
      "id": "D2",
      "date": "2026-09-01",
      "text": "Person B becomes operations director on October 1. Person A remains director until then."
    }
  ],
  "questions": [
    "What is changing in operations?",
    "Who currently leads operations?"
  ]
}
```

## Constraints
Use the fictional company bundle. Do not send outreach or infer personal characteristics.
Choose an available model that supports your implementation. Record its identifier and version.

## Evaluation
Review the complete application, not only the starter-case answers.
- The expansion claim cites D1.
- The director claim respects the effective date in D2.
- The proposed sales opportunity is not stated as a customer commitment.
Add one normal case, one incomplete-input case, and one failure-recovery case.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Preserve the source structure until you know which part of the prompt is actually driving the result quality.

Tune next

Change domain facts, examples, and tool context first before you rewrite the instruction scaffold.

Verify after

Validate one failure mode at a time so prompt changes stay attributable instead of getting noisy.