What problem does it solve?
It eliminates the confusion and wasted effort that happens when a bug bounty session drifts without a clear phase, engagement type, or decision framework for turning ideas into validated, reportable findings.
Core Features & Use Cases
- Engagement Mode Confirmation: Clarifies what counts as a finding (bug bounty vs red team vs pentest vs internal audit) so you don’t chase the wrong deliverable format.
- 5-Phase Non-Linear Workflow: Guides recon → mapping → discovery → proving/escalation → validating/reporting, with explicit “go back” navigation rules when you’re stuck.
- Critical Thinking & Anti-False-Positive Discipline: Adds attacker-style reasoning (trust boundaries, anomalies, what-if experiments) plus quality gates (marker uniqueness, body diffs, sample sizes) to prevent retracted or N/A findings.
- Skill-to-Phase Routing: Helps you decide what to do next by routing actions to the right downstream skills based on your current phase and obstacles.
Quick Start
Use bb-methodology at the start of your hunt or when switching targets by issuing the command bb-methodology and providing the engagement type and the target you are testing.
