runbook-recon

Perform read-only reconnaissance on a single host within a bounded context.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/terencefan/inority-workspace --skill runbook-recon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbook-recon
Source: https://github.com/terencefan/inority-workspace/tree/main/skills/runbook-recon
Command: npx skills add https://github.com/terencefan/inority-workspace --skill runbook-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, read-only reconnaissance channel to support runbook planning and boundary enforcement, ensuring no execution or modification occurs during reviews.

Core Features & Use Cases

  • Read-only reconnaissance for solo main rollout and team reconnaissance lanes
  • Enforces strict boundaries: no execution, no changes, no acceptance
  • Supports kickoff/heartbeat workflows and bounded-context reporting for traceable planning

Quick Start

Initiate read-only reconnaissance for the assigned host within the defined boundary and report the initial findings.

Frequently Asked Questions about runbook-recon

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

FAQPage Schema
How do I perform read-only reconnaissance for runbook planning without making changes?

Read-only reconnaissance for runbook planning is achieved by confining scope to a single recon issue and host boundary, executing kickoff and heartbeat protocols, and generating evidence-oriented reports without system modifications.

What is bounded-reach reconnaissance and when do I need it for a rollout?

Bounded-reach reconnaissance restricts exploration to a single host boundary and bounded context during a rollout. You need it when planning solo main rollouts or team reconnaissance lanes to ensure traceable, evidence-oriented reporting.

Can I use this approach for team reconnaissance lanes and solo rollouts simultaneously?

Yes, this approach supports both solo main rollout and team reconnaissance lanes. It enforces strict boundaries with no execution, no changes, and no acceptance, applying kickoff and heartbeat workflows to manage the scope.

Does read-only reconnaissance execute any actions beyond checking the host boundary?

No, read-only reconnaissance does not execute actions beyond read-only checks. It enforces strict boundaries to ensure no execution, no changes, and no acceptance occur during the runbook planning and rollout review.

How do kickoff and heartbeat protocols work during bounded-context reporting?

Kickoff and heartbeat protocols structure the reconnaissance workflow by initiating the review and maintaining periodic status checks. They ensure bounded-context reporting remains traceable and aligned with the defined host boundary throughout the runbook planning process.