investigate-pbi

Analyze Java/Jakarta EE PBIs and generate structured markdown investigation reports.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill investigate-pbi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate-pbi
Source: https://github.com/vndkubi/bootstrap-toolkits/tree/main/.github/skills/investigate-pbi
Command: npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill investigate-pbi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PBI and technical investigation workflow for Java/Jakarta EE projects. It performs as-is analysis by tracing current code flow, designs to-be state with proposed changes, maps scenarios with edge cases, assesses impact on affected modules and systems, identifies risks, and outputs a structured markdown investigation report.

Core Features & Use Cases

  • As-Is Analysis: trace entry points, call chains, data flow, and current validations.
  • To-Be Design: propose changes, new entities, services, and API considerations.
  • Scenario Mapping: create comprehensive scenarios including happy path, validations, and edge cases.
  • Impact & Risk Analysis: assess direct/indirect dependencies, data migrations, and risk mitigations.
  • Report Generation: produce standardized investigation documentation for reviews and audits.
  • Use Case: for PBIs, bugs, or performance issues in Java/Jakarta EE projects.

Quick Start

Provide a PBI or issue description and the system will generate a complete investigation report following the established workflow.

Frequently Asked Questions about investigate-pbi

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

FAQPage Schema
How do I conduct a technical investigation for a PBI in a Java project?▼

The investigation process parses PBI requests to perform as-is analysis on current Java code, design to-be states, map scenarios, assess risk and impact, and generate a standardized markdown report for audit and review.

What is included in an as-is and to-be analysis for a Jakarta EE bug?▼

As-is analysis traces entry points, call chains, data flow, and validations. To-be design proposes new entities, services, and API considerations to resolve the bug and improve the Jakarta EE system architecture.

How do I assess impact and risk across affected modules when analyzing a PBI?▼

Impact and risk analysis evaluates direct and indirect dependencies across affected modules, identifies data migrations, and outlines risk mitigations to ensure comprehensive scenario coverage and system stability.

Can I generate a standardized markdown investigation report for performance issues?▼

Yes, you can generate a standardized markdown investigation report by providing a performance issue description, which produces structured documentation covering as-is analysis, to-be design, and risk assessment for team reviews.

Does this investigation workflow handle edge cases and scenario mapping for new PBIs?▼

Yes, scenario mapping creates comprehensive coverage including the happy path, necessary validations, and edge cases to ensure the PBI investigation accounts for all potential technical impacts and system behaviors.