skills.rest
ognjhunt
ognjhuntCOMMUNITY
Explore all skills by this author →
GitHub

Blocker Taxonomist

Normalize audit findings into a structured blocker register with categories, severities, and resolution paths.

Updated Dec 7, 2025
Search Tags:#auditing#risk assessment#taxonomy#qualification#resolution#blocker
One-click install
npx skills add https://github.com/ognjhunt/BlueprintCapturePipeline --skill blocker-taxonomist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Blocker Taxonomist
Source: https://github.com/ognjhunt/BlueprintCapturePipeline/tree/main/.agents/skills/blocker_taxonomist
Command: npx skills add https://github.com/ognjhunt/BlueprintCapturePipeline --skill blocker-taxonomist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes and categorizes issues found during qualification, creating a clear register for resolution and tracking.

Core Features & Use Cases

  • Blocker Normalization: Converts raw audit findings, evidence gaps, and review issues into a structured format.
  • Categorization & Severity: Assigns primary/secondary categories and severity levels based on predefined taxonomies and rules.
  • Resolution Path Assignment: Determines the necessary next steps for each blocker (e.g., recapture, scope change, site modification).
  • Use Case: After an automated audit flags several potential issues with a site capture, this Skill will consolidate them, classify them (e.g., geometry_clearance, traffic_shared), assign a severity (hard_blocker), and suggest a resolution path (recapture).

Quick Start

Use the Blocker Taxonomist skill to process the evidence audit and capability checks to generate a blocker register.

Frequently Asked Questions about Blocker Taxonomist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure raw qualification issues into a standardized blocker register?▼

To structure raw qualification issues into a blocker register, you normalize audit findings and evidence gaps into predefined categories, severities, and resolution paths like recapture or scope change.

What is the best way to categorize site qualification blockers by severity?▼

Categorizing site qualification blockers by severity involves assigning primary and secondary categories based on predefined taxonomies, determining levels such as hard blockers according to industrial humanoid site standards.

How do I assign resolution paths to evidence gaps found during an automated audit?▼

Assigning resolution paths to evidence gaps requires classifying each gap against predefined rules to determine necessary next steps, such as site modification, human review, OEM consultation, or platform change.

Does this blocker taxonomy tool work with scene graph and site intake artifacts?▼

Yes, the blocker taxonomy tool integrates with scene graph and site intake artifacts, processing evidence audit and capability checks to identify and classify blockers accurately.

When should I use an automated blocker resolution path instead of human review?▼

You should use an automated blocker resolution path when a clear taxonomy rule matches the issue, whereas human review applies to ambiguous qualification findings or complex evidence gaps lacking predefined resolution criteria.

Related Skills

Explore More Software Engineering Skills→
ognjhuntognjhunt

Intake Normalizer

Normalize site intake JSON and manifest fields for qualification analysis.

Community
Advanced
halo-devhalo-dev
6

openspec-apply-change

Implement OpenSpec change tasks by reading status and task artifacts.

Official
Advanced
ognjhuntognjhunt

Blueprint Capture

Manage iOS capture app workflows and raw evidence bundle uploads.

Community
Intermediate
praburajasekaranpraburajasekaran

source-command-triage

Categorize code review, security audit, and performance findings into the CLI todo system.

Community
Intermediate