aidlc-intent

To draft an Intent document in Confluence before Jira, iterative drafting applies lightweight templates, incorporates human-in-the-loop validation checkpoints, and requires explicit approval gates to ensure risk visibility.

AI-DLC Intent documentation defines initiative planning pages requiring risk visibility, NFRs, and measurement criteria. You need it for new or evolving projects to guide Mob Elaboration before Jira work is created.

Add risk signaling and NFRs to a Confluence planning page by applying structured workflow guidance during the iterative Intent draft, surfacing risks and measurement criteria before downstream Jira artifacts are generated.

Yes, you can require approval gates before Jira tickets are created. The process enforces human-in-the-loop validation checkpoints on the Confluence Intent document to secure explicit approval before generating Jira work.

This works for both creating and updating existing initiative docs or Confluence planning pages. Iterative refinement applies to new and evolving projects, ensuring risk visibility and measurement criteria are maintained.

The best way to link planning artifacts for Mob Elaboration is through structured workflow guidance that connects relevant planning artifacts and references directly within the drafted Confluence Intent document.