Skip to content

Latest commit

 

History

16 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

fableplan

A Claude Code skill that delegates implementation planning to a Fable 5.1 planning subagent, checks the plan in your main session, and, when a GitHub issue is referenced, posts the vetted plan to the issue as a comment. Then it stops.

The idea: let a dedicated planning model (Fable 5.1) produce a concrete, ordered implementation plan before any code is written, review it against the real codebase, and preserve it on the tracker. The skill never builds; you build from the plan when you choose to.

What it does

Trigger it with /fableplan, "fableplan this", or "plan this with fable", plus a task description and optionally a GitHub issue (#N, a full URL, or owner/repo#N).

The skill then runs a 5-step flow:

  1. Resolve the GitHub issue (only if one is referenced) so the planner works from the real requirements, not a paraphrase.
  2. Dispatch the Fable 5.1 Plan subagent, confirm it made no edits, and save the plan verbatim to a scratch file. The plan follows the repo's CLAUDE.md/AGENTS.md conventions, cites file:line for its claims about the code, lists open questions and assumptions, and gives acceptance criteria and exact verification commands.
  3. Sanity-check the plan against the actual codebase (each file:line citation, files, symbols, conventions). It stops and asks you if the plan is structurally wrong rather than silently re-planning.
  4. Post the vetted plan to the GitHub issue as a comment (only if one was referenced). The heading and footer name the model and effort that actually produced the plan.
  5. Present the plan to you, then stop. The skill never builds.

Install

As a plugin (recommended)

This repo is a Claude Code plugin marketplace. Inside any Claude Code session:

/plugin marketplace add richkuo/fableplan
/plugin install fableplan@fableplan

The skill is picked up automatically from the plugin's skills/ directory, and updates flow through the plugin system.

With npx (npm)

Published to npm as @fableplan/fableplan. One command copies the skill into ~/.claude/skills/:

npx @fableplan/fableplan

Add --project to install into the current repo's .claude/skills/ instead of your personal directory.

Ask Claude Code to install it

Paste this straight into a Claude Code prompt:

Install the fableplan skill from https://github.com/richkuo/fableplan into ~/.claude/skills — fetch skills/fableplan/SKILL.md and place it at ~/.claude/skills/fableplan/SKILL.md

With npx skills

If you use Vercel Labs' skills CLI, it discovers the skills/fableplan/SKILL.md layout automatically:

npx skills add richkuo/fableplan

This installs into .claude/skills/ (and any other agents it detects). It's a third-party tool, separate from the official plugin marketplace above.

Manual (single file)

A Claude Code skill is just a directory containing a SKILL.md, so you can also install it with one command — no clone needed:

mkdir -p ~/.claude/skills/fableplan && curl -fsSL https://raw.githubusercontent.com/richkuo/fableplan/main/skills/fableplan/SKILL.md -o ~/.claude/skills/fableplan/SKILL.md

This puts it in your personal skills directory (~/.claude/skills/), available in every project. To scope it to a single project instead, put the file at <repo>/.claude/skills/fableplan/SKILL.md.

Verify

Start a new Claude Code session (or restart the current one), then run:

/fableplan <task to plan>

Requirements

  • Claude Code with access to the fable model for the planning subagent.
  • gh (GitHub CLI), authenticated, if you want the issue-comment step.
  • A local clone of the repository when you plan against a GitHub issue.

Notes

  • The planning subagent always runs on Fable 5.1 regardless of your main session's model.
  • The skill adapts to the target repo's conventions (e.g. its CLAUDE.md or AGENTS.md); behavior isn't hardcoded to any one project.

License

MIT — see LICENSE.

About

A Claude Code skill that delegates implementation planning to a Fable 5 subagent, then builds from the vetted plan in an isolated git worktree — posting it to a referenced GitHub issue along the way.

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages