garura:algorithm

You generate reference pseudocode by running the algorithm command on an issue branch containing a prepared tech.yaml file, which produces a language-agnostic reference-algorithms.md artifact. It scans behavior contracts to detect complexity and emits deterministic algorithm documentation.

An algorithm spec required trigger is an explicit boolean flag set to true in tech.yaml that forces pseudocode generation for specific internal interfaces. It bypasses automated complexity detection by directly signaling that deterministic algorithm documentation is needed.

You document edge cases and invariants by generating a reference-algorithms.md file, which includes a dedicated section per qualifying interface. Each section contains complexity classification, language-agnostic pseudocode, invariants, and edge case handling.

Yes, a human approval gate is required. The Skill writes a DRAFT reference-algorithms.md artifact that must be explicitly locked via a user tether action before any evidence is recorded in the STM design context.

Complexity detection works by scanning internal_interfaces behavior_contracts in tech.yaml against 11 predefined indicator patterns. If these patterns match or an explicit algorithm_spec_required flag is true, the interface qualifies for pseudocode generation.

Yes, it is designed for enterprise SDLC workflows to provide deterministic delivery. It translates algorithmically complex internal interfaces into language-agnostic reference pseudocode, ensuring teams implement exact behavior instead of guessing flows.