Back to library

structured interview kit

Creates a source-linked structured interview kit deliverable using concrete fields, rules, exceptions, and review controls. Use for competency, behavioral question, probe, score anchor, reconciliation, quality review, or operational reporting.

by adlass TemplatesVersion 1Uses adlass toolsUniversal

Published Aug 21, 2026 · Updated Aug 26, 2026

Helpful · 0View raw SKILL.md

Requirements

Add the process policy and field mapping for competency, question_id, probe. Define thresholds, statuses, owners, and source precedence for evidence_anchor, round_owner, score.

Skill document

The full SKILL.md your agent reads and follows.

structured interview kit

Purpose

This process converts its named business evidence into a traceable deliverable. It keeps source facts, calculations, decisions, and unresolved questions separate so a reviewer can verify the work without guessing. The working vocabulary is competency, behavioral question, probe, score anchor, panel round, debrief, and those fields must appear where applicable.

Scope

Assess only the records and documents relevant to this process. Preserve identifiers, dates, amounts, statuses, and source wording. Excluded: external communication, source-system changes, approvals, and conclusions unsupported by the corpus. For this template, use competency, behavioral question, probe, score anchor, panel round, debrief. This process-specific vocabulary is part of the acceptance check.

Data basis

  • The process-specific records named in the run scope.
  • The reference policy, schema, rubric, or calendar that defines allowed values.
  • Prior-period or comparison data only when it is explicitly in scope.
  • Run inputs for the reporting period, audience, threshold, or output convention. For this template, use competency, behavioral question, probe, score anchor, panel round, debrief. This process-specific vocabulary is part of the acceptance check.

Result

Produce the declared primary document or sheet with row-level evidence, calculated fields, exception status, and a concise summary. Every recommendation remains visibly distinct from a source fact. For this template, use competency, behavioral question, probe, score anchor, panel round, debrief. This process-specific vocabulary is part of the acceptance check.

Quality criteria

  • Every material finding cites a document, section, page, table, row, or field.
  • Counts, totals, dates, and comparisons reconcile to their source population.
  • Missing, conflicting, and inferred values are labelled rather than silently completed.
  • The output uses the process vocabulary and allowed status values from the reference material.
  • The final limitations section states what was not assessed. For this template, use competency, behavioral question, probe, score anchor, panel round, debrief. This process-specific vocabulary is part of the acceptance check.

Instructions

Use the most authoritative supplied source and retain competing values when sources disagree. Apply the stated rule before general judgement. Do not invent thresholds, owners, dates, approvals, rates, scores, or commitments. Keep original values beside normalized values. For each exception, state its affected record, impact, evidence, and current status. A derived value must show its formula or counting rule. Keep the main result concise and place row-level detail in the supporting output. For this template, use competency, behavioral question, probe, score anchor, panel round, debrief. This process-specific vocabulary is part of the acceptance check.

Adapt before use

  • Add the company reference policy, schema, rubric, or process playbook.
  • Map the named fields to the company tables and define source precedence.
  • Set reporting period, threshold, status vocabulary, owners, and escalation roles. For this template, use competency, behavioral question, probe, score anchor, panel round, debrief. This process-specific vocabulary is part of the acceptance check.

Related skills

  • Change request assessment

    Assesses a project change request against the approved baseline and produces a traceable impact analysis for scope, schedule, cost, quality, risk, resources, and dependencies. Use for change control boards, project governance, variation requests, scope changes, and decision papers.

  • Construction change-order pack

    Builds a documented construction variation package from the change trigger, contract terms, quantities, rates, and time effects. Use for change orders, variation claims, owner instructions, design changes, and subcontractor pricing review.

  • executive document brief

    Creates a source-linked executive document brief deliverable using concrete fields, rules, exceptions, and review controls. Use for decision question, board memo, actual, forecast, reconciliation, quality review, or operational reporting.

  • hr record data quality

    Creates a source-linked hr record data quality deliverable using concrete fields, rules, exceptions, and review controls. Use for employee_id, hire_date, manager_id, duplicate, reconciliation, quality review, or operational reporting.