plan-engagement

Generate a structured pentest engagement plan and initialize plan.md and session.json.

18|3|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Kalp1774/akira --skill plan-engagement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-engagement
Source: https://github.com/Kalp1774/akira/tree/main/skills/plan-engagement
Command: npx skills add https://github.com/Kalp1774/akira --skill plan-engagement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a clear, auditable engagement plan before any tools or scans are run, removing uncertainty about scope, required phases, and tracking artifacts across a pentest lifecycle.

Core Features & Use Cases

  • Interactive scoping: Prompts the user for quick vs full mode, target domain/IP, and in-scope/out-of-scope notes.
  • Automated artifact initialization: Generates a plan.md and a session.json that initialize the Pentest Task Tree (PTT) and session tracking.
  • Phase handoff guidance: Defines how subsequent phases should update session.json so recon, secrets, exploit, triage, and report phases can consume and append structured findings.
  • Use Case: Start a new bug bounty or red team engagement, choose Quick mode to jump straight to recon, or Full mode to create a persistent results directory and tracking artifacts.

Quick Start

Start a full engagement plan for example.com in Full mode with scope "in-scope: example.com".

Frequently Asked Questions about plan-engagement

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

FAQPage Schema
How do I create a structured pentest engagement plan for a target domain?

To create a pentest engagement plan, initialize a red team or bug bounty assessment by defining the target domain or IP, specifying in-scope and out-of-scope notes, and generating a plan.md to document the required phases.

What is the difference between quick and full mode when planning a pentest session?

Quick mode jumps directly to the recon phase for immediate scanning, whereas full mode establishes a persistent results directory and initializes a session.json file to track findings across all assessment phases.

How do I track pentest findings and scope information across different assessment phases?

You can track pentest findings by initializing a session.json file under a target-specific results directory, which subsequent phases like recon, secrets, exploit, triage, and report update with structured findings.

Do I need to manually initialize the Pentest Task Tree before running a bug bounty assessment?

No, you do not need to manually initialize the Pentest Task Tree. Generating an engagement plan automatically creates the task tree nodes and instructs subsequent phases to append structured findings to session.json.

What artifacts are generated when setting up a new red team engagement scope?

Setting up a red team engagement scope generates a plan.md file for phase documentation and a session.json file for tracking, both stored under the ~/pentest-toolkit/results/<target> directory.