feat(planning): make plans reviewable in a minute with behaviour-first summaries and code-shape views
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- html, markdown
调研方向
Start with PLAN.md and the /visualization:visualize code-shape views, then with the /planning:plan arbiter for Q12. This is not a first-timer task: it is blocked by #6926 and #6924, and Q12-Q14 are unresolved and reserved for the maintainer. Done means the issue is re-decomposed into smaller slices once the plan exists and the acceptance criteria are met.
由索引模型根据 Issue 内容生成。
描述
Parent
Refs #6917
What to build
Make a plan reviewable in a minute. PLAN.md stays the record; HTML is only a view of it.
- PLAN.md opens with a behaviour-first summary, split by behaviour rather than file, layer or order; its claims seed decompose's slices.
- Plans use
/visualization:visualize's code-shape views (call trees, file trees, diffs over them) with@ path:lineanchors, readable in a terminal. - The plan view is generated from PLAN.md, with links to the Brief, decisions and acceptance criteria.
- Later: mockups and state machines in the view; word budgets for plan prose.
This is too large for one session: re-decompose it once its plan exists, after the deferred questions are settled:
- Q12: which visual components ship, and when (arbiter:
/planning:plan) - Q13: prose standard for plans, STE or our own writing rules (user-reserved)
- Q14: may answers given in an HTML plan view write back into PLAN.md (user-reserved)
Key interfaces
None
Acceptance criteria
- PLAN.md opens with a behaviour-first summary
- Plans use the visualize code-shape views with
@ path:line - The plan view is generated from PLAN.md, linking the Brief, decisions and acceptance criteria
- Q12, Q13 and Q14 are answered before the visual work is sliced
- The PR body carries
Refs: #6917
Out of scope
- HTML as the record (the rendered-views convention stays)
- Any dependency on html-plan's runtime
Blocked by
- #6926
- #6924
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 8 小时 27 分钟
- 30 天内合并 PR
- 957
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
priority: medium
难度 2/5 1-3 小时 新手友好度 68/100
melodic-software/claude-code-plugins#7351 · 2 条评论 ·
维护者通常 1 天内回复
-
agent-ready priority: high work-class: scoped
难度 2/5 1-3 小时 新手友好度 74/100
melodic-software/claude-code-plugins#7312 · 3 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 76/100
melodic-software/claude-code-plugins#7288 · 2 条评论 ·
维护者通常 1 天内回复
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail threshold未关闭needs-human
难度 2/5 1-3 小时 新手友好度 78/100
melodic-software/claude-code-plugins#7286 · 2 条评论 ·
维护者通常 1 天内回复
-
priority: low
难度 2/5 1-3 小时 新手友好度 76/100
melodic-software/claude-code-plugins#7282 · 2 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
Sourced-library load-guards use a top-level `return` that errors on direct execution (repo-wide)未关闭
难度 2/5 1-3 小时 新手友好度 62/100
rossoctl/automation#115 ·
维护者通常 3 天内回复
-
loongarch64: `unsupported linker arg: --no-rosegment` with rustc 1.100可能已有人在做 @monosans 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
rust-cross/cargo-zigbuild#503 ·
维护者通常 1 天内回复
-
area/CubeMaster bug needs-triage
难度 2/5 1-3 小时 新手友好度 62/100
TencentCloud/CubeSandbox#1959 ·
维护者通常 1 天内回复
-
netbox status: backlog topic: testing type: housekeeping
难度 2/5 1-3 小时 新手友好度 70/100
netbox-community/netbox#23395 ·
维护者通常 1 天内回复