Skip to main content

Automate Dependency Documentation with Charlie AI

Learn how Charlie AI automates the documentation of cross-team dependencies in Kendis.

Written by Kendis Team
Updated over 2 weeks ago

Manually drafting summaries and technical descriptions for cross-team dependencies is no longer necessary. Charlie AI is integrated into the dependency workflow to automate narrative generation. It ensures that every technical link is documented with clarity.

Charlie AI analyses each task's metadata to generate context-aware descriptions that define the relationship between source and target items. Follow the steps below to completely automate your dependency creation process.

Standard Dependency Creation Methods

Before Charlie AI can work its magic, you must first establish the connection between your Features or Stories using one of these three seamless methods:

Method A: Card-to-Card Mapping: Hover over the Receiver card and drag the connector from the top-right circle directly onto the Creator card.

Method B: Dynamic Creation: Drag a link from an existing card and drop it onto the + icon in a Sprint column to create a new dependent item and link it in a single operation.

Method C: Search-Based Linking: Open the dependencies modal and select Create by Search to locate the dependent item by ID or Title.

So, these are the common methods we all have been using to create dependency. But this time, did you see the Charlie AI icon at the top of the dependency creation modal? Let’s see how we can use it to improve the way we create new dependencies.

Dependency Creation with Charlie AI

Now that you have opened the Dependencies modal by following one of the above-mentioned methods, use the Charlie AI suite to automate the summary and description for the link.

Initialising AI Content

Click the Charlie AI icon at the top of the modal to open the generation interface.

Charlie AI analyses the titles of the linked items, such as "Regulatory Compliance Tracking" and "Online Policy Quotation & Comparison", to determine the technical context.

Technical Prompts (Optional): You may provide specific technical guidance in the optional field (e.g., "Focus on deployment blockers") to influence the output.

Automated Output: Clicking Generate with Charlie populates a Summary (defining the constraint) and a Description (detailing the impact and coordination needs).

Use the Refine with Additional Context tools to ensure technical accuracy:

Segmented Regeneration: You can choose to Regenerate Summary or Regenerate Description independently to preserve preferred sections of the text.

Instructional Updates: Enter specific technical refinements (e.g., "Include impact on security validation timeline") and click Regenerate. It will improve the generated content

Click “Use This Content” to transfer the AI-generated narrative into the primary dependency form.

Finalise the Dependency

Before saving, ensure the operational metadata is correctly defined:

  • Define the relationship, such as Predecessor or Successor, to establish the flow of work.

  • Enter the Target Resolution Date to align the dependency with your PI schedule.

  • Choose a Responsible individual and verify the Reporter to ensure clear ownership.

  • Click Save. The dependency is now live!

Important Note: This AI-assisted workflow is identical across the entire Kendis platform, whether you are working in Program Boards, Solution Boards, or high-level Organization (Orgs) views. This ensures a unified standard for dependency management across all levels of your enterprise.

Did this answer your question?