Another workflow's trim no longer finds implement-feature step 1 #220

New issue

Closed

opened 2026-11-12 09:14:14 +01:00 by motoko · 0 comments

motoko commented

2026-11-12 09:14:14 +01:00

Collaborator

Seen at b04e7781d7.

Location

AGENTS.md § Workflows, which no longer names the rule.
.agents/skills/implement-feature/SKILL.md lines 12–15 and its
description, now the rule's only home.
.agents/skills/fix-bug/SKILL.md, document-feature/SKILL.md,
refactor-code/SKILL.md, and run-change/SKILL.md, which do not
point to it.

Evidence

Up to 6df8975, AGENTS.md § Workflows held: "When a request is also a
trim of AGENTS.md, a skill, a template, or a subagent brief, … run once
per work any step implement-feature gives that kind, before the step
its route starts at." Commit 612d6b6 (docs(skills): move workflow start
points to skills) moved it into implement-feature's preamble ("Step 1
runs here, or before the step another workflow's route starts at, for a
workflow whose change is also a trim …") and the end of its description
("as the opening step of another workflow's trim"). No other workflow
skill, nor AGENTS.md, refers to it.

Scenario

A user asks to fix a defect in a skill. The agent routes to fix-bug,
reads AGENTS.md and fix-bug, and goes straight to diagnose. It
never loads implement-feature, so it never saves document-reviewer's
audit in audits/ before run-change, and the trim lands unaudited.

Smallest fix

Put one sentence back in AGENTS.md § Workflows: a workflow whose
change is also a trim of AGENTS.md, a skill, a template, or a subagent
brief runs implement-feature step 1 before its own route's first step.
Pointing to it from the opening steps of fix-bug, document-feature,
and refactor-code would also work, at three places in place of one.

Seen at b04e7781d795547882b7bd47b878057cc9cdec32. ## Location - `AGENTS.md` § Workflows, which no longer names the rule. - `.agents/skills/implement-feature/SKILL.md` lines 12–15 and its description, now the rule's only home. - `.agents/skills/fix-bug/SKILL.md`, `document-feature/SKILL.md`, `refactor-code/SKILL.md`, and `run-change/SKILL.md`, which do not point to it. ## Evidence Up to 6df8975, `AGENTS.md` § Workflows held: "When a request is also a trim of `AGENTS.md`, a skill, a template, or a subagent brief, … run once per work any step `implement-feature` gives that kind, before the step its route starts at." Commit 612d6b6 (docs(skills): move workflow start points to skills) moved it into `implement-feature`'s preamble ("Step 1 runs here, or before the step another workflow's route starts at, for a workflow whose change is also a trim …") and the end of its description ("as the opening step of another workflow's trim"). No other workflow skill, nor `AGENTS.md`, refers to it. ## Scenario A user asks to fix a defect in a skill. The agent routes to `fix-bug`, reads `AGENTS.md` and `fix-bug`, and goes straight to `diagnose`. It never loads `implement-feature`, so it never saves `document-reviewer`'s audit in `audits/` before `run-change`, and the trim lands unaudited. ## Smallest fix Put one sentence back in `AGENTS.md` § Workflows: a workflow whose change is also a trim of `AGENTS.md`, a skill, a template, or a subagent brief runs `implement-feature` step 1 before its own route's first step. Pointing to it from the opening steps of `fix-bug`, `document-feature`, and `refactor-code` would also work, at three places in place of one.

motoko referenced this issue from a commit

2026-11-12 20:04:19 +01:00

fix(agents): point a trimming workflow to its audit

motoko referenced this issue from a pull request that will close it,

2026-11-12 20:04:31 +01:00

fix(agents): point a trimming workflow to its audit #224