agentsclimarketplace

Implementation notes

Skill MaybeMonad/skills/skills/unknown-reduction/implementation-notes

Install
npx -y skills add MaybeMonad/skills --skill implementation-notes

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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

During-implementation notes workflow for logging decisions, deviations, edge cases, conservative choices, evidence, and open questions while an agent implements a plan. Use when the user asks to keep implementation-notes.md or notes, when unknowns may appear during implementation, when the plan may need to change, or when a future attempt should learn from this run.

SKILL.md

1.9 KB, 320 tokens by cl100k_base, as published. Nobody here has run it

Implementation Notes

Use this skill to preserve what the agent learns while implementing. The notes are a temporary map of where the actual territory differed from the plan.

Workflow

  1. Create or maintain implementation-notes.md only when useful or requested.
  2. Record the plan snapshot:
    • Goal, key constraints, planned approach, and validation gates.
  3. Log decisions made without user input:
    • Decision, reason, alternatives, and why the chosen option is conservative.
  4. Log deviations:
    • Original plan, discovered edge case, new approach, and user-visible impact.
  5. Log evidence:
    • Files inspected, commands run, tests, runtime observations, screenshots, or source links.
  6. Log open questions:
    • Questions that remain after implementation, with whether they block release, review, or a follow-up.
  7. Before final response, summarize the notes or package them into a handoff.

Suggested File Shape

# Implementation Notes

## Plan Snapshot

## Decisions

## Deviations

## Edge Cases

## Evidence

## Open Questions

## Next Prompt

Rules

  • Keep notes factual and short. Do not turn them into a diary.
  • Surface deviations immediately when they change architecture, data shape, user-facing behavior, risk, or scope.
  • If the deviation is local and conservative, log it and keep moving.
  • Remove temporary notes if they are not meant to remain in the repo.
  • If notes reveal the plan is wrong, update the plan before continuing.

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.