rct-methodology

Converts specification documents into phase-driven checklists with enforcement gates.

19|5|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/lukacf/meerkat --skill rct-methodology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rct-methodology
Source: https://github.com/lukacf/meerkat/tree/main/.claude/skills/rct-methodology
Command: npx skills add https://github.com/lukacf/meerkat --skill rct-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates AI development governance by turning specifications into executable, phase-driven checklists and gates, ensuring representation contracts are validated before implementation.

Core Features & Use Cases

  • Transform specifications into agent-ready checklists with clearly defined gates (Gate 0–Gate 3).
  • Provide Luka Loop scaffolding and artifact layout (.rct/spec.yaml, .rct/plan.yaml, .rct/checklist.yaml) to guide implementation.
  • Support independent reviewer prompts and automated rendering of progress to .rct/outputs/CHECKLIST.md.
  • Offer strict, auditable process for enforcing spec compliance and preventing deferrals.

Quick Start

Scaffold the Luka Loop in your repository and start the gated implementation workflow.

Frequently Asked Questions about rct-methodology

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

FAQPage Schema
How do I turn a project specification into a gated checklist workflow for AI agents?

To convert a specification into a gated checklist, this methodology creates .rct/spec.yaml, .rct/plan.yaml, and .rct/checklist.yaml files, enforcing phase-driven gates and representation contracts before implementation.

What are phase-driven gates in AI development governance?

Phase-driven gates are strict checkpoints (Gate 0–Gate 3) that validate specification compliance. They use independent reviewer prompts to ensure representation contracts are met before behavior implementation proceeds.

How do I prevent must-have feature deferral during AI code generation?

To prevent must-have feature deferral, you apply strict governance checklists that validate completion via rendered outputs in .rct/outputs/CHECKLIST.md, ensuring all specified features pass gate reviews without deferral.

Does the RCT methodology require independent reviewer prompts for gate reviews?

Yes, the RCT methodology requires independent reviewer prompts to run gate reviews. This ensures auditable process enforcement and validates that representation contracts are satisfied before implementation behavior.

Can I use gated checklists to maintain artifact isolation in my repository?

Yes, you can use gated checklists to maintain artifact isolation by storing all governance files within the .rct/ directory, preventing spec deferral and rendering progress outputs cleanly to .rct/outputs/.

When should I not use a strict checklist methodology for AI development?

You should not use a strict checklist methodology for rapid prototyping or exploratory development where spec requirements fluctuate, as the phase-driven gates and representation contract enforcement demand fixed specifications.