spec

Convert ideation artifacts into executable contracts with acceptance criteria and deferred decisions mapped to implementation slices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning vague ideas and design notes into a concrete, executable contract that guides implementation and verification.

Core Features & Use Cases

  • Refines concept artifacts into a stable implementation contract with fixed decisions, probe questions, and deferred decisions.
  • Aligns design docs with the actual development slice, enabling predictable handoffs and measurable progress.
  • Supports executable checks and acceptance criteria as the contract matures.

Quick Start

Instruct the agent to convert the current ideation into a formal spec and lock initial decisions.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn ideation and design notes into a testable spec?

To turn ideation into a testable spec, you refine concept artifacts into a stable implementation contract containing fixed decisions, probe questions, and deferred decisions mapped to a bounded development slice.

What is an executable contract for software implementation?

An executable contract is a concrete specification that guides implementation by aligning design docs with a bounded development slice, enabling predictable handoffs and measurable progress through defined acceptance checks.

How do I define acceptance checks that align with verification needs?

Defining acceptance checks aligned with verification needs requires establishing clear success criteria within a durable spec frontmatter, ensuring the contract matures alongside executable checks mapped to the implementation slice.

Can I lock initial design decisions to enable predictable handoffs?

Yes, you can lock initial design decisions by instructing the agent to convert current ideation into a formal spec, which stabilizes concept artifacts into fixed decisions for predictable development handoffs.

When do I need to map a bounded implementation slice to a design doc?

You need to map a bounded implementation slice to a design doc when refining vague ideas into executable contracts, ensuring the development scope aligns with verification needs and measurable progress.