Skip to content

Conversation

@movito
Copy link
Owner

@movito movito commented Jan 28, 2026

Summary

  • Adds File Location Standards section to AGENT-TEMPLATE.md (inherited by all new agents)
  • Adds File Location Standards section to OPERATIONAL-RULES.md (applies to all agents)
  • Prevents common mistake of creating ADRs and documentation in .claude/ instead of proper locations

Motivation

In downstream projects, agents were creating ADRs in .claude/ directory instead of docs/decisions/adr/. This happened because agent instructions didn't explicitly specify file locations.

Adding explicit standards to:

  1. AGENT-TEMPLATE.md ensures new agents inherit correct guidance
  2. OPERATIONAL-RULES.md provides reference for all existing agents

Changes

AGENT-TEMPLATE.md

## File Location Standards (MANDATORY)

| Document Type | Location | Example |
|---------------|----------|---------|
| **ADRs** | `docs/decisions/adr/` | `ADR-004-feature-name.md` |
| **Tasks** | `delegation/tasks/1-backlog/` | `TASK-0030-task-name.md` |
| **Research** | `[project-specific]/research/<topic>/` | `analysis.md` |

**DO NOT create ADRs or documentation in `.claude/`** - that directory is for agent definitions and settings only.

OPERATIONAL-RULES.md

  • Added comprehensive file location standards section
  • Explains WHY file locations matter (discoverability, tool integration, separation of concerns)
  • Lists correct/incorrect locations for ADRs, tasks, research, and agent definitions

Test plan

  • Verify AGENT-TEMPLATE.md has new section
  • Verify OPERATIONAL-RULES.md has new section
  • Create a new agent from template and verify it includes the standards

🤖 Generated with Claude Code

…ules

Prevents common mistake of creating ADRs and documentation in `.claude/`
directory instead of proper project documentation locations.

Adds:
- File Location Standards section to AGENT-TEMPLATE.md
- File Location Standards section to OPERATIONAL-RULES.md
- Clear DO/DON'T guidance for ADRs, tasks, and research docs

This ensures new agents created from the template inherit correct
file placement guidance, reducing documentation location drift.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@coderabbitai
Copy link

coderabbitai bot commented Jan 28, 2026

📝 Walkthrough

Summary by CodeRabbit

Release Notes

  • Documentation
    • Established standardized file location guidelines for Architecture Decision Records (ADRs), Tasks, Research Documents, and Agent Definitions
    • Updated operational guidelines and template versions to reflect new documentation organization standards

✏️ Tip: You can customize this high-level summary in your review settings.

Walkthrough

Updated agent templates and operational documentation to establish standardized file location conventions for architectural decision records (ADRs), tasks, research documents, and agent definitions across the project, with version increments and date updates.

Changes

