Aristoのルーブリック

No discernible outcome.

例: Tell me about marketing.

Topic or activity stated, outcome implicit.

例: Write about our new product.

Outcome stated, no success criteria.

例: Write a launch email for our product.

Outcome plus at least one testable criterion.

例: …that gets existing customers to book a demo; under 150 words.

Outcome, testable criteria, and priority among them when they conflict.

例: …Success = clear single call to action and a demo link above the fold; brevity matters more than covering every feature.

No context at all; the model must guess the situation, the subject and the material.

例: Summarise this.

Situation named in passing; the material or facts the task needs are missing or only alluded to.

例: Summarise the meeting we had about the budget.

The needed material is present but undelimited or incomplete, so the model cannot tell input from instruction.

例: Summarise the meeting notes below for the finance team. Budget review 14 May: Ana raised…

Material is clearly delimited (tags, fences or headings) and the situation is explained; small gaps remain.

例: <notes>…</notes> These are notes from the 14 May budget review; summarise them for the finance team.

Complete and delimited material, background the model could not infer, and a statement of what it does not have.

例: <notes>…</notes> Background: this is the third review this quarter; last time we overspent on travel. Figures for June are not yet available, so do not estimate them.

No reader or purpose can be inferred.

例: Explain photosynthesis.

Reader implied by the topic or the register, but never stated.

例: Explain photosynthesis simply.

Reader named; what they will do with the output is not.

例: Explain photosynthesis to a 12-year-old.

Reader and purpose of use both stated.

例: Explain photosynthesis to a 12-year-old preparing for a science quiz next week.

Reader, purpose and what they already know or need, so the level, emphasis and register follow from it.

例: …for a 12-year-old who has covered cells but not chemistry; she needs to answer short written questions, so favour precise terms over analogies.

No boundaries of any kind.

例: Write a blog post about remote work.

One vague boundary, usually length or tone, nothing on scope or sources.

例: Write a short blog post about remote work.

Several concrete boundaries (length, scope, sources) but silent on what to do when uncertain.

例: …about 600 words, for managers, no product recommendations, cite at least two studies.

Concrete boundaries plus explicit must-nots and an instruction for the uncertain case.

例: …if you cannot find a study published after 2023, say so rather than inventing one.

Boundaries are complete, consistent and prioritised, stated as what to do rather than only what to avoid.

例: …Word count may stretch to 800 if needed to keep both studies; accuracy outranks length; mark any claim you are unsure of with “(verify)”.

No actionable instruction; a topic or a fragment.

例: Customer churn Q3.

One ambiguous instruction, or several tasks tangled together with no order.

例: Look at the churn data and also fix the dashboard and tell me what to do.

A clear single task, or multiple tasks listed but their order or dependencies unstated.

例: Analyse the Q3 churn data and recommend three actions.

Clear, ordered steps or an explicit decomposition; each step has one verb and one object.

例: 1. Compute churn by plan. 2. Identify the plan with the biggest rise. 3. Propose three actions for that plan.

Ordered steps with the reasoning behind them, what to do if a step cannot be completed, and where to stop.

例: …Step 2 matters because we can only fund one intervention. If the data for a plan is missing, skip it and say so. Stop after the three actions; do not draft the rollout plan.

Nothing said about the form of the result.

例: Compare the two proposals.

A single loose hint such as “briefly” or “in a table”.

例: Compare the two proposals in a table.

Format and rough length stated; structure, language or tone left open.

例: Compare the two proposals in a table of at most ten rows, then a one-paragraph recommendation.

Format, structure, length and language or tone all stated and consistent with the goal.

例: …columns: criterion, proposal A, proposal B, winner. Write in Portuguese, neutral tone, no preamble.

A complete contract: schema or template, length, language, tone, and how edge cases appear in the output.

例: …Return JSON {"rows":[{"criterion","a","b","winner"}],"recommendation"}; if a criterion cannot be judged, set winner to "tie" and explain in recommendation.

Examples would clearly help (a specific format, style or classification) but none is given.

例: Classify each support ticket by urgency.

A reference is mentioned but not provided, or one example that is incomplete.

例: Classify each ticket by urgency, like we did last month.

One complete example, or several that all show the same case, so the model may over-fit it.

例: <example>Ticket: “Site down for all users” → urgent</example>

Two to five varied examples in a consistent, delimited format.

例: <examples><example>…→ urgent</example><example>…→ normal</example><example>…→ low</example></examples>

Varied examples that include an edge case or a counter-example, each with a short note on why.

例: …<example>“Invoice typo” → low, because nothing is blocked</example><example>“Cannot log in (one user)” → normal, not urgent: single user</example>

A perspective would change the output and none is given, or the role given contradicts the task.

例: Review this contract clause.

A generic label with no bearing on the output (“you are a helpful assistant”).

例: You are a helpful assistant. Review this contract clause.

A relevant role named, but its perspective is not used in the instructions.

例: You are a commercial lawyer. Review this contract clause.

A role whose expertise shapes the task, plus guidance on voice or stance.

例: As a commercial lawyer acting for the buyer, review this clause and flag risks to the buyer; be direct, no hedging.

Role, stance, voice and the standard to judge by, applied only where it changes the output.

例: …Judge against standard Canadian commercial practice; where the clause is market-standard say so in one line and move on.

Contradictory instructions, or shouting in capitals (“CRITICAL”, “MUST”), or a trick that harms current models (forced step-by-step, prefill-style openings).

例: CRITICAL: you MUST think step by step and NEVER make mistakes. Also be brief but cover everything.

No contradictions, but obsolete tricks or heavy emphasis remain, or long material comes after the question.

例: Think step by step. What are the risks? [20 pages of contract follow]

Plain, calm instructions; structure is weak (no delimiters) or the request ignores the target family’s conventions.

例: Here is the contract and here are my questions, mixed together in one paragraph.

Calm, consistent instructions; long material first and the question last; delimiters or tags separate parts; explains the why where it matters.

例: <contract>…</contract> Review the clause above. Keep the answer short because it goes into a client email.

Everything at 3, written for the chosen model family: structure and emphasis in the vendor’s recommended form, effort left to the model, nothing redundant.

例: Same prompt with <contract> and <questions> tags, a one-line role, no “think carefully” padding, and success criteria the model can check itself.