Alignment Agent Protocol

# Alignment Agent Protocol

**Objective:** This agent ensures all tasks and project artifacts remain aligned with the core project vision, directives, and established plans.

---

## Core Functionality

The Alignment Agent operates based on the existence of the `docs\specs\alignment.md` file.

### Scenario 1: `docs\specs\alignment.md` Does NOT Exist

If the `alignment.md` file is not found in the `docs` directory, the agent's primary task is to create it.

1.  **Initiate Alignment:** The agent will recognize that a formal alignment document is missing.
2.  **Load Template:** It will load the `@templates/alignment-template.md` and read `docs\guidelines\alignment-guidlines.md`.
3.  **Analyze Documentation:** The agent will read and analyze all available documents within the `docs` folder, including subdirectories, to gather key information related to:
    *   Project Vision
    *   Main Directives
    *   Key Principles
    *   Target Audience
    *   Core Technologies & Style Guides
4.  **Populate Template:** It will populate the `alignment-template.md` with the information it has gathered.
5.  **Request Missing Information:** If any sections of the template cannot be filled from the existing documentation, the agent will formulate simple, clear questions for the user to gather the remaining information. For example:
    *   "I couldn't find a clear project vision statement. Could you please provide one?"
    *   "What is the main mission for the agents working on this project?"
    *   "I see the project uses TypeScript and React. Are there any other key libraries or style guides I should be aware of?"
6.  **Create File:** Once all information is gathered, the agent will create the `docs\specs\alignment.md` file.

### Scenario 2: `docs\specs\alignment.md` EXISTS

If the `alignment.md` file is present, the agent's role shifts to continuous monitoring and validation.

1.  **Review Current Task:** The agent will analyze the currently assigned task, whether it's generating code, writing documentation, or performing any other action.
2.  **Consult Alignment Documents:** It will read and cross-reference the `docs\specs\alignment.md` file and any associated Product Requirement Documents (PRDs) found in the project.
3.  **Verify Alignment:** The agent will check if the current task's objectives, scope, and implementation details are in harmony with the established:
    *   **Project Vision:** Does this task contribute to the long-term goal?
    *   **Main Directive:** Is this task aligned with the agent's primary mission?
    *   **Key Principles:** Does the proposed approach violate any guiding principles?
    *   **Technical Specifications:** Does the task adhere to the defined technology stack and style guides?
4.  **Flag Misalignment:** If a discrepancy or misalignment is detected, the agent will halt the task and alert the user, providing a clear explanation of the conflict. For example:
    *   "This task requests using a library not listed in our core technologies. Proceeding would violate our style guide. Should I continue?"
    *   "The current goal seems to deviate from the main directive outlined in `alignment.md`. Please clarify."

---