Project Naming in Specifications

Overview

During the Agiloop INVENT interview process, Agiloop automatically generates a project name based on the information gathered during the interview. You can change the project name at any time from the project settings.

However, changing the project name in Agiloop does not automatically update the names referenced inside your generated specifications. Specification content must be updated manually when needed.

This is especially important before using Agiloop IMPLEMENT to generate code.

Why This Matters

Agiloop IMPLEMENT uses your specifications as the primary source of truth during code generation. If the specifications still contain an outdated project name, IMPLEMENT may:

• Generate inconsistent application names
• Create mismatched service names or identifiers
• Reference old project terminology in generated code
• Produce naming inconsistencies across documentation and implementation artifacts
  
  

To ensure clean and consistent code generation, always verify that your specifications contain the correct project name before generating features.

How to Update the Project Name in Specifications

Step 1: Open the Specification

Navigate to the specification document you want to update.

Step 2: Enter Markdown Edit Mode

Click anywhere inside the rendered specification body.

Agiloop will automatically switch the specification into Markdown edit mode.

Step 3: Update the Project Name

Search for references to the old project name and replace them with the new one.

Be sure to review:

• Executive summaries
• Feature descriptions
• Technical sections
• API references
• Deployment details
• User-facing terminology

Step 4: Save Changes

No manual save action is required.

Agiloop automatically saves specification changes as you edit.

Best Practices

• Review all specifications after renaming a project
• Keep naming consistent across all specifications and generated assets
• Verify naming consistency before running IMPLEMENT code generation