agentsclimarketplace

Implement client feedback

Skill jqaisystems/jqai-ai-skills/skills/implement-client-feedback

MIT reusable AI skills for Codex and Claude Code: safe publishing, research briefs, case studies, web scraping, copy cleanup, and release automation.

Install
npx -y skills add jqaisystems/jqai-ai-skills --skill implement-client-feedback

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Convert client revision notes into scoped implementation work with traceable decisions and verification. Use when a user provides comments, marked-up files, approval notes, or a feedback handoff and asks to implement changes, preserve approved elements, enforce exclusions, prepare a new version, or prove that every requested item was handled.

SKILL.md

3.1 KB, as published. Nobody here has run it

Implement Client Feedback

Turn client language into a controlled implementation contract, apply the authorized changes, and verify the result against the feedback source.

1. Establish the authoritative feedback set

  • Confirm the project root, current artifact or version, feedback source, and requested outcome.
  • Read the latest approved brief, feedback, current implementation, and relevant handoff material before changing files.
  • Treat the latest explicit decision as authoritative when it overrides earlier direction.
  • Preserve literal replacement text, names, exclusions, filenames, and approved claims.

2. Build the feedback matrix

  • Use assets/feedback-implementation-brief.md.
  • Classify every item as change, keep, remove, exclude, question, or future.
  • Record the literal instruction, minimal interpretation, target, acceptance evidence, and status.
  • Keep rejected concepts in a prominent exclusion list so older files or templates cannot reintroduce them.
  • Separate client requests from optional internal improvements.

3. Resolve only material ambiguity

  • Inspect the current artifact to resolve locations, nearby patterns, and implementation details.
  • Record small reversible assumptions that cannot change the intended outcome.
  • Ask before choosing a visual direction, changing approved scope, removing a public route, altering rights or deliverables, or contradicting literal feedback.
  • Do not turn a focused revision into a redesign.

4. Implement with controlled scope

  • Follow the project's existing architecture, versioning, and file conventions.
  • Start from the latest approved foundation.
  • Preserve approved elements and unrelated user-owned changes.
  • Apply only confirmed changes and keep excluded items absent.
  • Use the appropriate project tools for code, copy, images, documents, or website work.
  • Do not deploy, publish, upload, send, or change external permissions unless the user explicitly authorizes that separate action.

5. Verify every feedback item

  • Check each matrix row against the final files or rendered result.
  • Confirm additions, exact replacements, removals, preserved elements, and exclusions.
  • Run checks appropriate to the artifact, such as syntax, build, route, browser, dimensions, contrast, packaging, or document inspection.
  • Mark every item verified, partial, blocked, or awaiting client.
  • Do not call the revision complete while a required item is partial or unverified.

6. Report the review state

Return the implementation-brief location, version or artifact location, changed items, verification results, preserved exclusions, unresolved questions, and next client-review action.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.