feat(backlog-triage): add spec-aware Decision Review#174
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
Walkthrough백로그 트리아지 기술에 스펙 기반 Decision Review 계층을 추가하여 이슈를 Do Now/Shape First/Defer/Drop 네 가지 버킷으로 분류한다. 증거 우선순위, 루브릭, 앵커-체크박스 계약, 그리고 graceful no-op 처리를 정의하고 예시 리포트로 검증한다. ChangesDecision Review 기반 우선순위 분류
Sequence DiagramsequenceDiagram
participant Sprint as Active Sprint
participant Charter as Charter
participant Specs as Spec Files
participant Snapshot as Issue Snapshot
participant Phase1 as Phase 1: Analyze
participant Report as backlog/triage/YYYY-MM-DD-report.md
Sprint->>Phase1: Context / burndown / active goals
Charter->>Phase1: Resolved charter constraints
Specs->>Phase1: Optional capabilities / system-map
Snapshot->>Phase1: Issues / relationships / stale signals
Phase1->>Phase1: Alignment Check<br/>(Coverage + Orphans + Contradictions)
Phase1->>Phase1: Decision Review<br/>(Evidence-driven classification)
Phase1->>Report: § Alignment<br/>§ Decision Review<br/> ├─ Do Now (evidence)
Phase1->>Report: § Decision Review<br/> ├─ Shape First (evidence)
Phase1->>Report: ├─ Defer (evidence)<br/> ├─ Drop / Close (explicit evidence)
Phase1->>Report: § Apply Checklist<br/>(Anchor-based checkboxes)
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fe455ead53
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - #76 - Current tree already contains `triage-apply.integration.test.js` plus SKILL/README run instructions; verify against the issue AC and close if no gap remains. | ||
| - #118 - Belongs to dev-relay documentation rather than dev-backlog's accepted capability set; close here after confirming the dev-relay-side follow-up exists. |
There was a problem hiding this comment.
When a maintainer uses this dogfood report as the acceptance surface, these Drop / Close recommendations cannot be accepted or applied because they are plain bullets, even though the new Decision Review reference says close proposals must keep the anchor-comment apply contract and that prose alone must not imply mutation. Since triage-apply.js only parses <!-- triage:... --> anchors followed by checkboxes, either add supported close/revisit anchors for these recommendations or reword them as non-mutating follow-up notes.
Useful? React with 👍 / 👎.
1 participant
Summary
Backlog artifact policy
This repo already tracks backlog/triage-config.yml, so backlog/ is not treated as entirely local-only here. This PR commits the final dogfood report and the matching snapshot it references. Regenerable relate/stale intermediate JSON files were intentionally excluded.
Verification
Related: #167, #168, #169, #170, #171, #172, #173
Summary by CodeRabbit
릴리스 노트
새로운 기능
--apply적용 흐름 구현문서