agentsclimarketplace

Retain

Skill Jed-Tech/spar-kit/Research/research/example skills/retain

Specify → Plan → Act → Retain: SPAR-kit is a lightweight workflow that helps AI agents align with your intent, plan clearly, act with less drift, and retain durable project memory.

Install
npx -y skills add Jed-Tech/spar-kit --skill retain

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

  • 16 stars16 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

Finalizes documentation for a completed change under Docs/<scope>/Specs/<change-name>/. Aligns <change-name>_spec.md with final behavior, proposes broader doc updates for approval, and moves the change folder to Archive. Use after implement-change when implementation is done and the user wants cleanup and durable docs.

SKILL.md

2.7 KB, as published. Nobody here has run it

Document change

Turn completed implementation into clean, accurate, durable knowledge: honest <change-name>_spec.md, captured decisions, broader doc updates only with approval, then archive the change folder.

Inputs

  • Docs/<scope>/Specs/<change-name>/<change-name>_spec.md
  • Docs/<scope>/Specs/<change-name>/plan.md
  • Completed code changes
  • Repository documentation (e.g. README, Docs/technicalBrief.md, setup or usage docs)

Outputs

  • Finalized <change-name>_spec.md (matches actual behavior)
  • Optional updates to broader docs (after approval)
  • Archived folder: Docs/<scope>/Archive/<change-name>/ (contents moved from Specs/)

Workflow

1. Review implementation vs spec

  • Compare implemented behavior with <change-name>_spec.md
  • Note mismatches, missing decisions, outdated assumptions

2. Update <change-name>_spec.md

  • Reflect final behavior (spec must match reality, not original guesses)
  • Update Decisions, Constraints, Success Criteria as needed
  • Resolve or remove stale Open Questions
  • Keep intent-focused; no step-by-step implementation in the spec

3. Identify broader documentation impact

  • Use Documentation Impact in <change-name>_spec.md and the change itself
  • Consider: Docs/technicalBrief.md, README, setup/usage, developer notes

4. Propose broader documentation updates

  • List suggested edits clearly. Be concise.
  • Do not apply until the user approves

5. Apply approved updates

  • Update only what was approved; keep changes minimal and accurate

6. Final cleanup

  • <change-name>_spec.md: clear and complete
  • plan.md: final state (all done or explained); trim noise and temporary notes

7. Archive change

Move the entire folder:

Docs/<scope>/Specs/<change-name>/ → Docs/<scope>/Archive/<change-name>/

(Create Archive if missing.)

Rules

  • Spec describes final behavior; not a build log
  • No silent edits to README, technical brief, or other repo docs—approval first
  • Stay concise

Completion

Done when:

  • <change-name>_spec.md matches the implementation
  • Approved documentation updates are applied (or none were needed)
  • Change folder is under Archive/

Then:

  1. Summarize: key outcomes, doc updates made, archive path
  2. Confirm to user that implementation and documentation is complete.

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.