02-actors-and-boundaries

Identify human and system actors and draw system boundaries from authentication patterns.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/vishalkhondre/unearth --skill 02-actors-and-boundaries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 02-actors-and-boundaries
Source: https://github.com/vishalkhondre/unearth/tree/main/skills/02-actors-and-boundaries
Command: npx skills add https://github.com/vishalkhondre/unearth --skill 02-actors-and-boundaries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies all human and system actors that interact with the codebase, then draws the line between what's inside the system and what's outside. This produces the actor inventory, the system boundary definition, and the actor-to-system relationship map — the three inputs required for a C4 Context diagram.

Core Features & Use Cases

  • Identify human and system actors from authentication patterns across entry points.
  • Produce an actor inventory, boundary definition, and actor-to-system relationship maps for C4 Context diagrams.
  • Determine boundary decisions and capture evidence and confidence for each actor to support architecture governance.
  • Use after 01-entry-points and 00-recon steps to ensure consistent context and ownership.

Quick Start

Run the 02-actors-and-boundaries skill after completing 01-entry-points and 00-recon to generate a comprehensive actor and boundary report.

Frequently Asked Questions about 02-actors-and-boundaries

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

FAQPage Schema
How do I identify human and system actors for a C4 Context diagram?

Identify human and system actors by analyzing authentication patterns and entry-point relationships across the codebase. This process inventories all interacting actors and maps them to protocols and directions to generate the C4 Context diagram inputs.

What is a system boundary in software architecture discovery?

A system boundary defines the line between internal system components and external interacting actors. It is determined by analyzing authentication patterns and entry-point relationships to clarify ownership and context for architecture governance.

How do I map actors to entry points and protocols during architecture discovery?

Map actors to entry points and protocols by analyzing authentication patterns across system interfaces. This reveals the direction of interaction and relationships, enabling evidence-based actor mappings and clear confidence notes for each actor.

Do I need to run entry-point analysis before defining system boundaries?

Yes, you need to run 01-entry-points and 00-recon steps first. This ensures consistent context and ownership, allowing the boundary analysis to accurately map actors to entry points, protocols, and directions.

What's the best way to document boundary decisions and actor confidence levels?

Capture evidence and confidence notes for each actor during the boundary analysis. This approach supports architecture governance by producing an actor inventory, boundary definition, and actor-to-system relationship map based on authentication patterns.