Prompt

Vista previa

# Role
You are a pragmatic security architect who finds exploitable risk without blocking useful shipping. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Turn analytics questions into a decision-grade data product for AI system threat modeling, prompt-injection review, data exposure risk, and incident readiness.

# Inputs
- Project context: an internal agent that can read tickets, GitHub issues, and customer documents
- Target audience: security engineers, platform owners, privacy teams
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: threat model template, SIEM, secret scanner, policy engine
- Constraints: prioritize exploitability; map each risk to a control; respect privacy boundaries
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- data flow diagrams
- tool permissions
- audit logs
- security incidents

# Known risks to control
- prompt injection
- credential leakage
- cross-tenant access
- unreviewed tool writes

# Method
1. Define grain and denominator
2. List confounders and caveats
3. Prioritize actionability over chart volume
4. Write one recommendation with confidence level

# Required output sections
1. Decision to support
2. Metric contract
3. Data sources
4. Analysis method
5. Dashboard layout
6. Decision memo

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

Artefactos

1 artefacto(s)

Example Output: Security Risk Data Product Brief

Inputs used

Project context: an internal agent that can read tickets, GitHub issues, and customer documents
Target audience: security engineers, platform owners, privacy teams
Success metric: activation, quality, and risk reduction
Available tools and data: threat model template, SIEM, secret scanner, policy engine
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

metric contract, analysis plan, dashboard outline, and decision narrative

Decision to support

Use data flow diagrams as evidence, apply the constraint "prioritize exploitability", and explicitly note how the plan reduces prompt injection. The output should be ready for a practitioner to act on without a follow-up explanation.

Metric contract

Define the metric grain before analysis. For an internal agent that can read tickets, GitHub issues, and customer documents, the first dashboard view should show cohort, denominator, time window, and confidence note, not just top-line movement.

Data sources

Rank sources by authority before retrieval. Chunk around task intent rather than page boundaries, and require every answer to cite the exact source segment used for audit logs.

Analysis method

Define the metric grain before analysis. For an internal agent that can read tickets, GitHub issues, and customer documents, the first dashboard view should show cohort, denominator, time window, and confidence note, not just top-line movement.

Dashboard layout

Define the metric grain before analysis. For an internal agent that can read tickets, GitHub issues, and customer documents, the first dashboard view should show cohort, denominator, time window, and confidence note, not just top-line movement.

Decision memo

Use tool permissions as evidence, apply the constraint "respect privacy boundaries", and explicitly note how the plan reduces credential leakage. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on data flow diagrams and tool permissions. Treat prompt injection as the primary launch blocker. The first milestone should prove that the workflow produces a usable risk register, mitigations, and verification checklist with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to AI system threat modeling, prompt-injection review, data exposure risk, and incident readiness.
It includes the required sections: Decision to support, Metric contract, Data sources, Analysis method, Dashboard layout, Decision memo.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: prompt injection.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

Security Risk: Data Product Brief

Use this prompt when you need metric contract, analysis plan, dashboard outline, and decision narrative for AI system threat modeling, prompt-injection review, data exposure risk, and incident readiness.

Best for

security engineers, platform owners, privacy teams
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.