sketch

Create lightweight specification files with Context, Plan, constraints, and Done When sections.

5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/KodingDev/meridian --skill sketch-kodingdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sketch
Source: https://github.com/KodingDev/meridian/tree/main/skills/sketch
Command: npx skills add https://github.com/KodingDev/meridian --skill sketch-kodingdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a lightweight, disciplined spec workflow for small fixes that preserves rigor without the overhead of a full spec.

Core Features & Use Cases

  • Lightweight, repeatable sketch that captures context, plan, constraints, and acceptance criteria for small changes.
  • Enables self-review loops, gated approvals, and a clear handoff to the execution phase when needed.
  • Useful for single-file edits, quick fixes, or adjustments that require formalized planning but not full projects.

Quick Start

Create a new sketch file under .meridian/sketches with a date-based slug that describes the change, and fill in the Context, Plan, constraints, and Done When sections.

Frequently Asked Questions about sketch

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

FAQPage Schema
How do I plan a small code fix without writing a full specification?

Plan small fixes by creating a lightweight sketch file that captures Context, Plan, User Constraints, and Done When sections. This enforces rigor and gated approvals without the overhead of a full specification.

What is the best way to document context and acceptance criteria for quick single-file edits?

Document single-file edits using a sketch file under .meridian/sketches with a date-based slug. This fixed format ensures repeatable planning, captures constraints, and provides clear acceptance criteria for fast execution handoffs.

Does the sketch workflow support gated approvals for minor adjustments?

Yes, the sketch workflow supports gated approvals and self-review loops. It is designed for minor adjustments that require formalized planning, ensuring changes are reviewed before execution without needing a full project spec.

How do I structure a lightweight specification for fast handoff to execution?

Structure the specification by creating a sketch file in a consistent location with defined Context, Plan, User Constraints, and Done When sections. This fixed pattern enables quick, scoped changes and fast execution handoffs.

When should I use a sketch instead of a full specification for a code change?

Use a sketch for single-file edits or quick fixes that need formalized planning but not a full project specification. It provides a disciplined, lightweight workflow to maintain rigor for scoped changes without unnecessary overhead.