planning-osprey-rules

To gather requirements for SML rules in Osprey, standardize the planning phase by validating project context and producing structured specifications. This process defines detection logic, labeling patterns, and entity types before writing code.

Osprey rule creation fails without structured requirements gathering because it leads to invalid code generation. Enforcing a rigorous planning phase ensures labels exist in configurations and target entities are correctly identified, preventing downstream implementation failures.

Before gathering requirements for an Osprey SML rule, you need a valid investigator report. This report must contain project structure, label tables, and UDF signatures to successfully validate project context and proceed with specification generation.

Context validation for ATProto rule specifications works by checking the investigator report for necessary project metadata, labels, and UDF signatures. This ensures all required configuration details are present before defining event types and target entities.

No, you cannot define target entities and expiration logic without a label table in the investigator report. The skill requires a valid investigator report containing project structure, label tables, and UDF signatures to function and produce specifications.