Skip to content

Governed Requirements Delivery

AIKOZO End User Guide

AIKOZO helps teams turn business intent into reviewable delivery artifacts. It uses AI where it reduces repetitive drafting and discovery work, but it keeps humans in control of scope, meaning, and final approval.

This guide covers the end-user experience for analysts, planners, and builders. It describes the current tabs, the main analyst flow, the Planning flow, and the implementation flow for builder-oriented work. Start here when you want the big picture before you open a page reference or jump into a role-specific flow. You do not need any setup beyond access to the product, and most people can read this overview in about five to ten minutes.

Note

What you see depends on your role, your tenant configuration, and feature flags. Hidden tabs usually mean that the capability is not enabled for your current context.

What AIKOZO is for

AIKOZO is a requirements and delivery workspace for teams that want:

  • clearer requirements, use cases and test cases
  • stronger traceability between analysis and implementation
  • controlled AI support instead of full automation
  • bilingual work on requirements and use cases without losing canonical English structure

How AI is used selectively

AI is available where it adds real leverage:

  • generating an epic and starter requirements from a business requirement
  • enhancing requirement and use case text
  • suggesting links and semantic matches
  • analyzing Ubiquitous Language and running gap analysis
  • generating architecture and instruction artifacts for implementation work

AI is not the final decision-maker. Users still review, edit, link, and finalize artifacts before they become trusted project inputs.

Guide structure

  • Purpose and working model

Understand the main entities, builder-side concepts, the bilingual model, and where human review is expected.

  • Tabs and workspaces

Review the top-level tabs and learn which guide to open for concepts, flows, or page-by-page reference.

  • Analyst flow

Follow the recommended path from business requirement to epic, requirements, use cases, and justified gap closing.

  • Planning flow

Follow the path from validated specification scope to accepted planning baselines, scope item factors, and effort allocation guidance.

  • Builder flow

Follow the path from implementation planning to architecture, guardrails, instructions, and build execution.

  • Page reference

Look up the purpose, main actions, and pop-up modals for the main pages in the application.

  • Architecture AI guide

Learn when to use Validate, Align, and Enhance, how scoped architecture AI works, and how to review and apply AI-driven architecture changes.

  1. Start with Purpose and working model.
  2. Review Tabs and workspaces.
  3. Read the flow for your role: Analyst flow, Planning flow, or Builder flow.
  4. Use Page reference when you need page-level detail on purpose, actions, or pop-up modals.
  5. If you work on implementation architecture actively, continue with the Architecture AI guide.