plan-engagement

Create structured pentest engagement plans with phased task trees.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates structured engagement plans for pentest targets to guide phased activities.

Core Features & Use Cases

  • Generate an engagement plan document outlining scope and phases.
  • Initialize a PTT session and plan artifacts (plan.md and session.json).
  • Support quick mode to skip plan creation and jump to recon.

Quick Start

Run /plan-engagement <target> to generate a full engagement plan and initialize the session.

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 new target?

A pentest engagement plan provides a clear blueprint by generating a plan document outlining scope and phases for your target. It initializes a session and produces artifacts to guide your phased activities.

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

Pentest planning quick mode skips plan creation to jump directly to recon, while full mode generates a plan document and initializes session artifacts. Choose quick mode for immediate reconnaissance and full mode for structured tracking.

Do I need any dependencies to initialize a pentest session and plan?

No dependencies are required to initialize a pentest session and plan. The tool operates independently to generate your plan.md and session.json artifacts directly under your local results directory.

What artifacts are generated when scoping a pentest target?

Scoping a pentest target generates a plan.md document and a session.json file under the ~/pentest-toolkit/results/<target> directory. These artifacts define a phased task tree for tracking your engagement progress.

Can I use this to plan a pentest for both domains and IP addresses?

Yes, you can plan a pentest for both target domains and IP addresses. The planner applies to starting new engagements and creates a structured blueprint regardless of the specific target type.