Weaver E9 Auto Builder

Problem

Weaver E9 form, process, permission, list, and code block configurations are often scattered across implementation docs, screenshots, and UI pages. Manual builds can miss items, rely on guessed dependencies, and lack read-back evidence. This skill turns requirements into a verifiable E9 build plan, reducing uncertainty about whether a configuration actually took effect.

How It Works

• Read the source first: Word/DOCX inputs should be converted to Markdown via e9-cli docx read --out, then checked against amounts, dates, fields, and transitions in images.
• Plan before writing: Use plan.md to define scope, dependency edges, topology order, risks, validation criteria, and item-level completion checks; reconfirm when scope or dependencies change.
• Implement by real dependencies: Read back actual IDs, fields, and relationships before creating or changing dependent resources; configure in the order A -> B, and record completion after each read-back.
• Close the loop: Failed items are repaired and re-verified; delivery includes resource hierarchy, real IDs, evidence, and limitations.

Boundaries

This skill fits E9 environments where the target tenant, CLI access, and requirements are reasonably clear. If resource identity, critical business rules, or CLI capability cannot be confirmed from read-only evidence, it marks the block instead of guessing and writing.