Tilly

Validate engineering ideas through adversarial CCM checks before coding.

Updated Jan 18, 2026

Search Tags:#planning #execution #session-management #guardrails #adversarial #ccm

Ready to run

npx skills add https://github.com/murillodutt/cellm --skill tilly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Tilly
Source: https://github.com/murillodutt/cellm/tree/main/cellm/skills/tilly
Command: npx skills add https://github.com/murillodutt/cellm --skill tilly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Tilly provides a disciplined, adversarial CCM workflow for engineering sessions, ensuring that ideas are validated against adversaries before any code is written, reducing rework and guiding safe, deliberate execution.

Core Features & Use Cases

Phase-gated session lifecycle (Opening Contract, CCM, plan-to-spec, implementation, post-execution, and handoff) to keep work aligned with objectives.
Adversarial validation loops: structured agent-based challenges that prune weak hypotheses early.
Relational persona injection and guardrails: standardized context framing, templates, and artifacts to ensure consistent collaboration.

Quick Start

Call /cellm:tilly to start a CCM-driven engineering session and follow the four opening sections.

Frequently Asked Questions about Tilly

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

FAQPage Schema

What is adversarial validation in software engineering planning?▼

Start a CCM-guided engineering session by calling the command and following the four opening sections. The workflow then progresses through CCM validation, plan-to-spec, implementation, post-execution, and handoff phases.

How does phase-gated session management work for engineering execution?▼

Phase-gated session management operates across Opening Contract, CCM, plan-to-spec, implementation, post-execution, and handoff phases. Strict guardrails and automated hooks enforce traceable, safe execution throughout the lifecycle.

Do I need to define specifications before starting CCM validation?▼

No, the plan-to-spec phase occurs after initial CCM validation. The workflow first validates ideas against adversaries through the Opening Contract, then transitions into generating specifications before any implementation begins.

When should I use adversarial CCM sessions instead of standard planning?▼

Use adversarial CCM sessions for serious engineering tasks requiring strict guardrails, provenance, and decision logging. It is designed to validate complex ideas before coding, reducing rework in deliberate, traceable execution.

Does the workflow enforce traceability for engineering decisions?▼

Yes, the workflow enforces traceability through provenance tracking, decision logging, and automated hooks. These guardrails ensure that all adversarial checks and phase-gated transitions are recorded for safe execution.