Skip to content

docs: describe how agents work on issues and keep the project current - #553

Open
olebhansen-agent wants to merge 5 commits into
mainfrom
docs/agents-md-work-process
Open

olebhansen-agent wants to merge 5 commits into
mainfrom
docs/agents-md-work-process

Conversation

@olebhansen-agent

@olebhansen-agent olebhansen-agent commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

AGENTS.md gets a section on working on issues. It replaces #545.

  • What to take first. What is closest to merged goes before something new. An issue is analyzed together with the others that touch the same area, so the work is split into parts that land on their own, and no choice pulls against what is planned.
  • What an agent decides itself follows the issue's type. A person decides whether a Feature should be built, before anyone builds it. A Bug that can be reproduced, and an Enhancement that leaves what users see as it is, go from Inbox to merged without asking. Agents set the type, and leave no-agent issues alone.
  • Finding and linking work. Look for existing pull requests through the issue, open your own as a draft with Closes #N in the description, and record sub-issues and blocked-by as relations. Assign yourself to what you work on and to what you follow up while another agent works on it.
  • The project. It shows one item for what lands together, so a pull request linked to an issue is archived. Status says how far the work has come. WIP State says whether it is moving, and what it waits for when it is not.

CONTRIBUTING.md gets a release step that archives what the release shipped, since the project has no status after Waiting to be released.

Checks show that a change works, not that the project should have it. That is why the type sets the threshold, and why a Feature stops for a person even when it is easy to build.

Evidence

#539 repeated the change in the draft #533 for #532, and was closed as a duplicate. #538 was missing from #537's Development section until Closes #537 was added to its description. gh issue view 532 --json closedByPullRequestsReferences lists #533.

Against project 74, gh project item-edit 74 --owner digdir --url URL --field Status --value Testing set the field on this pull request and printed the item's id, and --clear cleared WIP State on another. Closing #545 without a merge moved it to Waiting to be released, and gh project item-archive 74 --owner digdir --id ID took it off the board.

The rules were applied to the 121 items on the board. gh issue edit set the type on 78 issues, --parent made #298 a sub-issue of #338, and --add-blocked-by with a URL made #524 blocked by digdir/microsandbox#20 in another repository.

Not confirmed: whether GitHub adds an archived pull request to the project again when it changes. #545 stayed archived when its branch was deleted.

Risk

  • None for the code. It changes what agents do while they work on an issue.
  • An agent now merges a reproducible bug fix or an enhancement without asking first. CODEOWNERS still decides which paths need a person's approval.
  • Most open issues have no type yet. An agent sets one before it starts, and a wrong type gives it the wrong threshold.
  • Self-assignment does not start the integrations bot, which skips assignments its own account made.

🤖 Generated with Claude Code

Agents missed pull requests that already existed for an issue, and nothing
told people who was on an issue or what it waited for. AGENTS.md now says
how far an agent takes an issue on its own, by the issue's type, how to
find and link the work, and how to keep the digdir-agents project current.

The project has no status for released work, so the release steps archive
what a release shipped.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@olebhansen-agent olebhansen-agent added the skip-changelog No agentctl changelog entry needed label Nov 19, 2026
@olebhansen-agent olebhansen-agent self-assigned this Nov 19, 2026
@coderabbitai

coderabbitai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 8bc13e1a-5057-4d23-b869-ff75d44b5f36

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

GitHub sets Waiting to be released on every closed item, also one that no
release will ship.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@olebhansen-agent

Copy link
Copy Markdown
Collaborator Author

This waits for a code owner's approval, since CODEOWNERS gives AGENTS.md and CONTRIBUTING.md to a person. Nothing else is open.

The one thing to weigh before approving is under Risk: agents will take reproducible bugs and enhancements from Inbox to merged without asking first.

A pull request that lacks only a code owner's approval was set to
Up-for-grabs in Testing, though no session can move it on.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@olebhansen-agent
olebhansen-agent marked this pull request as draft November 19, 2026 15:39
@olebhansen-agent
olebhansen-agent marked this pull request as ready for review November 19, 2026 15:40
@olebhansen-agent

Copy link
Copy Markdown
Collaborator Author

Since the comment above, the rules say to open every pull request as a draft and to assign yourself to work you follow up while another agent does it. The evidence now covers the issue commands, which were run when the rules were applied to the board.

It waits for a code owner's approval again. Nothing else is open.

…ollow up

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@olebhansen-agent

Copy link
Copy Markdown
Collaborator Author

Since the last comment, three things changed after input from the code owner:

  • A new part says what to take first: what is closest to merged, and to analyze an issue together with the others that touch the same area.
  • The draft rule says why: a ready pull request brings in reviewers and tells others it is stable enough to build on.
  • The board shows one item for what lands together. A sub-issue that can land on its own, and a pull request that is not linked to an issue, stay on it.

It waits for a code owner's approval. Nothing else is open.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog No agentctl changelog entry needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant