agentsclimarketplace

Evidence

Skill JarrydAdaens/agentic_rails_tooling/archived/skills/evidence

The right rail of Agentic Rails: Reusable skills, agent personas, rules, and workflows for agentic coding IDEs — the tooling rail of the Agentic Rails framework.

Install
npx -y skills add JarrydAdaens/agentic_rails_tooling --skill evidence

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

  • 1 stars1 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

Use this skill when the user explicitly asks for evidence capture, provenance, validation evidence, source-grounded proof, or an evidence.md file during an agentic task. It maintains an opt-in evidence record — by default the `## Evidence / References` section inside the active plan.md, or a standalone evidence.md when explicitly requested or genuinely required for audit — that indexes changed files, commits, checks, planning inputs, and unverified claims.

SKILL.md

3.9 KB, as published. Nobody here has run it

Evidence

Maintain a durable provenance record for implementation work: what proves the work happened and what remains unverified.

This skill is opt-in and should not be created by default for every plan. When it is active, default to writing inline into the active plan, not a standalone file.

Artifact

Default: write into plan.md. If the target repository follows Agentic Rails and an active implementation-plan folder is identifiable, record evidence inside that plan's ## Evidence / References section (see rails-planning's plan-template.md). Do not create a standalone evidence.md for this case.

Standalone evidence.md, only when justified. Create a separate evidence.md file only when:

  • the user explicitly asks for a standalone evidence file, or
  • the work is high-risk enough, or needs strong enough audit/provenance, that a dedicated file is genuinely warranted (for example, a large or phased story already using standalone sidecar files).

When a standalone file is warranted, it must live beside plan.md in the same story folder — context/implementation-plans/<milestone-slug>/<story-slug>/evidence.md — never in context/ root. Load references/path-selection.md if the correct location is not obvious.

Content shape, whether inline (as subsections under ## Evidence / References) or in a standalone file:

## Evidence / References

### Source Files Changed

### Commits

### Validation

### Planning Inputs

### Known Unverified Claims

Operating Model

  1. Identify the target project root and whether an active plan is identifiable.
  2. Default to recording inline in that plan's ## Evidence / References section. Only fall back to a standalone evidence.md per the criteria above.
  3. Record changed files with short source-grounded summaries.
  4. Record commits when commits exist; use pending when work is not committed.
  5. Record commands, tests, builds, manual checks, and review passes with pass/fail/blocked/not-run status.
  6. Record planning inputs that materially shaped the work.
  7. Record important unverified claims instead of presenting them as proven.

Evidence Standard

Useful evidence is specific and inspectable:

  • Link or name the file, command, commit, plan, or manual check.
  • Include the result, not just that a check was attempted.
  • Mark blocked or skipped validation honestly.
  • Separate verified facts from inferred or unverified claims.

Optional Sibling Artifacts

If thinking.md, complaining.md (or a plan's ## Complaints / Friction section), or an execution log (plan.md's ## Execution Log section, or standalone implementation-log.md) exists for the same work, use them as inputs when they contain source-grounded evidence. Do not create missing optional artifacts unless their skills are active.

Validation

  • Evidence was recorded inline in plan.md's ## Evidence / References section unless a standalone evidence.md was explicitly requested or genuinely justified.
  • Any standalone evidence.md lives beside plan.md in the same story folder, not in context/ root.
  • Validation entries distinguish passed, failed, blocked, and not-run checks.
  • Unverified claims are explicitly labeled.
  • Optional sibling artifacts were referenced only when present or active.

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.