frink-evidence-pack

Name: frink-evidence-pack
Rating: 5 (1 reviews)
Author: FdoMillan

by @FdoMillan in Development

# Install this skill:

npx skills add FdoMillan/FRINK

Or install specific skill: npx add-skill https://github.com/FdoMillan/FRINK/tree/genesis/SKILLS/frink-evidence-pack

# Description

Compile a FRINK evidence pack after implementation and testing. Use to capture diffs, test results, logs, and reproduction steps so reviewers can verify changes.

# SKILL.md

name: frink-evidence-pack
description: "Compile a FRINK evidence pack after implementation and testing. Use to capture diffs, test results, logs, and reproduction steps so reviewers can verify changes."

FRINK Evidence Pack

Objective

Provide verifiable proof of work for an iteration.

Inputs

Diff or commit summary
Test outputs and logs
Manual verification notes and screenshots (if any)
Reproduction steps

Outputs

docs/frink/evidence/ITER-XXXX/README.md
Optional attachments (e.g., test_output.txt, screenshots/)

Procedure

Summarize code changes and affected files.
Record test suites run and results.
Document manual verification steps and observations.
Include relevant logs or metrics.
Provide copy/paste reproduction commands.
Redact secrets and sensitive data.

Guardrails

Do not run tests or modify code in this skill.
If evidence is insufficient, request additional validation.

# README.md

FRINK Codex Skills Suite

FRINK = Functional Recursive Iteration & Neural Knowledge

A project-agnostic skill suite for Codex that enforces a bounded, verifiable delivery loop. Each iteration must define scope, implement only that scope, verify, write a checkpoint, and attach evidence so progress is reviewable end-to-end.

Included skills

frink-orchestrator — Orchestrates the full FRINK loop
frink-task-list — Defines scope, dependencies, and DoD
frink-implementation-plan — Plans the technical approach before coding
frink-progress-checkpoint — Captures iteration state and updates task statuses
frink-evidence-pack — Collects diffs, tests, and reproduction steps
frink-walkthrough — Final milestone walkthrough and validation

Repository layout

SKILLS/
  frink-orchestrator/
    SKILL.md
  frink-task-list/
    SKILL.md
  frink-implementation-plan/
    SKILL.md
  frink-progress-checkpoint/
    SKILL.md
  frink-evidence-pack/
    SKILL.md
  frink-walkthrough/
    SKILL.md

Install in Codex

Copy the skill folders into one of Codex’s discovery locations:

Project scope: YOUR_REPO/.codex/skills/
User scope: ~/.codex/skills/

Example:

cp -R SKILLS/* YOUR_REPO/.codex/skills/

FRINK artifacts

When used, FRINK writes durable artifacts to the target repo:

docs/frink/
  artifacts/
    00_task_list.md
    01_implementation_plan.md
    99_walkthrough.md
  checkpoints/
    ITER-0001.md
  evidence/
    ITER-0001/
      README.md
      test_output.txt           (optional)
      screenshots/             (optional)

Quick start prompts

"Run frink-orchestrator. Spec is in docs/spec.md. Produce Task List and Implementation Plan for the smallest shippable slice. Keep scope tight and create checkpoint + evidence pack."
"Use frink-progress-checkpoint and frink-evidence-pack for the current branch. Provide reproduction steps and a diff summary."

Notes

Each skill is intentionally small and composable.
Artifacts must be truthful; evidence packs must include copy/paste commands.

# Supported AI Coding Agents

This skill is compatible with the SKILL.md standard and works with all major AI coding agents:

⚡ Amp 🚀 Antigravity 🤖 Claude Code 🦀 Clawdbot 📝 Codex ▶️ Cursor 🤖 Droid 💎 Gemini CLI 🐙 GitHub Copilot 🪿 Goose 📊 Kilo Code 🔧 Kiro CLI 💻 OpenCode 🦘 Roo Code 🌲 Trae 🏄 Windsurf

Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.