`bdd-maintain` gives two orders for a destructive REMOVE
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, python
- Domain
- documentation, testing
Research direction
Start with agentic/.claude/skills/bdd-maintain/SKILL.md: line 106 says to run all three scripts before any REMOVE, while step 3 (line 38) runs find_unused_steps.py after scenarios are removed in step 2, and line 135 says to run it after removing deprecated scenarios. Rewrite line 106 to match that order, then extend agentic/.claude/skills/living-doc-shared/test_skill_doc_consistency.py to catch the contradiction. Done when the wording is consistent and that test passes; the evals and regression gate in agentic/docs/testing/ apply if a script or canon copy changes.
Written by the indexing model from the issue text.
Description
Description of Technical Debt
SKILL.md:106 says to run "All three" scripts before any REMOVE. Step 3 (:38) runs find_unused_steps.py after the
scenarios are removed in step 2, and :135 says to run it after removing the deprecated scenarios, "not before". A
model that follows :106 finds no unused steps and may remove the wrong things.
Impact of Technical Debt
- A destructive operation can remove the wrong code.
Category
Code Quality / Refactoring
Priority
High - Actively causing problems
Proposed Solution
Make :106 match the step order, and add a consistency check to agentic/.claude/skills/living-doc-shared/test_skill_doc_consistency.py. Re-measure the named evals by agentic/docs/testing/eval-protocol.md (two runs, one grader), and run the regression gate in agentic/docs/testing/baseline.md when a script or canon copy changes. Evals: bdd-maintain 1 and 5.
Effort Estimate
2 hours
Dependencies / Related
No response
Additional Context
Measured 2026-11-12 at living-doc 2df73dc. Re-check:
grep -n "All three" agentic/.claude/skills/bdd-maintain/SKILL.md
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 14m
- Merged PRs (30d)
- 27
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 AbsaOSS/living-doc
-
type:tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 78/100
AbsaOSS/living-doc#133 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
AbsaOSS/living-doc#130 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AbsaOSS/living-doc#129 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 5/5 Over a week Newbie friendliness 5/100
AbsaOSS/living-doc#136 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 4/5 1-2 days Newbie friendliness 18/100
AbsaOSS/living-doc#135 ·
Maintainers usually reply within 1 day
All issues in AbsaOSS/living-doc
Similar issues
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
JheysonJhordyHuarauyaRiquelme/sprocguard#18 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
dlq/synthpopcan#59 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mdn/translated-content#40220 ·
Maintainers usually reply within 4 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ETSInitiative/PETSIRD#243 ·
Maintainers usually reply within 1 day
-
deferred p2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cuadrao-ai/argus#2160 ·
Maintainers usually reply within 1 day