feat: Add Research Quality Standards for knowledge-focused agents #8
Conversation
📝 WalkthroughSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings. WalkthroughAdds formal Research Quality Standards documentation, updates an agent template with the new standards and a template version bump, and introduces an ADR establishing a coupling strategy between agent definitions, the Research Quality workflow, and the adversarial-workflow CLI. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @.claude/agents/AGENT-TEMPLATE.md:
- Around line 342-343: Update the metadata "Last Updated" field in the
AGENT-TEMPLATE.md header to the correct date 2026-01-28 (replace the incorrect
2025-01-28), keeping "Template Version: 1.3.0" unchanged; locate the "Template
Version" and "Last Updated" lines in the file and change only the date string
for "Last Updated" so the metadata reflects the PR creation date.
.claude/agents/AGENT-TEMPLATE.md
Outdated
| **Template Version**: 1.3.0 | ||
| **Last Updated**: 2025-01-28 |
There was a problem hiding this comment.
Fix the date inconsistency in metadata.
The "Last Updated" date changed from 2025-11-27 to 2025-01-28, which moves backwards in time (November to January within the same year). Given that this PR was created on 2026-01-28, the correct date should likely be 2026-01-28.
📅 Proposed fix for the date
**Template Version**: 1.3.0
-**Last Updated**: 2025-01-28
+**Last Updated**: 2026-01-28
**Project**: agentive-starter-kit📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| **Template Version**: 1.3.0 | |
| **Last Updated**: 2025-01-28 | |
| **Template Version**: 1.3.0 | |
| **Last Updated**: 2026-01-28 |
🤖 Prompt for AI Agents
In @.claude/agents/AGENT-TEMPLATE.md around lines 342 - 343, Update the metadata
"Last Updated" field in the AGENT-TEMPLATE.md header to the correct date
2026-01-28 (replace the incorrect 2025-01-28), keeping "Template Version: 1.3.0"
unchanged; locate the "Template Version" and "Last Updated" lines in the file
and change only the date string for "Last Updated" so the metadata reflects the
PR creation date.
Introduces a comprehensive quality framework for agents that produce research, analysis, or knowledge documents. Workflow document establishing the Four Quality Gates: - Gate 1: Citation Integrity (verify URLs, mark status) - Gate 2: Factual Accuracy (confidence levels, verification hierarchy) - Gate 3: Reproducibility (search methodology documentation) - Gate 4: External Validation (adversarial evaluation) Includes document lifecycle, working process template, and checklists. Documents the architectural decision to keep tight coupling between agent definitions and adversarial-workflow CLI commands: - Analysis of abstraction levels (tool-specific vs mechanism-aware) - Trade-off evaluation favoring agent effectiveness - Coupling manifest template for tracking - Future refactoring path if needed - Added "Research Quality Standards" section (marked optional for non-knowledge agents) - Added "File Location Standards" section - Template version: 1.1.0 → 1.3.0 Knowledge-focused agents (research specialists, analysts, etc.) should: 1. Include the Research Quality Standards section from template 2. Follow the Four Quality Gates for all research output 3. Use `adversarial evaluate` for Gate 4 validation Implementation-focused agents can delete the Research Quality section. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
movito
force-pushed
the
upstream-research-quality-standards
branch
from
8746e86 to
4e5b7c3
Compare
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Fix all issues with AI agents
In @.agent-context/workflows/RESEARCH-QUALITY-STANDARDS.md:
- Line 4: Update the metadata line that currently reads "**Last Updated**:
2025-01-28" to the correct date matching the PR creation date, i.e. "**Last
Updated**: 2026-01-28", so the timestamp in the
.agent-context/workflows/RESEARCH-QUALITY-STANDARDS.md file is consistent with
the changes.
In @.claude/agents/AGENT-TEMPLATE.md:
- Line 342: Add a single trailing newline character to the end of the Markdown
file that currently ends with the text "**Template Version**: 1.3.0" so the file
ends with exactly one newline (satisfying MD047); open
.claude/agents/AGENT-TEMPLATE.md, move the cursor to the end of the file after
the "Template Version: 1.3.0" line and insert a single newline, then save.
In
`@docs/decisions/starter-kit-adr/KIT-ADR-0020-research-quality-coupling-strategy.md`:
- Line 4: Update the ADR metadata Date field in
KIT-ADR-0020-research-quality-coupling-strategy.md: change the existing `Date:
2025-01-28` entry to `Date: 2026-01-28` so the ADR date matches the PR creation
date; locate the `**Date**:` line in that file and replace the year accordingly.
| # Research Quality Standards | ||
|
|
||
| **Version**: 1.0.0 | ||
| **Last Updated**: 2025-01-28 |
There was a problem hiding this comment.
Fix the date inconsistency in metadata.
The "Last Updated" date is 2025-01-28, but this PR was created on 2026-01-28. The year appears to be incorrect.
📅 Proposed fix
-**Last Updated**: 2025-01-28
+**Last Updated**: 2026-01-28📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| **Last Updated**: 2025-01-28 | |
| **Last Updated**: 2026-01-28 |
🤖 Prompt for AI Agents
In @.agent-context/workflows/RESEARCH-QUALITY-STANDARDS.md at line 4, Update the
metadata line that currently reads "**Last Updated**: 2025-01-28" to the correct
date matching the PR creation date, i.e. "**Last Updated**: 2026-01-28", so the
timestamp in the .agent-context/workflows/RESEARCH-QUALITY-STANDARDS.md file is
consistent with the changes.
| **Template Version**: 1.2.0 | ||
| **Last Updated**: 2025-01-28 | ||
| **Project**: agentive-starter-kit | ||
| **Template Version**: 1.3.0 No newline at end of file |
There was a problem hiding this comment.
Add trailing newline at end of file.
Markdown files should end with a single newline character for better compatibility with version control systems and text processing tools.
📝 Proposed fix
**Template Version**: 1.3.0
+As per coding guidelines: markdownlint rule MD047 (single-trailing-newline).
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| **Template Version**: 1.3.0 | |
| **Template Version**: 1.3.0 | |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
342-342: Files should end with a single newline character
(MD047, single-trailing-newline)
🤖 Prompt for AI Agents
In @.claude/agents/AGENT-TEMPLATE.md at line 342, Add a single trailing newline
character to the end of the Markdown file that currently ends with the text
"**Template Version**: 1.3.0" so the file ends with exactly one newline
(satisfying MD047); open .claude/agents/AGENT-TEMPLATE.md, move the cursor to
the end of the file after the "Template Version: 1.3.0" line and insert a single
newline, then save.
| # KIT-ADR-0020: Research Quality Standards Coupling Strategy | ||
|
|
||
| **Status**: Accepted | ||
| **Date**: 2025-01-28 |
There was a problem hiding this comment.
Fix the date inconsistency in ADR metadata.
The date is 2025-01-28, but this PR was created on 2026-01-28. The year appears to be incorrect.
📅 Proposed fix
-**Date**: 2025-01-28
+**Date**: 2026-01-28📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| **Date**: 2025-01-28 | |
| **Date**: 2026-01-28 |
🤖 Prompt for AI Agents
In
`@docs/decisions/starter-kit-adr/KIT-ADR-0020-research-quality-coupling-strategy.md`
at line 4, Update the ADR metadata Date field in
KIT-ADR-0020-research-quality-coupling-strategy.md: change the existing `Date:
2025-01-28` entry to `Date: 2026-01-28` so the ADR date matches the PR creation
date; locate the `**Date**:` line in that file and replace the year accordingly.
Summary
Introduces a comprehensive quality framework for agents that produce research, analysis, or knowledge documents. This ensures research outputs are factually accurate, well-sourced, and defensible.
The Four Quality Gates
adversarial evaluatefor high-stakes docsNew Files
.agent-context/workflows/RESEARCH-QUALITY-STANDARDS.mddocs/decisions/starter-kit-adr/KIT-ADR-0020-research-quality-coupling-strategy.mdTemplate Changes
.claude/agents/AGENT-TEMPLATE.mdUsage
For knowledge-focused agents (researchers, analysts, specialists):
adversarial evaluatefor Gate 4For implementation-focused agents (developers, testers):
Coupling Decision (KIT-ADR-0020)
We chose tight coupling (inline CLI commands in agents) over loose coupling (reference-only) because:
Test Plan
🤖 Generated with Claude Code