No Verity fields detected on this work item. Follow the setup instructions below to add them to your ADO process — takes about 20 minutes.

Verity Framework — ADO Setup (Option 2: Add Fields to Existing Work Item Type)

Estimated time: 20 minutes. Access required: ADO Project Administrator.

Step 1 — Navigate to your process settings

Organization Settings → Boards → Process → [Your current process] (e.g. Agile, Scrum, or Basic)

Step 2 — Create an inherited process (if not already done)

Click "Create inherited process" from your base process. Name it something like "Verity Agile" or "Verity Scrum". This preserves your original process and all existing projects.

Step 3 — Add five custom fields to your User Story (or Product Backlog Item)

Select your inherited process → Work Item Types → User Story. Click "+ New field" for each of the following:

Name	Reference name	Type	Description
VF Intent	Custom.VFIntent	Text (multi-line)	What is the problem and who experiences it?
VF Value	Custom.VFValue	Text (multi-line)	What changes if this problem is solved?
VF Appetite	Custom.VFAppetite	Text (single-line)	How much time/resource is this problem worth?
VF Trust Criteria	Custom.VFTrustCriteria	Text (multi-line)	What hardening evidence is required before this ships?
VF Failure Scope	Custom.VFFailureScope	Picklist (string): Narrow, Moderate, Broad, Systemic	What is the scope of failure if this goes wrong in production?

Field format guidance

The quality of the generated prompt depends entirely on the quality of these fields. Aim for:

Field	Good	Bad
VF Intent	"Engineers reviewing AI-assisted code have no structured method for evaluating failure modes — they rely on intuition, leading to missed risks."	"Build a code review checklist feature."
VF Value	"Engineers have a consistent, evidence-based method for Gate 2 review. Estimated 30% reduction in production incidents attributable to missed failure modes."	"A checklist will be available in the PR review workflow."
VF Appetite	"3 days", "0.5 sprint", "1 week", "2 days"	"high", "medium", "large", "urgent"
VF Trust Criteria	"Load tested to 500 concurrent users with P95 response < 2 seconds"; "SAST scan clean — no high or critical severity findings"; "Rollback procedure documented and tested in staging environment"	"Tested", "Works correctly", "Causes no issues", "Approved"
VF Failure Scope	Narrow = single user or isolated feature. Moderate = feature area or user segment. Broad = significant user population or core functionality. Systemic = platform-wide impact or data integrity implications.

Step 4 — Switch your project to the inherited process

Organization Settings → Boards → Process → [Your inherited process] → Projects → Move project to this process. Select your project and confirm.

Step 5 — Install the Verity Framework extension

Install from the Visual Studio Marketplace. The "Verity Prompt" tab will appear on all User Story work items.

Step 6 — Verify

Open any User Story. You should see the five VF fields in the work item form, a "Verity Prompt" tab, and the prompt generator populated when you fill in the fields.

Reversing the setup

To remove: delete the five custom fields from the work item type and uninstall the extension. Your existing work items are unaffected. Any VF field data entered will be lost when the fields are removed.

If your organization named the custom fields differently, use the extension's Settings page (Project Settings → Verity Framework Settings) to point the extension at your actual field reference names.