ai_tessl

Extract a complete, source-traceable legacy evidence specification for one Oracle Forms module from Forms XML/FMT/FMB/FMX, PLL/PLD, DDL, message catalogues, menus/object libraries, and screenshots. Use for fresh or incremental reverse engineering when the output must preserve every evidenced screen region, tab, field, operation, rule, message, database dependency, provenance locator, uncertainty, and source-supported detail without inventing target requirements, target architecture, target tests, POC assumptions, or implementation decisions.

Review one linked Oracle Forms legacy-evidence package produced by leg-spec-from-code-oracle for semantic relationships, cross-fact ambiguities, apparent conflicts, missing runtime context, and source-supported reconciliations. Use after Oracle code evidence extraction and before target requirement curation when the master specification and its operation, decoded-source, and database children need a human-readable semantic review overlay without modifying extracted evidence or generating target requirements, UI designs, tests, or implementation decisions.

Implement or incrementally complete a legacy-modernization module in a target Next.js application from a canonical curated feature requirement package and its linked target implementation specification. Use when a reviewed mockup supplies the approved visual UI while curated requirements supply every backend, Oracle, validation, operation, persistence, transaction, error, and security behavior; supports POC generation with explicit known gaps without silently inventing missing behavior.

Generate high-fidelity, functional Next.js mockup screens for Oracle Forms modernization from one or more module evidence folders and linked screenshots. Use when asked to preserve legacy fields, tabs, grids, section organization, and business behavior while applying minimal web modernization; combine separate Maintain/Retrieve-style forms into a unified search, filter, add, edit, and delete experience; or extend a target Next.js application while matching its existing Reference / Products / Maintain Products visual and interaction conventions.

Curate an Oracle Forms modernization feature by reconciling extracted Oracle evidence, linked screenshots, a running target mockup, its Next.js implementation, existing canonical requirements, and accepted target architecture. Use when a target mockup must be converted or incrementally enriched into a review-ready feature requirement package plus an evidence-backed server-side implementation specification covering UI-to-data mappings, LOVs, validations, detailed decision rows for Delete, Add, Edit, and other operations, Oracle-constraint-to-application-message translations, transactions, tab dependencies, APIs, errors, security, and acceptance scenarios without inventing unsupported physical mappings.