documentation
Example prompts
Questions and tasks that work well, and the tools a client uses to answer them.
The model chooses the tools; these examples show what to expect.
Traceability
Section titled “Traceability”| Prompt | Tools |
|---|---|
| Which requirements in PRJ have no verifying test case? | bloom_traceability_coverage_gaps |
| What is affected if PRJ-REQ-001 changes? | bloom_traceability_impact |
| Show the traceability matrix for project PRJ. | bloom_traceability_matrix |
| Link test case PRJ-TC-004 to requirement PRJ-REQ-004 as verifies. | bloom_links_create |
Test results
Section titled “Test results”| Prompt | Tools |
|---|---|
| How did our runs go in the last 30 days? | bud_runs_stats |
| Which assertions failed in the latest Checkout API run? | bud_runs_list, bud_results_list_for_run |
| Show the log of run 7’s first artifact. | bud_runs_artifacts, bud_artifacts_get_content |
| Which Test Stations are online? | bud_runners_status |
| Queue the safety tests on a station that ran them before. | bud_catalog_list, bud_runs_trigger_custom |
Authoring
Section titled “Authoring”| Prompt | Tools |
|---|---|
| Draft a requirement for checkout latency under 300 ms. | bloom_requirements_create |
| Add a section on heartbeat timeouts to PRJ-SPEC-001. | bloom_documents_list, bloom_document_sections_create |
| Request review of PRJ-REQ-009 from the assigned reviewer. | bloom_workflow_get, bloom_workflow_request |
Reviews and approvals themselves are recorded in the Bloom web app; no tool signs off a document.