Skip to content

Reconcile the agent files required by Repository Standard with the set Agentic Development defines #140

Closed

Description

A repository adopting the agent-file model reads two pages that both say which agent files it must carry. The list is stated twice, so it can disagree with itself — and it has.

Request

Repository Standard states the agent files in its required-files table, which is the surface a repository is audited against — it is what someone lists when asking "what is missing here". Agentic Development states the same set again in its own table, together with the reasoning for it: one router, and a route for every client that cannot reach it under that name.

The two tables have already disagreed. Repository Standard listed CLAUDE.md at the repository root where Agentic Development listed .claude/CLAUDE.md, and it omitted .github/copilot-instructions.md entirely although Agentic Development marks it Required. Bringing Storhaug-ting/Kilden up to the baseline produced exactly that repository — a root CLAUDE.md and no .github/copilot-instructions.md — because the required-files table was the checklist, and both were corrected only after reading Agentic Development, which is not the page a repository-baseline task routes to.

#122 has since corrected the paths, so the two tables agree today. What it did not remove is the reason they disagreed: it had to fix the same rule in two pages. A file required by the framework but absent from the required-files table gets left out, and a file placed where that table says gets placed wrong, for as long as the table keeps its own copy of the list.

Acceptance criteria:

  • A reader following the required-files table produces the same set of agent files that Agentic Development requires, at the same paths.
  • The tables cannot drift again: one page owns the list and the other links to it.
  • The set described matches what this repository actually carries.

Technical Decisions

Agentic Development owns the agent-file set. It holds the reasoning, and it is where the framework spec points for the exact set an MSX repository carries. Repository Standard should route to it rather than restate it, for the same reason a router does not restate a standard: a copy of a rule is a rule that can drift, and this issue is the proof.

The narrower alternative — correcting the rows — is what #122 already did, and it left the duplication that produced the mismatch in place.

Note that the required-files table legitimately describes files Agentic Development does not, such as .gitattributes and SECURITY.md. Only the agent-file rows move.

Related: #67 tracks required-standard files missing from this repository, and needs re-checking against the settled set.


Implementation Plan

  • Replace the agent-file rows in Repository Standard's required-files table with a single row that links Agentic Development as the owner of the agent-file set.
  • Confirm the linked table names every file, including .github/copilot-instructions.md, and matches what this repository carries.
  • Check whether Missing required repository-standard files in MSXOrg/docs #67's list changes once the set is settled.

Activity

  1. MariusStorhaug commented on Aug 2, 2026

    @MariusStorhaug
    MemberAuthor

    Body updated, and the plan is ticked off — #148 carries the change.

    What changed in the body. The Request section no longer says the two tables disagree. #122 landed after this issue was written and corrected both differences: the required-files table now lists .claude/CLAUDE.md, not a root CLAUDE.md, and it carries a .github/copilot-instructions.md row. The evidence is kept as what already happened rather than as the current state, and the ask is now stated as what #122 left behind: the same list living in two pages, which is why it had to be fixed in two places.

    Why the issue still stands. The acceptance criteria were never about the two specific mismatches — the second one asks that the tables cannot drift again. That is unmet as long as both pages carry the list, so the deduplication this issue argues for is still the whole of the work, and it is what #148 does. The narrower alternative is now recorded as the thing #122 already did.

    On the plan items. The first was written as "the AGENTS.md and CLAUDE.md rows"; the table had three agent-file rows by the time the work started, so it now reads "the agent-file rows". The third resolves to no change: #67's list is LICENSE, SECURITY.md, SUPPORT.md, CODE_OF_CONDUCT.md, .github/CODEOWNERS, .github/pull_request_template.md, and .github/release.yml, none of which are agent files, and this repository already carries all three required ones. Recorded there, with one unrelated gap that check surfaced.

    Nothing left open. The spec needed no change: its Client routes requirement already defers the exact set to Agentic Development, so the three pages agree on both the list and its owner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions