sketch

Writes single-pass pre-commitment design sketches to dated Markdown files.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill sketch-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sketch
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/families/ok-planner/skills/sketch
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill sketch-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It captures a feature idea in a structured design document before any commitment to build, letting you think about, share, or revisit the idea without running a full planning ceremony or writing any code. ## Core Features & Use Cases - Single-pass sketch generation: Produces one dated Markdown sketch in .ok-planner/sketches/ with sections for the idea, shape, open questions, risks, and explicit exclusions. - Light codebase grounding: Skims existing design concept catalogs and greps @concept: tags so the sketch respects established terminology and boundaries. - Clear boundaries: Never edits code, never files issues, never invokes sprint planning — it records assumptions as open questions instead of asking. - Use Case: You have a rough idea for a new caching layer. Invoke the sketch command, and receive a dated design document you can sit on, share with teammates, or later promote into a full sprint plan. ## Quick Start Ask the assistant to run /sketch and describe the feature idea you want captured as a design sketch.

Frequently Asked Questions about sketch

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

FAQPage Schema
How do I create a design sketch before committing to build a feature?▼

Invoke the /sketch slash command with your topic, and it writes a dated Markdown sketch to .ok-planner/sketches/ covering the idea, shape, open questions, and risks. It makes reasonable assumptions instead of asking questions, and never authorizes implementation.

What is the difference between a design sketch and sprint planning?▼

A sketch is a single-pass, pre-commitment document with no review loop and no authorization to build. Sprint planning via /plan-sprint includes intake dialogue, corpus deltas, issue resolution, and sign-off for work you intend to build.

Does the sketch command modify code or file issues?▼

No. The sketch skill never edits code, never writes to the design corpus, and never files issues into the intake. It only creates one Markdown file in the sketches directory and ends the turn.

When should I not use a design sketch?▼

Skip the sketch when you already intend to build the work — go directly to /plan-sprint for full intake and sign-off. A sketch is for speculative or early ideas you want to think about, share, or revisit later.

What happens to a sketch when the idea is taken up for planning?▼

When the idea enters /plan-sprint, that ceremony's terminal phase moves the individual sketch file to history/sketches/. Abandoned sketches are moved there by hand, never wholesale.