impl

Translate implementation contracts into code, configs, tests, and artifacts.

9|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/corca-ai/charness --skill impl-corca-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impl
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/skills/impl
Command: npx skills add https://github.com/corca-ai/charness --skill impl-corca-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Use this when work should move from an implementation contract into code, config, tests, or operator-facing artifacts. It also provides a bootstrap path when no canonical contract exists and mandates honest progression with robust verification and contract syncing as reality changes.

Core Features & Use Cases

  • Bootstraps the smallest honest contract when no canonical contract exists and keeps it aligned with the current slice.
  • Verifies progress aggressively, closes the loop with premortem-style review, and progressively updates the contract as work evolves.
  • Supports projects where specs and implementations diverge, enabling smooth transition from contract to executable artifacts (code, configs, tests, docs).

Quick Start

Provide the agent with the current implementation contract and ask it to bootstrap the smallest honest slice.

Frequently Asked Questions about impl

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

FAQPage Schema
How do I translate an implementation contract into executable code slices?

When specs and implementations diverge, this process enforces smooth transitions from contract to executable artifacts. It continually syncs the canonical contract as work evolves, ensuring alignment with fixed decisions and acceptance checks.

Can I bootstrap a project slice if no canonical spec or contract exists?

Yes, you can bootstrap the smallest honest contract when no canonical spec exists. The process mandates honest progression and progressively updates the contract as reality changes, keeping it aligned with the current executable slice.

What is a premortem review and how does it verify implementation contracts?

A premortem review closes the verification loop by aggressively identifying potential failures in the implementation contract before execution. It ensures progress aligns with fixed decisions and acceptance checks while enforcing contract honesty.

What's the best way to keep code, tests, and configurations aligned with a changing contract?

The best way to keep artifacts aligned with a changing contract is through aggressive verification and premortem review. This updates the canonical artifact accordingly whenever scope or reality changes, ensuring executable slices remain honest.