Skip to content

feat(pipeline): drop status:ready gate — implement directly from status:refined#127

Draft
Zlyzart wants to merge 1 commit into
trunkfrom
claude/drop-status-ready-gate
Draft

feat(pipeline): drop status:ready gate — implement directly from status:refined#127
Zlyzart wants to merge 1 commit into
trunkfrom
claude/drop-status-ready-gate

Conversation

@Zlyzart

@Zlyzart Zlyzart commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Removes the manual status:ready promotion step from the agent pipeline
  • /implement-next now picks issues directly from status:refined (unrefined → refined → in-progress)
  • Deletes ready-author-guard.yml (no longer needed)
  • Updates reconciler, agent-refine, labels, and docs accordingly

Files changed

File Change
.claude/commands/implement-next.md Selector targets status:refined; claim/failure paths updated
.github/workflows/ready-author-guard.yml Deleted
.github/workflows/reconciler.yml Deferred/stale reclaims restore status:refined; digest drops ready
.github/workflows/agent-refine.yml Remove status:ready from skip guard; update prompt
.github/labels.yml Remove status:ready label; update status:refined description
docs/agent-pipeline.md Update flow, lifecycle, threat model, setup, rollout

Gate note

Edits to .github/workflows/ trigger gate-guard. Owner approval required to merge.

🤖 Generated with Claude Code

…us:refined

Removes the manual `status:ready` promotion step. The local implementer
(`/implement-next`) now picks issues directly from `status:refined`, so
the flow is unrefined → refined → in-progress without a human click in
between.

Changes:
- implement-next.md: selector targets status:refined, claim removes
  status:refined, failure re-queues to status:deferred (reconciler
  re-promotes to status:refined)
- reconciler.yml: deferred and stale reclaims restore status:refined
  (not status:ready); weekly digest drops the ready count
- agent-refine.yml: remove status:ready from already-past-refinement
  guard; update prompt to drop the "human should apply status:ready" note
- ready-author-guard.yml: deleted (no status:ready to guard)
- labels.yml: remove status:ready label; update status:refined description
- docs/agent-pipeline.md: update flow diagram, lifecycle, threat model,
  setup, and rollout sections

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Gate integrity: this PR changes CI/test machinery — an owner must approve it to unblock (CI re-runs on approval). If unintended, restore the original gate instead.

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