playbook-builder

Executable playbooks are created by defining structured step formats and frontmatter fields that document how to validate features across local, staging, and production environments. This automates validation workflows by converting spikes or contracts into repeatable tests stored under ~/.knowledge/playbooks/.

The PB-NNN naming convention is a standardized identification scheme enforced for creating playbooks under ~/.knowledge/playbooks/. It ensures coherence and enables stale-detection by applying hierarchical references to templates during feature validation.

Spikes or contracts are converted into runnable validation workflows by applying a standardized step format and frontmatter-driven structure. This process stabilizes behavior for automated validation across different environments.

Templates are required to maintain coherence and support hierarchy when documenting feature tests. The playbook structure applies hierarchical references to templates and frontmatter fields to validate features across local, staging, and production environments.

Standardizing test documentation requires enforcing a structured step format and frontmatter-driven storage layout. This approach ensures consistent automation and human review while applying naming schemes like PB-xxx to validate existing features.

Child playbooks can be reused within the hierarchy to support structured test validation workflows. This reusability works alongside hierarchical references to templates to maintain coherence and enable stale-detection across environments.