fix(planning): export each decision once in its current form, without superseded or raw duplicate lines
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start in plugins/planning/surface/exporters.py, where answered rows are appended as - Q<N> bullets after the restated constraints; find where supersededBy rows are routed to Out-of-scope and where ### Decisions is rendered. Read plugins/planning/skills/plan/context/tag-decisions.md:7 for the semantics of withdrawn vs approved, then extend plugins/planning/surface/test_exporters.py with the two named tests (Q13 superseded by Q28, and no duplicated decision lines). Done when python3 -m unittest discover -s plugins/planning/surface -p 'test_exporters.py' passes and a changelog fragment is added; recheck line numbers against origin/main first.
Written by the indexing model from the issue text.
Description
Problem
#6051 finding E2. plugins/planning/surface/exporters.py appends - Q<N> <short>: <readable> for every answered row after the restated constraints, superseded and refined ones unmarked (39 bullets in the audited run). A supersedes row becomes withdrawn and exports into Out-of-scope, which plugins/planning/skills/plan/context/tag-decisions.md:7 treats as approved.
What to build
- Drop an answered row's raw line when the restated constraints or the
### Decisionssection (from the sibling slice) already carry it. - Stop exporting
supersededByrows to Out-of-scope; they stay in the ledger. - In
### Decisions, mark a true replacementreplaces Q<N>.
Done when
- A
plugins/planning/surface/test_exporters.pytest with Q13 superseded by Q28 asserts Q13's text appears in neither Constraints nor Out-of-scope, and Q28 appears once. - A test asserts no decision line appears twice in the exported Brief.
-
python3 -m unittest discover -s plugins/planning/surface -p 'test_exporters.py'exits 0. - Planning changelog fragment present.
Split from the parent by the owner's HITL session (2026-10-24) under Q93 (split before any run). Paths and line numbers checked on origin/main 2f6b81e2ca; recheck before building.
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 3h 42m
- Merged PRs (30d)
- 938
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from melodic-software/claude-code-plugins
-
admission-deferred priority: medium status: ready work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
melodic-software/claude-code-plugins#9914 · 1 comment ·
Maintainers usually reply within 1 day
-
priority: low status: ready work-class: mechanical
Difficulty 1/5 Under an hour Newbie friendliness 88/100
melodic-software/claude-code-plugins#9911 · 2 comments ·
Maintainers usually reply within 1 day
-
admission-deferred needs-human needs-triage status: needs-decision
Difficulty 2/5 1-2 days Newbie friendliness 78/100
melodic-software/claude-code-plugins#9865 · 1 comment ·
Maintainers usually reply within 1 day
-
priority: medium status: needs-decision work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
melodic-software/claude-code-plugins#9855 · 2 comments ·
Maintainers usually reply within 1 day
-
priority: medium status: needs-decision work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#9842 · 4 comments ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
resource-submission validation-passed
Difficulty 1/5 Under an hour Newbie friendliness 67/100
hesreallyhim/awesome-claude-code#3264 · 1 comment ·
Maintainers usually reply within 1 day
-
area: install bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
armbian/build#11107 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
wimpysworld/deb-get#2069 ·
Maintainers usually reply within 5 days