==================== START: .fortura-core/checklists/agent-validation.md ====================
<!-- Powered by Fortura™ Core -->

# Agent Validation Checklist

[[LLM: INITIALIZATION INSTRUCTIONS
Execute this checklist to validate a Fortura agent configuration.
Review the agent YAML configuration and all supporting materials.
For each item, determine: PASS | FAIL | PARTIAL | N/A
Provide specific evidence from the agent configuration.
]]

---

## Section 1: Structural Completeness

[[LLM: Verify all required YAML fields are present and properly formatted]]

- [ ] **YAML block complete with all required fields**
  - What to verify: activation-instructions, agent, persona, commands, dependencies
  - Determination: _______________
  - Evidence: _______________

- [ ] **Activation instructions include all 4 standard items**
  - What to verify: Lazy loading, customization precedence, numbered options, stay in character
  - Determination: _______________
  - Evidence: _______________

- [ ] **Agent metadata complete (name, id, title, icon, whenToUse)**
  - What to verify: All 5 fields present and non-empty
  - Determination: _______________
  - Evidence: _______________

- [ ] **Persona definition includes all 5 fields**
  - What to verify: role, style, identity, focus, core_principles
  - Determination: _______________
  - Evidence: _______________

- [ ] **Commands include `help` and `exit`**
  - What to verify: Both mandatory commands present
  - Determination: _______________
  - Evidence: _______________

- [ ] **Dependencies properly categorized**
  - What to verify: checklists, data, tasks, templates, utils (use applicable categories)
  - Determination: _______________
  - Evidence: _______________

---

## Section 2: Quality Standards

[[LLM: Verify agent follows Fortura quality principles]]

- [ ] **Core principles use CRITICAL prefix for non-negotiables (at least 2-3)**
  - What to verify: 2+ principles have CRITICAL prefix
  - Determination: _______________
  - Evidence: _______________

- [ ] **Numbered options protocol included in principles or activation**
  - What to verify: Mention of numbered lists for user selections
  - Determination: _______________
  - Evidence: _______________

- [ ] **Lazy loading philosophy reflected in activation instructions**
  - What to verify: "ONLY load dependency files when user selects them"
  - Determination: _______________
  - Evidence: _______________

- [ ] **No assumptions about user intent (user agency preserved)**
  - What to verify: Principles include asking questions, not assuming
  - Determination: _______________
  - Evidence: _______________

- [ ] **Agent type appropriate for intended use**
  - What to verify: Planning/Dev/Coordination/Process/Conversational matches purpose
  - Determination: _______________
  - Evidence: _______________
  - Rationale: _______________

---

## Section 3: Differentiation

[[LLM: Ensure agent is distinct from existing agents]]

- [ ] **Persona clearly distinct from existing agents**
  - What to verify: Role, style, identity don't duplicate other agents
  - Determination: _______________
  - Evidence: _______________

- [ ] **whenToUse provides specific, non-overlapping guidance**
  - What to verify: Clear use cases that don't conflict with other agents
  - Determination: _______________
  - Evidence: _______________

- [ ] **Commands are unique to this agent's role**
  - What to verify: Custom commands match agent's specific capabilities
  - Determination: _______________
  - Evidence: _______________

- [ ] **No duplicate responsibilities with existing agents**
  - What to verify: Agent fills a unique need in the framework
  - Determination: _______________
  - Evidence: _______________

---

## Section 4: Traceability

[[LLM: Verify documentation and tracking requirements]]

- [ ] **All design decisions documented with rationale**
  - What to verify: Design notes or comments explain key choices
  - Determination: _______________
  - Evidence: _______________

- [ ] **Source citations required where appropriate (in principles)**
  - What to verify: If technical decisions made, principles require citing sources
  - Determination: _______________
  - Evidence: _______________

- [ ] **Change tracking specified if agent modifies files**
  - What to verify: File permissions or change log requirements documented
  - Determination: _______________
  - Evidence: _______________

- [ ] **Version tracking for templates if applicable**
  - What to verify: Templates use versioned IDs (e.g., template-v2)
  - Determination: _______________
  - Evidence: _______________

---

## Section 5: Anti-Hallucination Controls

[[LLM: Verify safeguards against invented information]]

