prose-to-checks

Convert always-testable prose rules in pack documentation into automated checks.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill prose-to-checks-missingbulb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prose-to-checks
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/claudinite-growth/skills/prose-to-checks
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill prose-to-checks-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pack documentation accumulates prose rules that are always-testable but were never converted into automated checks, leaving enforcement to memory and review discipline instead of deterministic verification. ## Core Features & Use Cases - Rule triage and classification: Routes each candidate rule by where its violation leaves a mark (tree, change, tool call, transcript) into classes A through H, deciding whether it becomes a declared check, a scoped rule, a triggered skill, or stays prose. - Check authoring discipline: Enforces fixture-first development where a violating fixture must fail and a clean one must pass before any converted check ships, with severity, since-dating, and allowlist guidance. - Deletion test: Removes prose fully covered by a landed check so rules live in exactly one place and cannot drift. - Use Case: During a weekly sweep over a repo's packs, audit every RULES.md and SKILL.md for convertible rules, author proven checks for the strongest candidates, and delete the now-redundant prose in a single bounded PR. ## Quick Start Audit the packs in this repository for prose rules that can be converted into automated checks and convert the strongest candidates with proving fixtures.

Frequently Asked Questions about prose-to-checks

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

FAQPage Schema
How do I convert prose rules into automated checks?▼

Triage each rule by where its violation leaves a mark, then author a declared check in declared-checks.json or a rule module in pack.mjs. Write a violating fixture first and see it fail, ship at real severity with a since date, and delete the prose the check now covers.

What makes a prose rule a good candidate for check conversion?▼

A rule is convertible when it constrains a static signature in the repository artifact that a post-hoc scan could observe, such as filename conventions, forbidden patterns, or cross-file invariants. Rules about in-flight process, judgment calls, or runtime-only behavior stay as prose.

Should product requirements be converted into pack checks?▼

No. Product statements about what the product does belong in the executable spec and its test suite, not in pack checks. The discriminator is whether the rule would be wrong if the product changed its mind; if so, it is a requirement and must not be converted.

When should a converted check be advisory instead of blocking?▼

Use advisory severity when the rule is directional by kind, or when the condition is blocking-grade but irreversible by the time it is observable, such as an append-only transcript or published artifact. Blocking findings that no edit can retract never converge.

Why re-derive checkability verdicts instead of trusting prior sweep records?▼

A not-statically-checkable verdict reflects the tree's shape when it was recorded, and removals or consolidations can collapse the entry points that made a rule untestable. Re-ask the check-the-world question against today's sources rather than trusting the recorded answer.