feat(work-items): show "I read this item as" above the attended Proceed prompt

Closed Beginner friendly
  • Is something wrong?
#11,864 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #11905 by @melodic-automation-lanes — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python, shell
Domain
developer-experience

Research direction

Start with the attended "Proceed?" prompt in plugins/work-items/skills/work/SKILL.md and add the one-line I read this item as: restatement above it, leaving autonomous runs unchanged. Add a case under plugins/work-items/evals/ that expects the line before the prompt, then run the validator in plugins/evals/skills/validate/scripts/validate-cases.py and plugins/skill-quality/scripts/check-skill.sh. Done when those checks pass and a changelog fragment is included.

Written by the indexing model from the issue text.

Description

agent-ready priority: medium status: ready

Problem

/work-items:work's attended path asks "Proceed?" without restating what it understood the item to
ask, so a misread is caught only after work starts.

Origin: Matt's restate (D104, Q171).

Fix

Above the attended "Proceed?" prompt, print one line: I read this item as: <goal; done when>,
drawn from the item's brief. Autonomous runs are unchanged.

Done when

  • plugins/work-items/skills/work/SKILL.md states the I read this item as: <goal; done when> line above the attended "Proceed?" prompt (git grep -c 'I read this item as' 899a46af84 -- plugins/work-items/skills/work prints nothing; the same grep on the merged head prints a count).
  • A case under plugins/work-items/evals/ expects the line before the prompt; python3 plugins/evals/skills/validate/scripts/validate-cases.py plugins/work-items/evals exits 0.
  • bash plugins/skill-quality/scripts/check-skill.sh plugins/work-items/skills/work exits 0.
  • A work-items changelog fragment is present and bash scripts/check-changelog-fragments.sh passes.

Parent: #7578

Dominant language
Shell
Stars
22
Forks
2
Avg merge
1h 38m
Merged PRs (30d)
911

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.