- [ ] **Instructions to cite sources where technical decisions made**
  - What to verify: Principles or tasks require [Source: file.md#section] citations
  - Determination: _______________
  - Evidence: _______________

- [ ] **Explicit handling of missing information (flag vs. invent)**
  - What to verify: Principles state "flag missing info" not "invent"
  - Determination: _______________
  - Evidence: _______________

- [ ] **Reference to actual documentation/files where needed**
  - What to verify: Tasks reference specific files, not generic "documentation"
  - Determination: _______________
  - Evidence: _______________

- [ ] **No invented libraries, patterns, or frameworks**
  - What to verify: All technical references are to real, existing items
  - Determination: _______________
  - Evidence: _______________

---

## Section 6: Context Optimization

[[LLM: Verify dependencies appropriate for agent type]]

- [ ] **Development agents: Lean dependencies (< 8 items)**
  - What to verify: If agent type is Development, total dependencies < 8
  - Determination: _______________
  - Evidence: _______________
  - Note: N/A if not Development agent

- [ ] **Planning agents: Dependencies support comprehensive planning**
  - What to verify: If Planning agent, has templates, knowledge bases, tasks
  - Determination: _______________
  - Evidence: _______________
  - Note: N/A if not Planning agent

- [ ] **Coordination agents: Access to necessary cross-functional resources**
  - What to verify: If Coordination agent, has agent directories, workflow tools
  - Determination: _______________
  - Evidence: _______________
  - Note: N/A if not Coordination agent

- [ ] **No redundant or unused dependencies listed**
  - What to verify: All dependencies referenced in commands or principles
  - Determination: _______________
  - Evidence: _______________

---

## Section 7: Formatting Conventions

[[LLM: Verify proper formatting throughout]]

- [ ] **YAML: 2-space indentation, proper syntax**
  - What to verify: No tabs, consistent indentation, valid YAML
  - Determination: _______________
  - Evidence: _______________

- [ ] **Naming: kebab-case for IDs and filenames**
  - What to verify: agent.id, dependency files use kebab-case
  - Determination: _______________
  - Evidence: _______________

- [ ] **Commands: descriptive, not overly long**
  - What to verify: Command names clear, under 4 words
  - Determination: _______________
  - Evidence: _______________

- [ ] **Arrays: consistent bracket or dash notation**
  - What to verify: List style consistent within sections
  - Determination: _______________
  - Evidence: _______________

- [ ] **Null values: explicitly stated**
  - What to verify: customization: null (not omitted or empty)
  - Determination: _______________
  - Evidence: _______________

---

## Section 8: User Experience

[[LLM: Verify agent provides good user experience]]

- [ ] **Interactive patterns clear and consistent**
  - What to verify: Elicitation or dialogue patterns well-defined
  - Determination: _______________
  - Evidence: _______________

- [ ] **Numbered options for all selections**
  - What to verify: No yes/no questions for choices
  - Determination: _______________
  - Evidence: _______________

- [ ] **Help command lists all capabilities**
  - What to verify: help command specified
  - Determination: _______________
  - Evidence: _______________

- [ ] **Exit command allows graceful termination**
  - What to verify: exit command specified
  - Determination: _______________
  - Evidence: _______________

- [ ] **YOLO mode toggle if appropriate for agent type**
  - What to verify: If interactive workflows, yolo command offered
  - Determination: _______________
  - Evidence: _______________

---

## Section 9: Dependency Validity

[[LLM: Verify all dependencies exist or are planned]]

- [ ] **All referenced task files will exist or be created**
  - What to verify: Tasks listed in dependencies or supporting files list
  - Determination: _______________
  - Evidence: _______________

- [ ] **All referenced template files will exist or be created**
  - What to verify: Templates listed in dependencies or supporting files list
  - Determination: _______________
  - Evidence: _______________

- [ ] **All referenced data files will exist or be created**
  - What to verify: Data files listed in dependencies or supporting files list
  - Determination: _______________
  - Evidence: _______________

- [ ] **Checklist files will exist or be created**
  - What to verify: Checklists listed in dependencies or supporting files list
  - Determination: _______________
  - Evidence: _______________

- [ ] **No circular dependencies**
  - What to verify: Agent doesn't depend on file that depends on this agent
  - Determination: _______________
  - Evidence: _______________

---

## Section 10: Special Features

[[LLM: Verify special features properly implemented if present]]

- [ ] **File permissions clearly defined if applicable**
  - What to verify: If agent modifies files, permissions documented
  - Determination: _______________
  - Evidence: _______________
  - Note: N/A if agent doesn't modify files

- [ ] **Quality gates specified if applicable**
  - What to verify: If agent uses gates, PASS/FAIL/CONCERNS defined
  - Determination: _______________
  - Evidence: _______________
  - Note: N/A if no quality gates

- [ ] **Scoring/rating systems documented if applicable**
  - What to verify: If agent calculates scores, methodology explained
  - Determination: _______________
  - Evidence: _______________
  - Note: N/A if no scoring

- [ ] **Multi-mode behavior explained if applicable**
  - What to verify: If agent has modes, each mode documented
  - Determination: _______________
  - Evidence: _______________
  - Note: N/A if single mode

- [ ] **Integration points with other agents clear**
  - What to verify: Handoffs, file sharing, workflow transitions documented
  - Determination: _______________
  - Evidence: _______________

---

## Summary

[[LLM: Generate summary after completing all items]]

**Validation Summary**

| Status | Count |
|--------|-------|
| PASS   | ___   |
| FAIL   | ___   |
| PARTIAL| ___   |
| N/A    | ___   |
| **TOTAL** | ___ |

**Overall Validation Status:** [PASS | CONCERNS | FAIL]

**Determination Logic:**
- PASS: All items are PASS or N/A
- CONCERNS: One or more items are PARTIAL
- FAIL: One or more items are FAIL

**Critical Issues (FAIL items):**
- [List any FAIL determinations]

**Areas for Improvement (PARTIAL items):**
- [List any PARTIAL determinations]

**Recommendations:**
1. [Recommendation 1 if not PASS]
2. [Recommendation 2 if not PASS]

**Approval Decision:**
- [ ] **APPROVED** - Agent meets all quality standards, ready to use
- [ ] **APPROVED WITH MINOR REVISIONS** - Address PARTIAL items before production use
- [ ] **NOT APPROVED** - Address FAIL items and resubmit for validation

==================== END: .fortura-core/checklists/agent-validation.md ====================