Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Orchestrates Stage 0 research and planning for JUCE plugins - creates architecture.md and plan.md contracts through subagent delegation.
Install Plugin Planning
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/plugin-planning .claude/skills/plugin-planning && rm -rf skills-srcUse ~/.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/
Install the "plugin-planning" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-planning into .claude/skills/plugin-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/plugin-planning .agents/skills/plugin-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plugin-planning" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-planning into .agents/skills/plugin-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/plugin-planning .cursor/skills/plugin-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plugin-planning" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-planning into .cursor/skills/plugin-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/glittercowboy/plugin-freedom-system.git --path .claude/skills/plugin-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/plugin-planning .gemini/skills/plugin-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plugin-planning" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-planning into .gemini/skills/plugin-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install glittercowboy/plugin-freedom-system plugin-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/plugin-planning .github/skills/plugin-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plugin-planning" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-planning into .github/skills/plugin-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/plugin-planning .opencode/skills/plugin-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plugin-planning" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-planning into .opencode/skills/plugin-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plugin-planning- GitHub stars
- 216
- Token cost
- ~1.2k tokens
- SKILL.md length
- 355 words
- Files
- 16 (incl. references, assets)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Orchestrates Stage 0 research and planning for JUCE plugins - creates architecture.md and plan.md contracts through subagent delegation.
- Works in 4 steps: creative-brief.md must exist at… → Parameter specification required… → Plugin status must be ≤ Stage 0 (not… → …
- Creative brief exists and plugin needs DSP architecture specification
- SKILL.md covers Entry Point, Stage 0: Research & Planning and Reference Files
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plugin Planning is an agent skill from glittercowboy/plugin-freedom-system. Orchestrates Stage 0 research and planning for JUCE plugins - creates architecture.md and plan.md contracts through subagent delegation. Use when creative brief exists and plugin needs DSP architecture specification, complexity assessment, or implementation planning. Invoke via /plan command, natural language (plan architecture, research DSP), or as first implementation step.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including reference files and assets (for example `archive/stage-0-research.md`, `archive/stage-1-planning.md` and `assets/architecture-template.md`).
It sits in Agent Workflows, covering Subagents and Planning. The repository describes itself as: AI-assisted JUCE plugin development system for MacOS by TÂCHES.
When your agent uses it
- Creative brief exists and plugin needs DSP architecture specification
- Complexity assessment
- Implementation planning
Example prompts
- “Use the plugin-planning skill to orchestrate Stage 0 research and planning for JUCE plugins - creates architecture.md and plan.md contracts through…”
- “/plugin-planning”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Task, WebSearch, Grep, Glob
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- creative-brief.md must exist at plugins/[Name]/.ideas/
- Parameter specification required (parameter-spec.md OR parameter-spec-draft.md)
- Plugin status must be ≤ Stage 0 (not already in implementation)
- Detect existing contracts (architecture.md, plan.md) for resume logic
What it can do on your machine
Read from SKILL.md and the folder at commit e965cdd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashTaskWebSearchGrepGlob
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
Plugin Planning loads about 1.2k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 355 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Bash, Task, WebSearch, Grep, Glob
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 355 words (~1,200 tokens).
“Purpose: Handle Stage 0 (Research & Planning - consolidated) through subagent delegation. This skill creates the foundation contracts (architecture.md, plan.md) that guide implementation in a single consolidated pass.”
- name
- plugin-planning
- allowed-tools
- Read, Write, Edit, Bash, Task, WebSearch, Grep, Glob
- preconditions
- creative-brief.md must exist in plugins/[Name]/.ideas/, Parameter specification must exist (parameter-spec.md OR parameter-spec-draft.md), Plugin must NOT…
Files
SKILL.md and 15 other files (references, assets) in .claude/skills/plugin-planning of glittercowboy/plugin-freedom-system.
- SKILL.md
- archive/stage-0-research.md
- archive/stage-1-planning.md
- assets/architecture-template.md
- assets/continue-stage-0-template.md
- assets/continue-stage-1-template.md
- assets/decision-menu-stage-0.md
- assets/decision-menu-stage-1.md
- assets/implementation-handoff-template.md
- assets/plan-template.md
- assets/precondition-failed.md
- assets/stage-1-blocked.md
- references/git-operations.md
- references/preconditions.md
- references/state-updates.md
- references/subagent-invocation.md
Open the folder on GitHubat commit e965cdd
Compare with similar skills
Plugin Planning 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plugin Planning this skillglittercowboy/plugin-freedom-system | 216 | — | ~1.2k | Automated safety check: Notes | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 38 repos | ~1.2k | Automated safety check: Pass | None | |
| Execumputun/cc-thingz | 484 | — | ~8k | Automated safety check: Pass | MIT | |
| Executing PlansGanyuanRan/Aegis | 1.3k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Autopilot End-to-End Buildernick-vels/skills | 407 | — | ~2.5k | Automated safety check: Notes | MIT | |
| Workflow Orchestrationvxcozy/workflow-orchestration | 116 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Exec
umputun/cc-thingz
Execute plan tasks sequentially using subagents. An agent skill from umputun/cc-thingz.
Executing Plans
GanyuanRan/Aegis
A skill your agent uses when executing a written implementation plan across sessions or with review checkpoints.
Autopilot End-to-End Builder
nick-vels/skills
Builds an app, site, bot or feature from a spoken idea through requirements, spec, tickets, subagent work, review and acceptance, with a live progress dashboard.
Workflow Orchestration
vxcozy/workflow-orchestration
Disciplined task execution with planning, verification, and self-improvement loops.
Blueprint
byungjunjang/jangpm-meta-skills
Agentic system design blueprint generator. An agent skill from byungjunjang/jangpm-meta-skills.
More from glittercowboy/plugin-freedom-system
All 15 skills in this repoAesthetic Dreaming
glittercowboy/plugin-freedom-system
Create aesthetic templates without first creating a plugin - capture visual design concepts through adaptive questioning.
Deep Research
glittercowboy/plugin-freedom-system
Multi-agent parallel investigation for complex JUCE problems.
Plugin Ideation
glittercowboy/plugin-freedom-system
Adaptive brainstorming for plugin concepts and improvements when exploring ideas, not implementing.
Plugin Improve
glittercowboy/plugin-freedom-system
Fix bugs, add features to completed plugins. An agent skill from glittercowboy/plugin-freedom-system.
Plugin Lifecycle
glittercowboy/plugin-freedom-system
Manage complete plugin lifecycle - install, uninstall, reset, destroy.
Plugin Packaging
glittercowboy/plugin-freedom-system
Create branded PKG installers for plugin distribution. An agent skill from glittercowboy/plugin-freedom-system.
Related
Categories
Questions about Plugin Planning
What does Plugin Planning do?
Orchestrates Stage 0 research and planning for JUCE plugins - creates architecture.md and plan.md contracts through subagent delegation. Plugin Planning is an agent skill from glittercowboy/plugin-freedom-system.md contracts through subagent delegation.
When should I use Plugin Planning?
Plugin Planning fits situations like: creative brief exists and plugin needs DSP architecture specification; complexity assessment; implementation planning.
How do I install Plugin Planning in Claude Code?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a claude-code`. Or copy the skill folder (.claude/skills/plugin-planning in glittercowboy/plugin-freedom-system) into .claude/skills/plugin-planning in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Planning in Codex?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-planning -a codex`. Or copy the skill folder (.claude/skills/plugin-planning in glittercowboy/plugin-freedom-system) into .agents/skills/plugin-planning in your project. Codex loads it when a task matches its description.
Can I use Plugin Planning 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 glittercowboy/plugin-freedom-system --skill plugin-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plugin-planning, .gemini/skills/plugin-planning, .github/skills/plugin-planning and .opencode/skills/plugin-planning in your project.
What does Plugin Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Plugin Planning is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Task, WebSearch, Grep, Glob.
Does Plugin Planning 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 Plugin Planning safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Plugin Planning use?
No licence was found for Plugin Planning or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Plugin Planning use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to Plugin Planning?
Skills that share tags, products or a category with Plugin Planning: Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Exec (umputun/cc-thingz, 484 stars), Executing Plans (GanyuanRan/Aegis, 1.3k stars) and Autopilot End-to-End Builder (nick-vels/skills, 407 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plugin Planning?
glittercowboy (a GitHub user) maintains it in glittercowboy/plugin-freedom-system, which has 216 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on November 19, 2025.
Source: glittercowboy/plugin-freedom-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.