enumerate-behaviors

Enumerates Python module public API behaviors into a catalog with Given/When/Then.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Elijah-J/InfoScraper --skill enumerate-behaviors
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: enumerate-behaviors
Source: https://github.com/Elijah-J/InfoScraper/tree/main/.agents/skills/enumerate-behaviors
Command: npx skills add https://github.com/Elijah-J/InfoScraper --skill enumerate-behaviors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enumerate every testable behavior of a Python module or spec using Given/When/Then guarantees observable through the public API. It produces a durable behavior catalog under docs/behavior-catalogs/ with stable behavior IDs, coverage status, and doc-grounding evidence. This is Step 2 of the TDD pipeline.

Core Features & Use Cases

  • Enumerates every public API behavior for a target module or spec, ensuring coverage of happy paths, input variations, boundary conditions, error conditions, side effects, and return shapes.
  • Generates a single, doc-grounded catalog file under docs/behavior-catalogs/ with stable IDs and clear mappings to source documentation.
  • Provides a repeatable, audit-friendly workflow for behavior documentation aligned with SWE Chapter 12 guidelines.

Quick Start

Provide the module path or spec path to enumerate its public behaviors and generate a durable catalog under docs/behavior-catalogs/.

Frequently Asked Questions about enumerate-behaviors

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

FAQPage Schema
How do I enumerate public API behaviors for a Python module using Given/When/Then?▼

To enumerate public API behaviors, provide a Python module path or spec path. The tool analyzes the public surface and outputs a durable catalog with stable IDs, coverage status, and Given/When/Then guarantees under docs/behavior-catalogs/.

What is a behavior catalog in TDD and when do I need one?▼

A behavior catalog is a doc-grounded file mapping every testable public API behavior to stable IDs and coverage status. You need one to ensure repeatable, audit-friendly documentation aligned with SWE behavior enumeration guidelines during TDD pipelines.

How do I generate a durable behavior catalog with stable IDs for unit testing?▼

Provide a target module or spec path to generate a single doc-grounded catalog file under docs/behavior-catalogs/. This catalog includes stable behavior IDs, coverage status, and mappings to source documentation for unit testing.

Does the behavior enumeration cover error conditions and boundary cases for public APIs?▼

Yes, behavior enumeration targets the public API surface to cover happy paths, input variations, boundary conditions, error conditions, side effects, and return shapes, ensuring comprehensive testable behavior documentation.

Can I use this behavior enumeration tool without external dependencies?▼

Yes, the behavior enumeration tool operates without external dependencies. It directly analyzes your Python module or spec path to produce the durable behavior catalog file under docs/behavior-catalogs/.

What's the best way to document observable behaviors for a Python spec?▼

The best way is enumerating every testable behavior observable through the public API using Given/When/Then guarantees. This generates a repeatable, publishable catalog with stable IDs and doc-grounding evidence aligned with SWE Chapter 12 guidelines.