New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Plan Thread

by nubjs in nubjs/nub

A skill your agent uses when an effort's APPROACH isn't settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work, weighing options, resolving…

MITAuto-check passed

Install Plan Thread

skills CLI
$ npx skills add nubjs/nub --skill plan-thread -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nubjs/nub plan-thread --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nubjs/nub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/plan-thread .claude/skills/plan-thread && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
plan-thread
GitHub stars
4.4k
Token cost
~1.2k tokens
SKILL.md length
611 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when an effort's APPROACH isn't settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work, weighing options, resolving…

  • Works in 4 steps: Create the thread note FIRST — it exists… → Work the open questions — with the human… → Move each answered question to ##… → …
  • An efforts APPROACH isnt settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work
  • SKILL.md covers The defining property: the…, Status lifecycle, How to run a plan thread and Boundaries with the other…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Plan Thread is an agent skill from nubjs/nub. Use when an effort's APPROACH isn't settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work, weighing options, resolving open questions with the human. The design-in-progress thread profile. Auto-triggers on "spin up a plan", "let's design", "plan thread", "how should we approach", "think through the approach".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The fast all-in-one Node.js toolkit. The licence is MIT.

When your agent uses it

  • An efforts APPROACH isnt settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work
  • Weighing options
  • Resolving open questions with the human
  • How should we approach

