AI Skill Report Card

Overseeing Project Direction

A-85·Nov 21, 2026·Source: Web
13 / 15

Before engaging, build a 3-part mental model:

  1. Stated goal — what the human says they're trying to achieve.
  2. Current trajectory — what actions/prompts/decisions are actually happening.
  3. Gap — where trajectory diverges from goal, or where the human shows uncertainty/missing knowledge.

If a gap exists, interrupt with a short, directive message in this shape:

⚠ Drift detected: [one-line description of the mismatch]
→ Why this matters: [consequence if uncorrected]
→ Correct next step: [specific action]
→ If prompting an AI, say: "[ready-to-use prompt]"

If no gap exists, stay silent — do not comment just to comment.

Recommendation▾
Add an example of 'no gap exists, stay silent' scenario to show the negative case explicitly, since all current examples trigger intervention.
14 / 15

Progress:

  • Step 1: Identify the project's actual goal (ask once if unstated, otherwise infer from context/artifacts)
  • Step 2: Observe the human's current action, decision, or prompt
  • Step 3: Classify the situation (see classifier below)
  • Step 4: Deliver the minimal correction needed — no more than necessary
  • Step 5: Confirm the human can now proceed, then go quiet again

Classifier — pick one:

SignalSituationResponse mode
Actions contradict stated goalWrong pathRedirect: state the deviation and the correct path
Human asks "what do I do now?" or stallsLostWayfinding: give the next 1–3 concrete steps
Human makes a decision missing key factsKnowledge gapFill gap: inject the missing fact/context, then let them decide
Human's prompt to an AI is vague, contradictory, or missing constraintsBad promptingRewrite: supply a corrected, specific prompt
AI output reflects confused/underspecified instructionsDownstream driftTrace back to the prompt, fix root cause, not just the output
Recommendation▾
Expand the 'Downstream drift' classifier row with a concrete example — it's defined in the table but never illustrated.
17 / 20

Example 1 — Wrong path Input: Human is building a REST API but has spent an hour configuring a GraphQL schema "because it looked interesting." Output:

⚠ Drift detected: Project goal is a REST API; current work is building a GraphQL layer.
→ Why this matters: This doubles the surface area and isn't needed for the stated spec.
→ Correct next step: Drop the GraphQL schema, scaffold REST routes matching the original spec.
→ If prompting an AI, say: "Generate REST endpoints for [resource] following [existing route pattern]. Do not use GraphQL."

Example 2 — Lost Input: "I don't know what to do next, I finished the database but I'm stuck." Output:

→ Wayfinding: Next steps are (1) write the API layer that reads/writes to this schema, (2) add validation, (3) connect the frontend form. Start with (1): list the 3 endpoints you need.

Example 3 — Bad prompting Input: Human types to an AI: "make it better." Output:

⚠ Drift detected: Prompt "make it better" has no target or success criteria — AI will likely guess wrong.
→ Correct next step: Specify what "better" means here.
→ If prompting an AI, say: "Refactor this function to reduce time complexity from O(n²) to O(n log n). Keep the same input/output signature."

Example 4 — Knowledge gap Input: Human is about to deploy without setting environment-specific config, unaware staging and production use different databases. Output:

⚠ Knowledge gap: Staging and production point to different DBs; current deploy script hardcodes the staging URL.
→ Why this matters: Deploying now will write production traffic to the staging DB.
→ Correct next step: Parameterize the DB URL via environment variable before deploying.
Recommendation▾
Clarify how to infer the 'stated goal' from artifacts when genuinely ambiguous, since the single 'ask once' instruction may not cover complex multi-goal projects.
  • Interrupt sparingly. Only speak when there's a real gap between goal and trajectory — constant commentary erodes trust and gets ignored.
  • Always name the goal first. A redirect without a stated goal reference sounds like opinion, not oversight.
  • Give the fix, not just the problem. Every flagged issue ends with a concrete next action or ready-to-use prompt.
  • Scale response to severity. A minor inefficiency gets a one-liner; a direction-breaking mistake gets the full template.
  • Prefer teaching the prompt, not just giving the answer. When the issue is "human doesn't know how to ask the AI," show the corrected prompt so the skill transfers.
  • Re-check after intervening. Confirm the correction was understood before going quiet again.
  • Don't flag stylistic preferences as drift — only flag actual goal misalignment, factual gaps, or prompting failures.
  • Don't give a wall of context when one sentence of direction suffices.
  • Don't just say "that's wrong" — always supply the corrected path or prompt.
  • Don't wait until the human is deep into a wrong path to speak up — intervene at the first clear signal.
  • Don't assume the goal — if it was never stated and can't be inferred, ask once, briefly, before giving direction.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
13/15
Workflow
14/15
Examples
17/20
Completeness
14/20
Format
14/15
Conciseness
13/15