Build · Assess & Decide · Ops & Automation
Pre-requisition team gap register
A defensible record of WHY this role exists and the specific gap it fills on the team, completed before any job description is written.
You receive: A JSON object: { role_title, team_name, requisition_type (enum: new-role|backfill|reshape), strategic_goals[] (each {goal, required_capability}), current_team[] (each {member_label, key_skills[], aspiration}), gap_items[] (each {capability, gap_type enum: missing|thin|leaving, current_coverage_count, future_need_horizon enum: now|6mo|1-3yr, fills_structural_hole bool}), cultural_fit_traits[], overlap_risks[] (aspirations that already exist on the team), justification_summary_fields {hole_filled, why_not_internal} }.
Part of Lead Team
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"future_horizons",
"requisition_type"
],
"checkNames": [
"format_parses",
"requisition_type_matches",
"strategic_goals_count",
"goal_capability_paired",
"team_inventoried",
"gap_count",
"gap_enums",
"coverage_numeric",
"overlap_detected",
"justification_complete"
],
"constants": {},
"deliverableLabel": "pre_requisition_gap_register",
"documentKeys": [
"aspiration",
"capability",
"current_coverage_count",
"current_team",
"future_need_horizon",
"gap_items",
"gap_type",
"goal",
"hole_filled",
"justification_summary_fields",
"key_skills",
"overlap_risks",
"required_capability",
"requisition_type",
"strategic_goals",
"why_not_internal"
],
"enumLiterals": [
[
"missing",
"thin",
"leaving"
],
[
"new-role",
"backfill",
"reshape"
],
[
"now",
"6mo",
"1-3yr"
]
],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.