advpl-tlpp-sdd

Spec-driven development for Protheus ADVPL features orchestrates work across Specify, Design, Tasks, and Execute phases. It decomposes ambiguous requirements into atomic tasks with explicit verification criteria, ensuring requirement traceability and persistent state memory across sessions.

Mapping an existing Protheus codebase uses a brownfield initialization event to load project context before feature design. This process analyzes your current ADVPL/TLPP sources and establishes a baseline state, enabling accurate feature planning and implementation within existing project structures.

UTF-8 to CP-1252 encoding conversion is automatically enforced as a safety rule after generating any Protheus source files. This mandatory conversion step happens during the Execute phase, ensuring all ADVPL/TLPP code adheres to the required character encoding before commit.

You can pause and resume Protheus feature implementation using dedicated pause and resume work events. The workflow maintains decisions, blockers, and ideas through persistent STATE memory, allowing you to securely stop and continue spec-driven development tasks across multiple sessions without losing context.

Spec-driven development for ADVPL supports both small quick fixes and large complex features through auto-sizing depth. The workflow adapts its Specify, Design, Tasks, and Execute phases based on complexity, ensuring appropriate verification steps whether handling minor adjustments or full-scale Protheus implementations.

The best way to verify TLPP code changes is using the workflow's built-in validation and work verification events. These steps enforce strong verification gates with explicit "Done when" checks and mandatory CP-1252 encoding conversion, ensuring code quality before any commit is made.