finish-check

Validate loom pipeline outputs and generate demo-checklist.md and risks.md.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ajmeyers42/loom --skill finish-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-check
Source: https://github.com/ajmeyers42/loom/tree/main/skills/finish-check
Command: npx skills add https://github.com/ajmeyers42/loom --skill finish-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads and validates pipeline outputs to surface a definitive pre-demo readiness package, including a go/no-go decision and a concrete checklist.

Core Features & Use Cases

  • Aggregates demo pipeline outputs (discovery, platform audit, demo script, data model, ML config, current state) into a unified readiness artifact.
  • Performs deterministic compliance checks and outputs a pre-demo checklist, known risks, and a go/no-go recommendation.
  • Generates ready-to-present outputs (demo-checklist.md and risks.md) that SEs can use the day-of-demo.

Quick Start

After weave outputs exist, run the finish-check skill to generate the pre-demo checklist and risk register for your engagement.

Frequently Asked Questions about finish-check

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

FAQPage Schema
What is a pre-demo readiness check and do I need it for my customer engagement?

A pre-demo readiness check validates pipeline outputs to surface a definitive go/no-go decision. You need it for customer engagements preparing for a live demo to verify required artifacts exist and are schema-consistent.

How do I generate a demo readiness checklist and risk register from pipeline outputs?

To generate a demo readiness checklist and risk register, run the finish-check process after your loom pipeline outputs exist. It aggregates discovery, platform audit, demo script, data model, ML config, and current state into deployable demo-checklist.md and risks.md files.

What pipeline artifacts are required to produce a go/no-go recommendation for a live demo?

Producing a go/no-go recommendation requires access to discovery, platform audit, demo script, data model, ML config, and current state artifacts. These pipeline outputs are consolidated to perform deterministic compliance checks and verify version gate consistency.

Can I use pre-demo checklist validation if my pipeline outputs are missing the data model or ML config?

Pre-demo checklist validation requires discovery, platform audit, demo script, data model, ML config, and current state artifacts. Missing any of these pipeline outputs prevents the deterministic compliance checks from generating an accurate go/no-go recommendation and risk summary.

What files do I get from running a pre-demo readiness check?

Running a pre-demo readiness check produces two deployable outputs: demo-checklist.md and risks.md. These ready-to-present files provide software engineers with a deterministic checklist and known risks for day-of-demo use.