Example prompts

  • “s APPROACH isn”
  • “spin up a plan”
  • “s design”
  • “/plan-thread”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Create the thread note FIRST — it exists before any dispatch — with status: planning. Write the Goal (the objective + why) and seed ##…
  2. Work the open questions — with the human (a plan thread routinely carries human-owned decisions: defaults, product behavior, API/config…
  3. Move each answered question to ## Decisions the instant it's settled — a decided thing lives under Decisions, never lingering in Open…
  4. Lock the design + hand off: when the approach is settled, record the final design in ## Decisions, write the implementation handoff in ##…

What it can do on your machine

Read from SKILL.md and the folder at commit 568e73a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Plan Thread loads about 1.2k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 611 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nubjs/nub at commit 568e73a, republished under its MIT licence (© nubjs). 611 words, ~1,168 tokens.

Download SKILL.mdSave it as .claude/skills/plan-thread/SKILL.md (or your agent's skills folder).
name
plan-thread
description
Use when an effort's APPROACH isn't settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work, weighing options, resolving open questions with the human. The design-in-progress thread profile. Auto-triggers on "spin up a plan", "let's design", "plan thread", "how should we approach", "think through the approach".
metadata.internal
true

Plan threads

A plan thread is one of the four thread profiles, alongside the implementation thread (build-the-decided-thing), the research thread (find-out-what's-true → wiki/research/, see the research-thread skill), and the audit thread (verify-parity → wiki/research/, see the audit-thread skill). Its deliverable is a settled design / approach — not code, not findings, not a gap catalog. It is the thread you open when how to do something is the open question.

The defining property: the deliverable is the DESIGN

A plan thread's work IS the thinking. You'd staff it with the human and/or a Plan/architect agent (Claude Code's Plan agent type) — never an implementer, because there's nothing settled to implement yet. Its ## Open questions are the live work; its ## Decisions accrete as questions resolve. When the design locks, the plan thread's job is done and an implementation thread takes over.

Status lifecycle

  • A plan thread carries status: planning, the status for "design-in-progress". It is non-terminal but parked — it is NOT auto-surfaced in the per-turn / stop-hook nag (only enqueued/active/blocked nag the orchestrator). You pull a plan thread up deliberately when you choose to work it — it does not chase you. (Legacy plan/todo/needs-decision are still accepted as read-aliases — plan/todo→planned, needs-decision→blocked — but write only the canonical words.)
  • THE TRANSITION RULE (load-bearing): a plan thread flips to planned the moment the design is LOCKED — open questions resolved, approach decided, only implementation remaining. Planning ends by promoting to planned (or straight to active if you dispatch the implementer that turn). A plan thread that has no open design questions left but is still status: planning is mis-statused — promote it.
  • Distinguish from blocked: that's waiting on ONE specific human yes/no. planning is the broader ongoing design with multiple open questions being worked collaboratively.

How to run a plan thread

  1. Create the thread note FIRST — it exists before any dispatch — with status: planning. Write the Goal (the objective + why) and seed ## Open questions with the real unknowns.
  2. Work the open questions — with the human (a plan thread routinely carries human-owned decisions: defaults, product behavior, API/config surface, architecture) and/or by dispatching a Plan/architect agent or a focused wiki/research/audit sub-thread to get the facts a decision needs. Ground every design claim in code or an experiment, never memory (the probing-methodology discipline).
  3. Move each answered question to ## Decisions the instant it's settled — a decided thing lives under Decisions, never lingering in Open questions. The thread always reads as current truth (no changelog).
  4. Lock the design + hand off: when the approach is settled, record the final design in ## Decisions, write the implementation handoff in ## Next step (what an implementer should build), and flip the status to planned (or dispatch the implementer and go active). The implementation thread inherits the locked design.
Show full SKILL.md (162 more words)Show less

Boundaries with the other profiles

  • A plan thread that needs a FACT to decide → spin a research or audit sub-effort, fold the result back, keep deciding. The plan thread owns the decision; the wiki/research/audit owns the fact.
  • A plan thread does NOT land code. The instant code should be written, the design is locked → it becomes a planned/implementation thread.
  • Don't let a plan thread become a place to park indefinite "someday" design — if it's not being actively worked toward a lock, it's either planned (scoped, awaiting actioning) or should be dismissed.

Anti-redundancy with planned

planning and planned are NOT the same parked state: planning = the design itself is still the work (you'd dispatch an architect or talk to the human); planned = the design is DONE and the next dispatch is an implementer. The whole point of the split is to tell, at a glance, whether a parked thread needs thinking or building. Keep the boundary crisp by always promoting planning→planned at design-lock.

© nubjs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/plan-thread of nubjs/nub.

Open the folder on GitHubat commit 568e73a

Compare with similar skills

Plan Thread next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Plan Thread compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plan Thread this skillnubjs/nub4.4k—~1.2kAutomated safety check: PassMIT
Turn This Into A Threadsickn33/agentic-awesome-skills47k1 repos~1.4kAutomated safety check: PassMIT
Deep Think Maximum Cognitive Effort Protocol Mq8kvw92nexu-io/open-design100k—~1.7kAutomated safety check: PassApache-2.0
Thread Listget-bb/bb4.2k—~880Automated safety check: PassMIT
Threads Long Threadbam-bam-2/solo-skills367—~2.9kAutomated safety check: PassMIT
Codex Thread Readerhuangruiteng/CS-Notes4k—~1.4kAutomated safety check: PassMIT

Similar skills

  • Turn This Into A Thread

    sickn33/agentic-awesome-skills

    Turn a long idea, transcript, article or draft into a Twitter/X thread where every tweet stands alone.

    47k GitHub starsUsed in 1 repo~1.4k tokens
    Writing & ContentAuto-check passed

  • Thread List

    get-bb/bb

    Inspect or change the sidebar thread list's layout preferences: organization mode, sort, section order, hidden groups, collapsed groups, and thread row actions.

    4.2k GitHub stars~880 tokensUpdated today
    Auto-check passed

  • Threads Long Thread

    bam-bam-2/solo-skills

    밤밤 스레드 계정에 장문 연작 타래(13~30편)를 쓰고 이미지까지 붙여 임시저장·발행할 때 읽을 것. An agent skill from bam-bam-2/solo-skills.

    367 GitHub stars~2.9k tokensUpdated 23 days ago
    Auto-check passed

  • Codex Thread Reader

    huangruiteng/CS-Notes

    Locate and read a Codex thread by a codex thread link, thread id, or rollout path across all local CODEXHOME directories (~/.codex, ~/.codex-gpt, ...).

    4k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Threads

    unifapi-agent/agents

    When a workflow needs public Threads (Meta) data through UnifAPI — recent and top post search on a term, profiles, or a handle's posts, replies, and reposts.

    586 GitHub stars~1.3k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

More from nubjs/nub

All 31 skills in this repo

  • Cpu Reduction

    nubjs/nub

    Diagnose and clear CPU, memory, and disk contention on the maintainer's dev host.

    4.4k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Disk Reduction

    nubjs/nub

    Reclaim disk on the maintainer's Mac when the volume is full or filling — ENOSPC, "no space left on device", a failed build or agent harness, or a routine sweep of Rust build residue.

    4.4k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Nub Charts

    nubjs/nub

    Build a performance chart for nubjs.com — the SVG bar figures in blog posts, docs pages and social posts (a runtime augmentation against plain node, an install or dispatch comparison, a cross-tool…

    4.4k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Audit Thread

    nubjs/nub

    A skill your agent uses when running a compatibility/parity AUDIT — enumerating where nub diverges from a reference it claims parity with (pnpm CLI grammar, a lockfile format, a Node behavior, a…

    4.4k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Linux Vm Test

    nubjs/nub

    Run ad-hoc Nub tests and debugging probes on real local Linux guests.

    4.4k GitHub stars~986 tokensUpdated today
    Auto-check passed

  • Pm Perf Tracing

    nubjs/nub

    Performance-trace Nub package-manager installs using the existing phase timings, structured diagnostics, and sampling-profiler workflow.

    4.4k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Questions about Plan Thread

What does Plan Thread do?

A skill your agent uses when an effort's APPROACH isn't settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work, weighing options, resolving…. Plan Thread is an agent skill from nubjs/nub. Use when an effort's APPROACH isn't settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work, weighing options, resolving open questions with the human.

When should I use Plan Thread?

Plan Thread fits situations like: an efforts APPROACH isnt settled yet and needs collaborative design BEFORE implementation — fleshing out how a feature/change should work; weighing options; resolving open questions with the human; how should we approach.

How do I install Plan Thread in Claude Code?

Run `npx skills add nubjs/nub --skill plan-thread -a claude-code`. Or copy the skill folder (.claude/skills/plan-thread in nubjs/nub) into .claude/skills/plan-thread in your project. Claude Code loads it when a task matches its description.

How do I install Plan Thread in Codex?

Run `npx skills add nubjs/nub --skill plan-thread -a codex`. Or copy the skill folder (.claude/skills/plan-thread in nubjs/nub) into .agents/skills/plan-thread in your project. Codex loads it when a task matches its description.

Can I use Plan Thread in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nubjs/nub --skill plan-thread -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-thread, .gemini/skills/plan-thread, .github/skills/plan-thread and .opencode/skills/plan-thread in your project.

What does Plan Thread need to run?

SKILL.md names no scripts, command-line tools or credentials: Plan Thread is instructions for the agent only.

Does Plan Thread access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Plan Thread safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Plan Thread use?

Plan Thread is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plan Thread use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Plan Thread?

Skills that share tags, products or a category with Plan Thread: Turn This Into A Thread (sickn33/agentic-awesome-skills, 47k stars), Deep Think Maximum Cognitive Effort Protocol Mq8kvw92 (nexu-io/open-design, 100k stars), Thread List (get-bb/bb, 4.2k stars) and Threads Long Thread (bam-bam-2/solo-skills, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan Thread?

nubjs (a GitHub organization) maintains it in nubjs/nub, which has 4,370 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.

Source: nubjs/nub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.