Feature Review Process

Overview

Agiloop IMPLEMENT provides an optional human review workflow for generated feature code.

By default, the Requires Human Review option is disabled for new features. When enabled, generated output must be explicitly reviewed and approved by a member of your team before the feature can be marked complete.

This workflow is useful for projects that require additional oversight, compliance validation, architectural review, or manual quality assurance before accepting generated code.

How Human Review Works

During implementation, Agiloop IMPLEMENT generates the code for a feature and performs its standard automated validation and review processes.

Once generation is complete, the feature moves into the Review status.

From there, behavior depends on whether Requires Human Review is enabled.

When Human Review Is Enabled

If Requires Human Review is enabled:

• The feature remains in the Review status
• A human reviewer must approve or reject the generated output
• The feature cannot move to Done until approval is completed

This allows your team to inspect generated code before final acceptance.

When Human Review Is Disabled

If Requires Human Review is not enabled:

• Agiloop performs a final automated review
• The feature is automatically approved
• The feature moves directly to the Done status

This workflow is ideal for rapid implementation cycles where manual approval is not required.

Approving a Feature

When reviewing generated output, reviewers may approve the feature if the implementation meets expectations.

Once approved:

• The feature exits the Review state
• The feature moves into the Done status
• The implementation is considered complete

Rejecting a Feature

If the generated implementation does not meet requirements, the reviewer may reject the feature.

When rejecting a feature:

1. The reviewer is prompted to enter a rejection reason
2. The feature is moved back to the backlog
3. The feature may be rescheduled for future implementation

Providing clear rejection feedback helps improve future generation attempts and team coordination.

How to Enable Human Review

Step 1: Open the Feature Menu

Navigate to the feature you want to configure.

Step 2: Enable Requires Human Review

From the feature menu, select:

Requires Human Review

Once enabled, all future implementation runs for that feature will require manual approval before completion.

Common Use Cases

Teams commonly enable human review for:

• Security-sensitive functionality
• Compliance-regulated systems
• Financial or transactional logic
• Public-facing APIs
• Infrastructure automation
• Authentication and authorization features
• High-risk production systems
• Critical customer workflows

Best Practices

• Enable human review for high-impact or sensitive features
• Require reviewers to provide actionable rejection feedback
• Establish team review standards for consistency
• Use automated approval workflows for low-risk or iterative development
• Combine human review with strong code generation skills and validation policies

Example Workflow

1. Feature enters implementation
2. IMPLEMENT generates code
3. Feature moves into Review
4. Reviewer evaluates generated output
5. Reviewer approves or rejects the feature
6. Approved features move to Done
7. Rejected features return to the backlog