Validate Fableplan Loop logo

Validate Fableplan Loop

Community
richkuo
validate-fableplan-loop

Use when the user asks to validate a GitHub issue (without Fable), conditionally plan it with fableplan, then autonomously drive it to a reviewed PR in one shot — "validate-fableplan-loop", "validate, plan, and work on #N", "validate and fableplan and fully automate #N". Runs validate-issue on your session model (not a Fable subagent), auto-applies its update-issue edits when the verdict calls for it, has fableplan produce and post a Fable 5.1 implementation plan (skipped only when the verdict's title-floored signal reads `plan: no`, which means the title score and the recomputed score are both below 75, with no safety flags and no `plan first: Yes` stamp in the issue's Execution block), then hands off to work-on-issue-loop — stopping instead when validation flags the issue as too large, architecturally infeasible, or already addressed by an existing PR, or recommended for closure as completed or invalid, or when the issue edit does not land. The non-Fable-validation counterpart to fable-validate-loop.

Overview

Publisherrichkuo
Repositoryrk-skills
Skill namevalidate-fableplan-loop
Stars
50
Forks
8
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by richkuo on GitHub. Read the source before you install it.

Installation

Install the Validate Fableplan Loop AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/richkuo/rk-skills/tree/main/skills/validate-fableplan-loop
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/richkuo/rk-skills.git /tmp/rk-skills
mkdir -p .claude/skills
cp -r /tmp/rk-skills/skills/validate-fableplan-loop .claude/skills/validate-fableplan-loop
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Validate Fableplan Loop in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Validate Fableplan Loop on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Validate Fableplan Loop is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

validate-fableplan-loop

Chain validate-issue → (conditional) update issue → (conditional) fableplan → work-on-issue-loop into one autonomous run.

This is fable-validate-loop with validation run through the plain validate-issue skill on your session model instead of a Fable 5.1 subagent.

Do not skip or reorder the chain. Validation gates planning, and the plan gates implementation. The only sanctioned skip is fable-validate-loop step 4's score gate, which step 4 below applies unchanged. Every other step of each skill still runs; only the "wait for the user's reply" moments are replaced by the decision rules in the cited steps.

Input

Same as fable-validate-loop, including the optional targetBranch.

Steps

Follow fable-validate-loop steps 1 through 6 with these changes:

Step 1 (validation): invoke the plain validate-issue skill (Skill tool, skill: validate-issue) instead of fable-validate. Let it run its full process — steps 0 through 8 — and produce the standard verdict block that fable-validate-loop step 1 quotes. Treat the verdict as structured output to parse yourself, and don't ask the user to confirm. Record the resolved issue as owner/repo#N per fable-validate-loop step 1; every later step passes that full reference and targets exactly this issue.

Step 2 (scope gate): fable-validate-loop step 2's STOP table applies, sourced from the plain validation (the already-addressing PR comes from validate-issue's step 1 linked-PR check; too large from validate-issue step 7). Rows (a) to (c) are Fable validation only and do not apply here.

Step 3 (update-issue edits): apply validate-issue's step 11 (this chain has no fable-validate step), from the current checkout (no worktree for issue edits, per validate-issue step 0), with fable-validate-loop step 3's read-back and STOP row unchanged. The stacked attribution line is Validated with LLM: <session model> | <session tier> | Harness: <harness> | validate-fableplan-loop, naming the session model and tier that ran the validation.

Step 4 (fableplan): fable-validate-loop step 4's score gate, safety carve-out, stamped plan flag, and top-band note apply, except that here the posted plan is the only Fable 5.1 stage: validation runs on the session model. When fableplan runs, give the planning subagent the validation findings (the verdict block and validate-issue's report) alongside the issue, and instruct fableplan to use the harness suffix validate-fableplan-loop in the posted comment's attribution footer.

Step 5 (handoff) applies unchanged — including that deviations follow work-on-issue step 2's plan-deviation policy and must each be named in the PR body.

Step 6 (report) applies unchanged. Cap the whole report at 55 words and 5 sentences, plain simple English in ASD-STE100 — apply the Response Style rules in CLAUDE.md/AGENTS.md.

Red Flags — STOP

fable-validate-loop's Red Flags table applies, reading "validate-issue" wherever it says "fable-validate", except the row for step 2 rows (a) to (c).

Frequently asked questions

What does the Validate Fableplan Loop AI skill do?

Use when the user asks to validate a GitHub issue (without Fable), conditionally plan it with fableplan, then autonomously drive it to a reviewed PR in one shot — "validate-fableplan-loop", "validate, plan, and work on #N", "validate and fableplan and fully automate #N". Runs validate-issue on your session model (not a Fable subagent), auto-applies its update-issue edits when the verdict calls for it, has fableplan produce and post a Fable 5.1 implementation plan (skipped only when the verdict's title-floored signal reads `plan: no`, which means the title score and the recomputed score are...

Why use Validate Fableplan Loop on TypingMind?

Because you install it once and use it with any model. Validate Fableplan Loop is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Validate Fableplan Loop in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/richkuo/rk-skills/tree/main/skills/validate-fableplan-loop. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Validate Fableplan Loop?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Validate Fableplan Loop?

As many as you like. As long as a model supports skills, you can use Validate Fableplan Loop with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Validate Fableplan Loop AI skill free?

Yes. It is published on GitHub by richkuo under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