# Quiz Project

> Run an adaptive interview quiz from a Chronicle project using why, what, how, trade-off, failure, performance, and ownership questions. Use when reviewing a project for interviews, practicing follow-up questions, testing whether resume claims can be explained, or running a mock project deep dive.

- Skill: `r-jelly/quiz-project` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add r-jelly/quiz-project`
- Raw SKILL.md: https://api.skillmd.com/api/skills/r-jelly/quiz-project/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: r-jelly (https://skillmd.com/u/r-jelly)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/r-jelly/quiz-project

---


# Quiz Project

Quiz the user from their own project evidence. Let the user answer before
teaching or evaluating.

## Prepare

Resolve `<vault>/chronicle/projects/<project-id>/`. Read:

- `PROJECT.md`, `OWNERSHIP.md`, `DECISIONS.md`, `EVIDENCE.md`, and `STAR.md`;
- relevant session records;
- `QUIZ_HISTORY.md` before choosing a question.

If the project is ambiguous, ask for the project once. If no usable project
record exists, stop and suggest `capture-session` or `update-project`.

Select a question that is not a near-duplicate of recent history. Prefer a weak
area, stale topic, important resume claim, or unresolved decision. Rotate:

- Why: selection criteria, constraints, rejected alternatives, trade-offs;
- What: responsibility, architecture, data flow, interfaces, success criteria;
- How: mechanism, implementation, validation, failure handling;
- Deep dive: performance, cost, scale, security, evaluation, ownership,
  collaboration, failure, or retrospective.

## Run the Quiz

1. Ask one intuition-first main question.
2. Wait for the user's answer. Do not reveal the answer in the question.
3. Ask a focused follow-up when an important claim is vague or unsupported.
4. If the user asks for a hint, give incremental hints:
   - Hint 1: restate the relevant constraint or boundary;
   - Hint 2: identify the concept or comparison axis;
   - Hint 3: outline the reasoning path without giving a polished answer.
5. If the user says they do not know, explain directly from prerequisites to the
   project-specific answer, then ask a short transfer question.
6. Never treat an inferred project claim as the answer key. Call out uncertainty
   in the source record.

In mock-interview mode, use more skeptical follow-ups but remain evidence-based.
Do not manufacture adversarial facts.

## Evaluate

After the answer, provide:

- what was correct and specific;
- what was missing or weak;
- any conflict with the project record;
- a stronger reasoning structure, not a script to memorize;
- one concise example answer only after evaluation.

Score each dimension from 0 to 2:

- factual accuracy;
- why/what/how depth;
- evidence and ownership;
- communication clarity.

Use the score diagnostically, not as a hiring prediction.

## Finish and Record

Continue until the user ends the quiz or the agreed question count is complete.
Only then summarize strengths, recurring gaps, and the next review target.

Append one entry to
`<vault>/chronicle/projects/<project-id>/QUIZ_HISTORY.md` only after the quiz
finishes and the user approves saving. Use
`<plugin-root>/templates/project/QUIZ_HISTORY.md`. Let `<plugin-root>` be
`${CLAUDE_PLUGIN_ROOT}` when Claude Code supplies it; otherwise use the
directory two levels above this `SKILL.md`.

Record the main question, mode, score, strengths, gaps, completed follow-ups, and
next review date. Do not update history for an abandoned question.

Choose the next review interval from the 0–8 total score: 1–3 days for 0–4, one
week for 5–6, and two weeks for 7–8. Shorten it when the answer contradicted a
resume claim or exposed an ownership gap.