chore: remove bead workflow references from AGENTS.md#209
chore: remove bead workflow references from AGENTS.md#209glassBead-tc wants to merge 2 commits intomainfrom
Conversation
👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Greptile SummaryThis PR is a documentation-only cleanup of Key observations:
Confidence Score: 5/5Safe to merge — documentation-only change with no code impact and only minor clarity gaps. All findings are P2. The change is a straightforward removal of an obsolete tool integration from a single documentation file. The two style-level issues (ambiguous opening sentence and underspecified capture destination) are editorial and do not block agents from operating correctly. No files require special attention beyond AGENTS.md itself. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Unit of Work] --> B{Architectural Decision?}
B -- Yes --> C[hdd skill\n.claude/skills/hdd/SKILL.md]
B -- No --> D[Implement directly]
C --> E[Staging ADR + spec pair]
E --> F[Validate → Accept / Reject]
F --> D
D --> G{2 consecutive surprises?}
G -- Yes --> H[ulysses-protocol\n.claude/skills/ulysses-protocol/SKILL.md]
G -- No / Resolved --> I{Refactor task?}
H --> I
I -- Yes --> J[theseus-protocol\n.claude/skills/theseus-protocol/SKILL.md]
I -- No --> K[Landing the Plane]
J --> K
K --> L[Document remaining work]
L --> M[Quality gates]
M --> N[git pull --rebase && git push]
N --> O[Clean up + Verify + Hand off]
Prompt To Fix All With AIThis is a comment left during a code review.
Path: AGENTS.md
Line: 4
Comment:
**Opening sentence slightly misrepresents HDD scope**
The new line reads "Every unit of work runs through HDD for architectural decisions," which implies HDD is mandatory for *every* task. But the HDD description immediately below scopes it to "architectural decisions, new features, protocol implementations, and behavior-changing refactors" — explicitly not every unit of work (e.g. small bug fixes, chores, pure refactors handled by theseus-protocol).
The original sentence made sense because `bead-workflow` genuinely did cover every task. Now that bead-workflow is removed, the opening premise needs to be adjusted.
```suggestion
Every unit of work follows the conditional protocols below. HDD is mandatory for architectural decisions and new features.
```
How can I resolve this? If you propose a fix, please make it concise.
---
This is a comment left during a code review.
Path: AGENTS.md
Line: 63
Comment:
**"Captured" is now undefined — no destination specified**
The old step explicitly required creating a bead: *"Every follow-up … MUST become a bead before the session ends."* The replacement is: *"must be captured before the session ends"* — but there is no longer any guidance on WHERE to capture this information (no issue tracker, no markdown list, no artifact name). The removed BEADS INTEGRATION section also explicitly forbade markdown TODOs and external issue trackers, so agents have no fallback to default to.
Consider naming a concrete artifact or mechanism (e.g. session handoff JSON, an ADR note, a GitHub Issue) so agents don't leave this ambiguous at session end.
How can I resolve this? If you propose a fix, please make it concise.Reviews (1): Last reviewed commit: "chore: remove bead workflow references f..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| ## Development Workflow (Source of Truth) | ||
|
|
||
| Every unit of work runs through two mandatory skills. Two additional protocols activate conditionally. | ||
| Every unit of work runs through HDD for architectural decisions. Two additional protocols activate conditionally. |
There was a problem hiding this comment.
The new line reads "Every unit of work runs through HDD for architectural decisions," which implies HDD is mandatory for every task. But the HDD description immediately below scopes it to "architectural decisions, new features, protocol implementations, and behavior-changing refactors" — explicitly not every unit of work (e.g. small bug fixes, chores, pure refactors handled by theseus-protocol).
The original sentence made sense because bead-workflow genuinely did cover every task. Now that bead-workflow is removed, the opening premise needs to be adjusted.
| Every unit of work runs through HDD for architectural decisions. Two additional protocols activate conditionally. | |
| Every unit of work follows the conditional protocols below. HDD is mandatory for architectural decisions and new features. |
Prompt To Fix With AI
This is a comment left during a code review.
Path: AGENTS.md
Line: 4
Comment:
**Opening sentence slightly misrepresents HDD scope**
The new line reads "Every unit of work runs through HDD for architectural decisions," which implies HDD is mandatory for *every* task. But the HDD description immediately below scopes it to "architectural decisions, new features, protocol implementations, and behavior-changing refactors" — explicitly not every unit of work (e.g. small bug fixes, chores, pure refactors handled by theseus-protocol).
The original sentence made sense because `bead-workflow` genuinely did cover every task. Now that bead-workflow is removed, the opening premise needs to be adjusted.
```suggestion
Every unit of work follows the conditional protocols below. HDD is mandatory for architectural decisions and new features.
```
How can I resolve this? If you propose a fix, please make it concise.| **MANDATORY WORKFLOW:** | ||
|
|
||
| 1. **File issues for ALL remaining work** - Every follow-up, deferred decision, or "next session" item MUST become a bead before the session ends. If an ADR references future work (e.g., "deferred to ADR-010"), create the bead now — the ADR process starts next session, but the tracking starts this one. Prose in handoff JSON is not a substitute for a bead. | ||
| 1. **Document remaining work** - Every follow-up, deferred decision, or "next session" item must be captured before the session ends. |
There was a problem hiding this comment.
The old step explicitly required creating a bead: "Every follow-up … MUST become a bead before the session ends." The replacement is: "must be captured before the session ends" — but there is no longer any guidance on WHERE to capture this information (no issue tracker, no markdown list, no artifact name). The removed BEADS INTEGRATION section also explicitly forbade markdown TODOs and external issue trackers, so agents have no fallback to default to.
Consider naming a concrete artifact or mechanism (e.g. session handoff JSON, an ADR note, a GitHub Issue) so agents don't leave this ambiguous at session end.
Prompt To Fix With AI
This is a comment left during a code review.
Path: AGENTS.md
Line: 63
Comment:
**"Captured" is now undefined — no destination specified**
The old step explicitly required creating a bead: *"Every follow-up … MUST become a bead before the session ends."* The replacement is: *"must be captured before the session ends"* — but there is no longer any guidance on WHERE to capture this information (no issue tracker, no markdown list, no artifact name). The removed BEADS INTEGRATION section also explicitly forbade markdown TODOs and external issue trackers, so agents have no fallback to default to.
Consider naming a concrete artifact or mechanism (e.g. session handoff JSON, an ADR note, a GitHub Issue) so agents don't leave this ambiguous at session end.
How can I resolve this? If you propose a fix, please make it concise.1 participant
Summary
bdcommand references<!-- BEGIN BEADS INTEGRATION -->blockbeads-sync)bd syncremoved)👾 Generated with Letta Code