Cohort / File(s) Summary
Agent Documentation Standards
.claude/agents/AGENT-TEMPLATE.md, .claude/agents/OPERATIONAL-RULES.md
Added mandatory "File Location Standards" section defining canonical paths for ADRs (docs/decisions/adr/), Tasks (delegation/tasks/[status]/), Research documents (docs/research/), and Agent definitions (.claude/agents/). Includes explicit prohibitions on incorrect locations and rationale for standards. Updated versions (1.1.0→1.2.0 and 2.0→2.1) and timestamps (2025-11-27/2025-11-12 → 2025-01-28).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A burrow well-organized,
ADRs in docs where they're prized,
Tasks in delegation's nest,
Each file finds its rightful rest—
Standards hop, and chaos is organized! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: adding file location standards to two documentation files.
Description check ✅ Passed The description provides relevant context about the changes, motivation for the updates, and examples of the standards being added.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (2)
  • ADR-004: Entity not found: Issue - Could not find referenced Issue.
  • TASK-0030: Entity not found: Issue - Could not find referenced Issue.

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Fix all issues with AI agents
In @.claude/agents/AGENT-TEMPLATE.md:
- Around line 302-303: Update the "Last Updated" date in the AGENT-TEMPLATE
header from 2025-01-28 to the correct PR creation date 2026-01-28 by editing the
"Last Updated" line (the header block containing "Template Version" and "Last
Updated") so it reads **Last Updated: 2026-01-28**; leave "Template Version"
unchanged.
- Around line 227-240: Update the Tasks entry in the "File Location Standards
(MANDATORY)" table in AGENT-TEMPLATE.md so it reflects the full folder pattern
used elsewhere (not just delegation/tasks/1-backlog/); replace the single
example with the canonical pattern (e.g., delegation/tasks/{number}-{status}/)
or list the status folders (2-todo/, 3-in-progress/, 5-done/, etc.) to match
OPERATIONAL-RULES.md and other references in this template.

In @.claude/agents/OPERATIONAL-RULES.md:
- Around line 3-4: Update the "Last Updated" metadata in
.claude/agents/OPERATIONAL-RULES.md from "2025-01-28" to "2026-01-28": locate
the header block containing "**Version**: 2.1" and "**Last Updated**:
2025-01-28" and change the date string to 2026-01-28 so the file reflects the PR
creation date.

Comment on lines +227 to +240
## File Location Standards (MANDATORY)

When creating project documentation, use the correct locations:

| Document Type | Location | Example |
|---------------|----------|---------|
| **ADRs** | `docs/decisions/adr/` | `ADR-004-feature-name.md` |
| **Tasks** | `delegation/tasks/1-backlog/` | `TASK-0030-task-name.md` |
| **Research** | `[project-specific]/research/<topic>/` | `analysis.md` |

**DO NOT create ADRs or documentation in `.claude/`** - that directory is for agent definitions and settings only.

**Before creating an ADR**: Read `.agent-context/workflows/ADR-CREATION-WORKFLOW.md` for template and numbering.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Excellent addition! The File Location Standards section addresses the PR objectives effectively.

The new section provides clear guidance on where to place different document types and explicitly prohibits using .claude/ for ADRs/docs. This should prevent the downstream confusion mentioned in the PR objectives.

However, there's a minor inconsistency in the table:

Fix: Tasks location should reflect all status folders, not just backlog.

Line 234 shows only delegation/tasks/1-backlog/ for Tasks, but this template itself references multiple status folders throughout:

  • Line 46: 2-todo/
  • Line 53: 3-in-progress/
  • Line 71: 5-done/
  • Line 191: references numbered folders

The table should align with the comprehensive guidance in OPERATIONAL-RULES.md.

📝 Proposed fix
-| **Tasks** | `delegation/tasks/1-backlog/` | `TASK-0030-task-name.md` |
+| **Tasks** | `delegation/tasks/[status-folder]/` | `TASK-0030-task-name.md` |

Or show the full pattern with status folders:

-| **Tasks** | `delegation/tasks/1-backlog/` | `TASK-0030-task-name.md` |
+| **Tasks** | `delegation/tasks/{1-backlog,2-todo,3-in-progress,5-done}/` | `TASK-0030-task-name.md` |
🤖 Prompt for AI Agents
In @.claude/agents/AGENT-TEMPLATE.md around lines 227 - 240, Update the Tasks
entry in the "File Location Standards (MANDATORY)" table in AGENT-TEMPLATE.md so
it reflects the full folder pattern used elsewhere (not just
delegation/tasks/1-backlog/); replace the single example with the canonical
pattern (e.g., delegation/tasks/{number}-{status}/) or list the status folders
(2-todo/, 3-in-progress/, 5-done/, etc.) to match OPERATIONAL-RULES.md and other
references in this template.

Comment on lines +302 to +303
**Template Version**: 1.2.0
**Last Updated**: 2025-01-28
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix the year in the Last Updated date.

The Last Updated date shows 2025-01-28, but the PR was created on 2026-01-28 (per PR objectives). The year appears to be incorrect.

📅 Proposed fix
 **Template Version**: 1.2.0
-**Last Updated**: 2025-01-28
+**Last Updated**: 2026-01-28
 **Project**: agentive-starter-kit
🤖 Prompt for AI Agents
In @.claude/agents/AGENT-TEMPLATE.md around lines 302 - 303, Update the "Last
Updated" date in the AGENT-TEMPLATE header from 2025-01-28 to the correct PR
creation date 2026-01-28 by editing the "Last Updated" line (the header block
containing "Template Version" and "Last Updated") so it reads **Last Updated:
2026-01-28**; leave "Template Version" unchanged.

Comment on lines +3 to +4
**Version**: 2.1
**Last Updated**: 2025-01-28
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix the year in the Last Updated date.

Same issue as the template file: the Last Updated date shows 2025-01-28, but the PR was created on 2026-01-28. The year should be 2026.

📅 Proposed fix
 **Version**: 2.1
-**Last Updated**: 2025-01-28
+**Last Updated**: 2026-01-28
 **Applies To**: ALL agents in this project
📝 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.

Suggested change
**Version**: 2.1
**Last Updated**: 2025-01-28
**Version**: 2.1
**Last Updated**: 2026-01-28
🤖 Prompt for AI Agents
In @.claude/agents/OPERATIONAL-RULES.md around lines 3 - 4, Update the "Last
Updated" metadata in .claude/agents/OPERATIONAL-RULES.md from "2025-01-28" to
"2026-01-28": locate the header block containing "**Version**: 2.1" and "**Last
Updated**: 2025-01-28" and change the date string to 2026-01-28 so the file
reflects the PR creation date.

@movito movito merged commit 7e93112 into main Jan 28, 2026
3 checks passed
@movito movito deleted the upstream-file-location-standards branch January 28, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants