ok-planner

Maintains a design corpus of concepts, stories, decisions, and issue intake via slash commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It keeps a project's design knowledge — concepts, stories, decisions, and open questions — in a structured, versioned documentation corpus instead of scattered notes, and routes planning work through explicit slash commands. ## Core Features & Use Cases - Design corpus management: Bootstraps and maintains catalogs of concepts, agile-style stories with mandatory "so that" clauses, and technical decisions via /discover-design. - Issue intake and rulings: Holds one markdown file per open question in .ok-planner/issues/, with /verify-issues rewriting each into a ruling-ready narrative the owner accepts or overrides. - Pre-commitment sketching and task execution: /sketch externalizes an idea without authorizing a build, and /execute-tasks drains a task tracker's selected run with concurrent agents. - Use Case: A team inheriting an undocumented codebase runs /discover-design to extract the concept, story, and decision catalogs, then uses /verify-issues to resolve the judgment questions filed during discovery. ## Quick Start Run the /discover-design slash command to bootstrap the design corpus for this project.

Frequently Asked Questions about ok-planner

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

FAQPage Schema
How do I bootstrap design documentation for an existing codebase?▼

Run /discover-design, which performs as-is discovery scaffolding and then extracts concept, story, and decision catalogs. It files unresolved judgment questions to the issue intake and aborts rather than overwriting human-edited artifacts.

How do I triage open design questions before sprint planning?▼

Run /verify-issues to make every open issue ruling-ready without changing code. It rewrites each issue as a self-contained narrative ending in a recommended ruling the owner accepts by silence or overrides.

Does ok-planner trigger automatically from conversation?▼

No. It activates only through explicit slash commands: /sketch, /verify-issues, /discover-design, /ok-version, and /execute-tasks. Conversation content never auto-triggers it, and subagents dispatched for specific tasks skip it.

Can ok-planner execute a sprint or write implementation plans?▼

No. Implementation planning and execution are explicitly out of scope. A sprint document carries its own execution instructions, and issues close only through the suite-owned /plan-sprint ceremony, not this skill.

What is the difference between /sketch and /discover-design?▼

/sketch is a single-pass pre-commitment design sketch saved to .ok-planner/sketches/ with no review loop and no authorization to build. /discover-design is an autonomous two-phase bootstrap of the full concept, story, and decision catalogs.