UC-17.8 研发闭环（反馈 → 设计 → 排期）：需求录入 + UI 先行原型
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 969
Description
人类 2026-09-04 交办：按《研发闭环（Feedback → Design → Dev）需求文档 v1.0》（PDF）改进反馈提交、需求设计和后台的反馈/需求管理。
本 issue 追踪第一步（ad-hoc 交办，见 `.harness/instructions/ad-hoc-fix-pr-sop.md`）：
- [x] 需求转录为 `phases/phase-03-reuse-and-governance/requirements/17-gov/uc-17-8-研发闭环-反馈到设计到排期.md`
- [x] ui-prototyper 用真实组件 + mock 做出四块屏（快速反馈弹窗改造 / 反馈草稿 / 运营收件箱看板 / PM 设计工作台），截图与待确认清单在 `ui-preview/feedback-design-loop/README.md`
- [x] ui-prototyper 引入 anthropics/skills 的 frontend-design skill（人类指令）
- [ ] 人类核对 README 待确认清单（标题字段 / 旧后台替换还是并存 / 弹窗高度 / 附件契约 4→5 / Provider 是否上提到 AppShell）
- [ ] 契约束切分 + design-signoff（ADR-023），之后 requirement-author 生成 feature
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading phases/phase-03-reuse-and-governance/requirements/17-gov/uc-17-8-研发闭环-反馈到设计到排期.md and ui-preview/feedback-design-loop/README.md, then review .harness/instructions/ad-hoc-fix-pr-sop.md. Done means the README questions are confirmed, contract constraints are split, design-signoff for ADR-023 is complete, and the requirement-author can generate the feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, documentation, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100