See What the Standard Expects Before Reviewing

You need to see what the engineering standard expects for a specific role before you review agent-produced work against it.

Prerequisites

Complete the Get Output Review Grounded in the Standard guide first. This page assumes you installed an agent-aligned engineering standard. It also assumes you ran npx fit-pathway job at least once.

Look up the role's skill expectations

Generate the role definition for the discipline and level you review against:

npx fit-pathway job software-engineering J060

The Skill Matrix section lists every skill and the proficiency level the standard expects:

## Skill Matrix

| Skill | Level |
| --- | --- |
| Incident Response | Awareness |
| Planning | Foundational |
| Task Completion | Working |

Each row tells you the proficiency this role expects for this skill. When you review agent output, check the work against the expected proficiency. Do not check it against a higher or lower one.

If the role includes a track specialization, add the --track flag:

npx fit-pathway job software-engineering J060 --track=platform

Track specializations shift expectations. For example, the Platform track for J060 raises Incident Response from Awareness to Foundational. It also adds track-specific responsibilities to the generated description.

Understand what a proficiency level means

The skill name and proficiency level alone may not tell you what to look for in a review. Inspect the skill to see the description for each proficiency level:

npx fit-pathway skill task-completion

# Task Completion

Delivery

Completing work items reliably, from understanding requirements through
implementation to verification.

## Level Descriptions

| Level | Description |
| --- | --- |
| Awareness | You complete well-defined tasks with guidance... |
| Foundational | You break down tasks into steps, estimate effort... |
| Working | You manage your own workload, handle ambiguous requirements... |
| Practitioner | You coordinate task delivery across teams... |
| Expert | You define delivery practices across the organization... |

Find the row that matches the expected proficiency from the Skill Matrix. That description is what the standard considers adequate for this role. Use it as your review benchmark. The work should demonstrate the described actions. The skill name alone is not enough.

Check behaviour expectations

The Behaviour Profile section of the role definition shows expected maturity levels:

npx fit-pathway job software-engineering J060

## Behaviour Profile

| Behaviour | Maturity |
| --- | --- |
| Think in Systems | Practicing |

To see what "Practicing" means for a specific behaviour:

npx fit-pathway behaviour systems-thinking

# Think in Systems

The ability to see beyond individual components to understand how the entire
system behaves...

## Maturity Levels

| Maturity | Description |
| --- | --- |
| Emerging | Recognizes that systems have interconnected parts... |
| Developing | Identifies upstream and downstream impacts... |
| Practicing | Maps complex system interactions across technical and business domains... |
| Role Modeling | Shapes systems design practices across their function... |
| Exemplifying | Defines organizational systems architecture principles... |

The maturity description tells you what the standard expects for approach and reasoning. It covers more than the output. When you review, ask whether the work matches the pattern the maturity level describes.

Read the expectations section

The Expectations section at the top of the role definition describes the scope, autonomy, and complexity the standard defines for this level:

## Expectations

- **Impact Scope**: Features and small projects
- **Autonomy Expectation**: Work independently on familiar problems
- **Influence Scope**: Mentor junior team members
- **Complexity Handled**: Moderate complexity with some ambiguity

These four dimensions set the boundary for what the role should handle. The agent output may address problems well beyond the role's complexity level. It may also fall short of the expected autonomy. In either case, the expectations section tells you where to calibrate.

Extract skill IDs for scripts

When you need to check multiple skills programmatically, use the --skills flag to get a plain list of skill IDs:

npx fit-pathway job software-engineering J060 --skills

task-completion
planning
incident-response

Pipe these IDs into npx fit-pathway skill to inspect each one:

npx fit-pathway job software-engineering J060 --skills | while read id; do
  npx fit-pathway skill "$id"
  echo "---"
done

This produces the full description for every skill in the role. You can use it as a review checklist.

Verify

You reach the outcome of this page when you can answer these questions from your Pathway output:

• What skills does the role expect, and at what proficiency? You can list the skills and their expected levels from the Skill Matrix.
• What does each proficiency level look like in practice? You inspected at least one skill. You can describe the actions the expected proficiency requires.
• What behaviours does the role expect? You can name the expected maturity for each behaviour and describe what that maturity looks like.
• What scope and autonomy does the role imply? You can state the role's impact scope, autonomy expectation, and complexity level.

What's next