verify-issues

Verifies open design issues and writes generated or recommended rulings for each.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw design issues arrive as unverified problem statements that may already be answered by the design corpus, forcing owners to re-investigate every issue before deciding anything. ## Core Features & Use Cases - Legacy intake conversion: Converts a legacy .ok-planner/issues.jsonl event log into per-issue Markdown files under .ok-planner/issues/. - Corpus-answered closure: Closes issues the design corpus (concepts, stories, decisions) already squarely answers, moving them to history with a closure note. - Batched investigation plus inline authorship: Fans out read-only investigator subagents in batches of up to 10, then rewrites each surviving issue in the main loop as a from-the-top narrative ending in a marked generated or recommended ruling. - Use Case: After a certification gate promotes a batch of issues, run the verification pass so every open issue is either closed as already-answered or rewritten with a ruling the owner accepts by silence or overrides before the next sprint plan. ## Quick Start Run /verify-issues to verify every open issue in .ok-planner/issues and write a ruling for each one.

Frequently Asked Questions about verify-issues

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

FAQPage Schema
How do I verify open design issues before sprint planning?▼

Run /verify-issues to process every file with status open under .ok-planner/issues. It closes issues the corpus already answers and rewrites the rest with a generated or recommended ruling, so the next /plan-sprint can carry them directly.

How do I convert a legacy issues.jsonl file to issue files?▼

The verification pass folds .ok-planner/issues.jsonl by id, writes one Markdown file per still-open issue into .ok-planner/issues/, and archives the log to .ok-planner/history/issues.jsonl. Terminal ids stay only in the archived log.

Does verify-issues change code or the design corpus?▼

No. It edits only issue files, never code and nothing under .ok-planner/design/. Where the rules fully determine a fix, it writes a generated ruling naming that fix for /plan-sprint to draft and execution to apply.

Can I override a ruling written by verify-issues?▼

Yes. Every ruling is marked generated or recommended and is only a recommendation. Edit the text to redirect, empty the section to discuss live, or leave it as-is to accept by silence at the next /plan-sprint.

When should I not run verify-issues?▼

Skip it when there are no open issues, since it reports and stops on an empty scope. It also never touches verified, promoted, retired, or answered files, and it does not promote or retire issues, which are /plan-sprint acts.