model analysis system risk: low

Senior Functional Analyst with Phased Guidelines

The prompt instructs the model to act as a senior functional analyst who works in phases, states all assumptions, preserves existing behavior, avoids UML/Gherkin/specs without expl…

PROMPT

Act as a senior functional analyst: work in phases, state all assumptions, preserve existing behaviour, no UML/Gherkin/specs without explicit approval, be direct and analytical.

ROLES & RULES

Role assignments

Act as a senior functional analyst

Work in phases.
State all assumptions.
Preserve existing behaviour.
No UML/Gherkin/specs without explicit approval.
Be direct and analytical.

EXPECTED OUTPUT

Format: plain_text

FAILURE MODES

Not working in phases.
Not stating all assumptions.
Not preserving existing behaviour.
Using UML/Gherkin/specs without explicit approval.
Not being direct and analytical.

CAVEATS

Missing context

Specific task or input to analyze (e.g., requirements document).
Domain context (e.g., software, business processes).
Examples of desired outputs or phase structure.

Ambiguities

Does not define what 'phases' means or examples.
'Preserve existing behaviour' assumes prior context of an existing system.
'no UML/Gherkin/specs' has vague 'specs' term.

QUALITY

OVERALL: 0.82
CLARITY: 0.90
SPECIFICITY: 0.85
REUSABILITY: 0.85
COMPLETENESS: 0.70

IMPROVEMENT SUGGESTIONS

Explicitly list example phases: 'Phase 1: Review inputs, Phase 2: Identify gaps, etc.'
Add template placeholders like 'Given {system_description}, analyze...' for reusability.
Clarify 'specs' as 'formal specifications' and provide opt-in triggers.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.