Skip to content

feat(prompts): activate the issue/PR-tool references in the role block-0 prompts (RIG-1734) - #849

Open
rigel-mintaka wants to merge 1 commit into
mainfrom
compass/rig-1734-flip-issue-pr-tool-references
Open

feat(prompts): activate the issue/PR-tool references in the role block-0 prompts (RIG-1734)#849
rigel-mintaka wants to merge 1 commit into
mainfrom
compass/rig-1734-flip-issue-pr-tool-references

Conversation

@rigel-mintaka

Copy link
Copy Markdown
Contributor

The three taxonomy role prompts (config/prompts/{manager,owner,supervisor}/SYSTEM.md) held their issue-ownership affordances as deferred [TODO RIG-1734] comments under MP-4 flip discipline: activate a deferred line in the SAME PR that lands its gating primitive. That primitive — the agent-side board_set_issue_state tool — landed in #842 (RIG-3191), so this flips all three.

Each prompt now names the concrete tools in active prose instead of a deferred comment:

  • state/close is driven by board_set_issue_state (the Compass-native manual board — an agent moves its issue as the work moves and closes it itself; a forge closed/merged badge never advances board state for it);
  • issue/PR read + write go through the forge_* tools.

The [TODO RIG-1734] marker in each block-0 header Deferred here: list (L9) and the inline body comment on the work-loop bullet are both struck. The remaining compass_tree / RIG-1721 deferrals stay as-is (their primitives have not landed). Tool-name reference style follows the file's existing convention (compass_tree names the one concrete tool; the broader surface is a family reference) and RIG-1734's own scope wording ("name board_set_issue_state … and the forge_* tools").

Content-only edits under config/prompts/**. No test pins the real prompt text (prompt-consuming tests use synthetic fixtures).

Spec-impact: none. Refs RIG-1734

Co-authored-by: Matt Wilkinson matt@rigel.build

…k-0 prompts (RIG-1734)

The three taxonomy role prompts (`config/prompts/{manager,owner,supervisor}/SYSTEM.md`) held their issue-ownership affordances as deferred `[TODO RIG-1734]` comments under MP-4 flip discipline: activate a deferred line in the SAME PR that lands its gating primitive. That primitive — the agent-side `board_set_issue_state` tool — landed in #842 (RIG-3191), so this flips all three.

Each prompt now names the concrete tools in active prose instead of a deferred comment:

- state/close is driven by `board_set_issue_state` (the Compass-native manual board — an agent moves its issue as the work moves and closes it itself; a forge closed/merged badge never advances board state for it);
- issue/PR read + write go through the `forge_*` tools.

The `[TODO RIG-1734]` marker in each block-0 header `Deferred here:` list (L9) and the inline body comment on the work-loop bullet are both struck. The remaining `compass_tree` / RIG-1721 deferrals stay as-is (their primitives have not landed). Tool-name reference style follows the file's existing convention (`compass_tree` names the one concrete tool; the broader surface is a family reference) and RIG-1734's own scope wording ("name `board_set_issue_state` … and the `forge_*` tools").

Content-only edits under `config/prompts/**`. No test pins the real prompt text (prompt-consuming tests use synthetic fixtures).

Spec-impact: none. Refs RIG-1734

Co-authored-by: Matt Wilkinson <matt@rigel.build>
@trunk-io

trunk-io Bot commented Sep 3, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@linear-code

linear-code Bot commented Sep 3, 2026

Copy link
Copy Markdown

RIG-1734

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

Compass engineering docs preview: https://compass-rig-1734-flip-issue.compass-eng-docs.pages.dev

Deployed from compass/rig-1734-flip-issue-pr-tool-references at 6e8f6eb.

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.

1 participant