export interface IAutoBeAnalyzeReviewApplication {
    /**
     * Enhances planning documentation to meet all quality standards and requirements.
     *
     * This function receives a document and outputs an improved version directly.
     * The output IS the enhanced document itself, NOT review comments or feedback.
     *
     * The enhancement process includes:
     * - Expanding sections that are too brief
     * - Converting vague statements to specific EARS format requirements
     * - Fixing Mermaid diagram syntax errors
     * - Adding missing business processes and workflows
     * - Ensuring proper document structure and completeness
     *
     * DO: Output the actual document content that will be saved.
     * DO NOT: Output review comments or analysis of the document.
     *
     * Note: Any text output becomes part of the final document.
     *
     * @param props - The properties containing the document to enhance along with
     *   plan and review criteria for guidance
     */
    review(props: IAutoBeAnalyzeReviewApplication.IProps): void;
}
export declare namespace IAutoBeAnalyzeReviewApplication {
    interface IProps {
        /**
         * Step 1 (CoT: Review Phase) - Enhancement Criteria
         *
         * The enhancement criteria and guidelines that the agent must follow.
         *
         * This includes:
         *
         * - Minimum document length requirements
         * - Section completeness checks
         * - Link validation rules
         * - Mermaid syntax validation (especially parentheses in labels)
         * - Content specificity requirements
         * - EARS format compliance
         *
         * The review criteria ensure that documentation is implementation-ready and
         * removes all ambiguity for backend developers.
         *
         * Critical review points:
         *
         * - DO: Use double quotes for ALL labels in Mermaid diagrams
         * - DO NOT: Use spaces between brackets and quotes in Mermaid
         * - DO: Make requirements specific and measurable in natural language
         * - DO: Focus on business requirements and user scenarios
         * - DO NOT: Accept documents containing database schemas or API specifications
         * - DO: Describe business model and authentication requirements in natural language
         */
        review: string;
        /**
         * Step 2 (CoT: Plan Phase) - Original Document Plan
         *
         * The document plan that was used to create the content.
         *
         * This helps the reviewer understand:
         *
         * - What sections should be present
         * - The intended structure and organization
         * - The target audience and purpose
         * - Expected level of detail
         *
         * The enhancer uses this to ensure the improved content aligns with the
         * original plan and covers all required topics comprehensively.
         */
        plan: string;
        /**
         * Step 3 (CoT: Content Phase) - Complete Document Content
         *
         * The actual markdown document content that incorporates review feedback.
         *
         * This field contains a COMPLETE MARKDOWN DOCUMENT that has already
         * incorporated the review criteria and plan requirements.
         *
         * DO: Treat this as the final, production-ready document.
         * DO NOT: Treat this as raw input to be reviewed.
         *
         * This content represents:
         * - A fully-formed markdown document (.md file)
         * - The result of applying review criteria to the original plan
         * - A production-ready document for immediate deployment
         * - Complete business requirements ready for developers
         *
         * The enhancer should treat this as the actual document content:
         *
         * - Length and completeness (minimum 2,000 characters, more for technical
         *   docs)
         * - All sections from the plan are fully written
         * - No vague or abstract statements
         * - Proper use of EARS format for requirements
         * - Correct Mermaid diagram syntax (double quotes mandatory)
         * - Appropriate level of detail for backend implementation
         * - Proper document linking (descriptive text, not raw filenames)
         *
         * The enhancer outputs the document itself:
         *
         * - If content is provided, it represents the actual document
         * - The enhancer outputs the enhanced version AS the document itself
         * - No meta-commentary or review feedback should be in the output
         * - The output becomes the saved .md file directly
         *
         * Example of what this field contains:
         * "# Service Overview\n## Vision\nThe service provides..." (actual document)
         * NOT: "This document should cover service overview..." (review comment)
         */
        content: string;
    }
}
