Truto Integration Build Planner

Truto Integration Build Planner

Mission

Use the CLI's AI build pipeline as a proposal engine, not an autopilot. Produce reviewable plan/report artifacts and a clear apply decision.

Inputs

Collect docs source, target slug, profile, create-vs-improve intent, resource allow-list, source-tier hint, companion docs, category/label/base URL overrides, and whether the goal is full build, descriptions-only, bad-description cleanup, or audit.

Preflight

truto whoami -p "$PROFILE" -o json --no-color
truto integrations build "$DOC_SOURCE" "$SLUG" --lookup-only -p "$PROFILE" -o json --no-color

If the slug is new, skip --lookup-only and use dry-run creation with explicit --label, --category, and --base-url when known.

Recommended Plans

Full review:

truto integrations build "$DOC_SOURCE" "$SLUG" --dry-run --strict --plan-out --report-out -p "$PROFILE"

Focused resource pass:

truto integrations build "$DOC_SOURCE" "$SLUG" --resources "$RESOURCES" --dry-run --strict --plan-out --report-out -p "$PROFILE"

Higher-quality method generation:

truto integrations build "$DOC_SOURCE" "$SLUG" --feedback-loop --max-iterations 3 --dry-run --strict --plan-out --report-out -p "$PROFILE"

Descriptions-only:

truto integrations build "$DOC_SOURCE" "$SLUG" --descriptions-only --dry-run --plan-out --report-out -p "$PROFILE"

Bad-description cleanup:

truto integrations build "$DOC_SOURCE" "$SLUG" --rewrite-bad-descriptions --dry-run --plan-out --report-out -p "$PROFILE"

Source Control Choices

• Pin --source-tier when auto discovery is wrong: openapi-only, openapi-viewer, postman, llms-full, llms-index, mdtrick, md-sibling, firecrawl, graphql-introspection, graphql-sdl, or graphql-doc.
• Add --companion-docs "$URL" when specs lack auth, rate-limit, errors, webhooks, or lifecycle prose.
• Use --no-firecrawl when crawling is disallowed or a structured source is enough.
• Use cache refresh flags only when the source changed or cached output is suspect.

Review Gate

Before recommending apply, verify:

• No strict validation failures.
• Auth/base URL/category are correct.
• Resource grouping and method names are sane.
• Pagination paths are supported by examples.
• Query/body schemas are useful but not bloated.
• Docs will land in documentation rows unless --keep-inline-docs is intentionally required.
• Suppressed changes and report warnings are understood.

Apply Policy

Never use --yes unless the user explicitly asks to apply. To apply later, rerun the same command with --yes and without --dry-run. If applying, pair this with $truto-safe-admin-operator.