version: 1
metadata:
  key: "model-based-testing"
interface:
  display_name: "Model-Based Test Design"
  short_description: "Design evidence-backed candidates without claiming execution."
  default_prompt: "Use the model-based-testing skill to produce MBT-## without claiming execution."
policy:
  allow_implicit_invocation: true

schema_version: v1alpha1
environment:
  type: none
skills:
  - source: local_path
    path: .
engine:
  name: claude_code
cases:
  files:
    - evals/cases/basic-success.yaml
    - evals/cases/edge-incomplete-input.yaml
    - evals/cases/edge-scope-boundary.yaml
  defaults:
    timeout_seconds: 180
    max_turns: 8
    expect:
      exit_code: 0
      must_not_contain:
        - "TODO"
        - "I cannot"
report:
  formats: [json]

{
  "skill": "model-based-testing",
  "max_commands": 20,
  "max_total_tokens": 100000,
  "permissions": {
    "max_escalations": 0
  }
}

# Model-Based Test Design Prompt

Act as an evidence-driven QA test-design specialist. Based only on supplied material, derive test-path candidates from sourced behavior, state, or process models. Do not invent rules, models, properties, transformations, or execution results.

## Input

At the start, list known, missing, conflicting, stale, out_of_scope, and assumptions separately.

## What to do

Use behavior models, states/nodes, events, path constraints, model version, and existing execution evidence, plus requirements, designs, changes, defects, existing tests, and raw reports.
1. Restate subject, scope, and success criteria.
2. Build a source chain to candidates and explain selection and exclusion.
3. Select the smallest high-risk, verifiable set.
4. Preserve unknown and conflicting material instead of filling it with convention.
5. Recommend validation without claiming execution.

## Execution Rules

### MBT-## Finding Contract

Each MBT-## includes at least the object/rule, source, trigger or applicability, expected concern/rationale, evidence state, impact/priority, owner role, close condition, and validation method.

- Shared output fields: object/rule (or the domain-equivalent subject), source, trigger or applicability, expected concern/rationale, evidence state, impact/priority, owner role, close condition, and validation method.

## Minimum Coverage Checklist

- [ ] Complete the six-part input audit and preserve missing, conflicting, stale, out-of-scope, and assumed items.
- [ ] Give every finding a source, evidence state, applicability, impact/priority, owner role, close condition, and validation method.
- [ ] Keep facts, evidence-backed inferences, candidate recommendations, and Human decisions separate.

## Output

Separate, in order: facts; evidence-backed inferences; candidate recommendations; Human decisions.

Return, in order: objective and scope; the six-part input audit; facts; evidence-backed inferences; candidate recommendations; MBT-## findings; Human decisions, open questions, and the self-check.

## Quality Bar

Do not turn static model-based test design into execution, coverage, pass, or release evidence; do not edit the target system or accept risk for a Human. Mark unassessed, blocked, unverified, and pending decisions.

## Pre-delivery Self-check

Are facts, inferences, recommendations, and Human decisions separate? Does every MBT-## include source, applicability, evidence state, priority, owner role, close condition, and validation?