Confluence Tool

The Confluence Tool allows DinoAI to pull page content directly from Confluence, bringing your specifications, technical designs, and team documentation into your development workflow without switching tabs.

This tool bridges the gap between planning and implementation, enabling DinoAI to extract structured content from Confluence pages and turn it into actionable development work β€” from implementation checklists to dbt model requirements.

plug-circle-exclamation

Requires Confluence integration. Before using this tool, make sure you've connected your Confluence account in Paradime. See Connecting Confluence to Paradime for setup instructions.

Capabilities

The Confluence Tool fetches page content and converts it into a format DinoAI can reason over and act on. Specifically, it:

  • Retrieves page content, title, and metadata

  • Supports Confluence Cloud

  • Supports Confluence Data Center

Using the Confluence Tool

  1. Open DinoAI in the right panel of the Code IDE

  2. Provide the Confluence page ID you want to reference (e.g., 123456789)

  3. Add your prompt describing what you want DinoAI to do with the page content

  4. Grant permission when DinoAI asks to access Confluence

  5. Review and implement DinoAI's suggested actions

Example Use Cases

Summarizing Requirements from a Spec Page

Prompt

Result: DinoAI retrieves the page content, identifies the key requirements, and produces a clear summary you can use as a starting point for scoping and implementation work.

Extracting Acceptance Criteria

Prompt

Result: DinoAI reads the page, pulls out the acceptance criteria, and formats them as a structured checklist you can work through directly in the IDE β€” making it easy to track what needs to be built and validated.

Working with Other Tools

The Confluence Tool works well alongside DinoAI's other capabilities to support your full development workflow:

  • Combine with the Terminal Tool to scaffold models and run dbt commands based on requirements extracted from a Confluence page

  • Combine with the Linear Tool or Jira Tool to cross-reference ticket requirements against a linked Confluence spec

  • Use alongside Git Lite to commit implementation work that traces back to a specific page or design document

You'll need appropriate access permissions on the Confluence page for DinoAI to retrieve it. DinoAI will request permission each time it needs to access Confluence content.

Best Practices

  • Use well-structured pages β€” DinoAI works best with Confluence pages that use clear headings, structured sections, and explicit requirement or criteria language

  • Be specific in your prompt β€” Tell DinoAI exactly what you want extracted or produced, such as implementation steps, acceptance criteria, or a list of dbt models to build

  • Pair with the Linear Tool β€” If your team tracks work in Linear, use both tools together to align Confluence specs with the corresponding ticket requirements

  • Verify the output β€” Always review DinoAI's interpretation of the page content before implementing, especially for complex or densely written documentation

Last updated

Was this helpful?