crafter-buffer

Appends NDAP UAT and Gap findings to per-run JSONL buffers.

2|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/richardriman/crafter --skill crafter-buffer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crafter-buffer
Source: https://github.com/richardriman/crafter/tree/main/skills/crafter-buffer
Command: npx skills add https://github.com/richardriman/crafter --skill crafter-buffer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Append a UAT or Gap entry to the current run's buffer file under .crafter/run/<task-id>/ to preserve manual QA findings and deferred follow-ups without blocking the workflow.

Core Features & Use Cases

  • Append a single NDJSON line to <run-dir>/uat-buffer.jsonl or <run-dir>/gaps-buffer.jsonl, creating the files if needed.
  • Support both UAT and Gap entries with structured fields (id, kind, created_at, created_by, task_id, title, source, verify for UAT; detail and followup for Gap).
  • Enable long-running or unattended runs to persist findings for later review and action.

Quick Start

Append a UAT or Gap entry to the current per-run buffer located at .crafter/run/<task-id>/.

Frequently Asked Questions about crafter-buffer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist QA findings during unattended Crafter runs?

You can persist QA findings during unattended Crafter runs by appending them as NDJSON records into uat-buffer.jsonl or gaps-buffer.jsonl under .crafter/run/<task-id>/, preserving manual observations without blocking the workflow.

What is the difference between UAT and Gap buffer entries in NDJSON logging?

UAT buffer entries in NDJSON logging contain structured fields including id, kind, source, and verify, whereas Gap entries include detail and followup fields to capture deferred follow-ups across implementer, verifier, and reviewer roles.

How do I append a UAT entry to a per-run buffer file?

To append a UAT entry to a per-run buffer file, append a single NDJSON line with structured fields to uat-buffer.jsonl within the .crafter/run/<task-id>/ directory, which is created on demand if it does not exist.

Can I use header markers to detect NDJSON buffer file types automatically?

Yes, you can use header markers to detect NDJSON buffer file types automatically, as the implementation supports header marker detection to enable tooling to identify whether a file contains UAT or Gap scenarios.

Does crafter-buffer work for manual QA runs or only unattended workflows?

crafter-buffer works for both unattended and manual Crafter runs, allowing implementer, verifier, and reviewer roles to persist UAT and Gap findings into the designated buffer files for later review and action.