Agent skill

Plannotator Setup Goal

Turn ideas into executable goal packages with guided interviews and codebase analysis

MITAuto-check passedDevelopment

Install Plannotator Setup Goal

skills CLI

$ npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a claude-code

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

GitHub CLI

$ gh skill install jellydn/my-ai-tools plannotator-setup-goal --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/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plannotator-setup-goal .claude/skills/plannotator-setup-goal && 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/

Paste into Claude Code

Install the "plannotator-setup-goal" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/plannotator-setup-goal into .claude/skills/plannotator-setup-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-setup-goal", 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

$skill-installer install https://github.com/jellydn/my-ai-tools/tree/main/skills/plannotator-setup-goal

Type 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.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools plannotator-setup-goal --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plannotator-setup-goal .agents/skills/plannotator-setup-goal && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "plannotator-setup-goal" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/plannotator-setup-goal into .agents/skills/plannotator-setup-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-setup-goal", 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.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools plannotator-setup-goal --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plannotator-setup-goal .cursor/skills/plannotator-setup-goal && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "plannotator-setup-goal" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/plannotator-setup-goal into .cursor/skills/plannotator-setup-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-setup-goal", 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

$ gemini skills install https://github.com/jellydn/my-ai-tools.git --path skills/plannotator-setup-goal

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools plannotator-setup-goal --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plannotator-setup-goal .gemini/skills/plannotator-setup-goal && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "plannotator-setup-goal" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/plannotator-setup-goal into .gemini/skills/plannotator-setup-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-setup-goal", 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.

GitHub CLI

$ gh skill install jellydn/my-ai-tools plannotator-setup-goal

Installs 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).

skills CLI

$ npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plannotator-setup-goal .github/skills/plannotator-setup-goal && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "plannotator-setup-goal" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/plannotator-setup-goal into .github/skills/plannotator-setup-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-setup-goal", 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.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools plannotator-setup-goal --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plannotator-setup-goal .opencode/skills/plannotator-setup-goal && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "plannotator-setup-goal" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/plannotator-setup-goal into .opencode/skills/plannotator-setup-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-setup-goal", 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: plannotator-setup-goal
GitHub stars: 123
Token cost: ~1.6k tokens
SKILL.md length: 663 words
Files: 1
Skills in repo: 33
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Turn ideas into executable goal packages with guided interviews and codebase analysis

Works in 5 steps: Rearticulate → Interview Bundle → Fact Sheet → …
Tasks that involve Codebase onboarding
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Plannotator Setup Goal is an agent skill from jellydn/my-ai-tools. Turn ideas into executable goal packages with guided interviews and codebase analysis

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi

It sits in Development, covering Codebase onboarding. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.

When your agent uses it

Tasks that involve Codebase onboarding

Example prompts

“/plannotator-setup-goal”

Requirements

Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Rearticulate
Interview Bundle
Fact Sheet
Plan
Goal Output

What it can do on your machine

Read from SKILL.md and the folder at commit 62c9227. 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 (its code samples are bash and json).
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.
Compatibility
cline, claude, opencode, amp, codex, gemini, cursor, pi
From compatibility in the SKILL.md frontmatter.

Context cost

Plannotator Setup Goal loads about 1.6k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 663 words of instructions outside code blocks.

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

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 jellydn/my-ai-tools at commit 62c9227, republished under its MIT licence (© jellydn). 663 words, ~1,576 tokens.

Download SKILL.mdSave it as .claude/skills/plannotator-setup-goal/SKILL.md (or your agent's skills folder).

name: plannotator-setup-goal
description: Turn ideas into executable goal packages with guided interviews and codebase analysis
compatibility: cline, claude, opencode, amp, codex, gemini, cursor, pi
license: MIT
hint: Use when turning an idea or objective into a structured goal package with facts and plan
user-invocable: true
disable-model-invocation: true
metadata.audience: all
metadata.workflow: planning
metadata.source: backnotprop/plannotator@1d9fe3f10fb34af0ef3ce9eed8db1c103a0b05cc
metadata.source_path: apps/skills/extra/plannotator-setup-goal/SKILL.md

Setup Goal

Turn an idea into a goal package at goals/<slug>/ through structured discovery, user interview, and codebase exploration.

Phases

1. Rearticulate

State back what the user wants in your own words. If the conversation already has rich context, summarize it. If the goal is bare or vague, do minimal shallow exploration of the codebase to ground your understanding. Keep it to 2-3 sentences. Wait for the user to confirm or correct before continuing.

Create goals/<slug>/ once the slug is clear. Keep working JSON files and final documents there. JSON preserves provenance and iteration state; markdown is the human-readable authoritative goal package.

Browser session patience: After launching an interview or facts command, wait until the user submits, dismisses, or asks you to stop. Do not close, kill, restart, refresh, or open a second session because the UI is idle. If a rerun is needed, wait for the previous session to end, update its working JSON file, and launch from that file.

For a vague goal with interdependent decisions, suggest an optional one-at-a-time grilling pass. Run it when requested, with a recommended answer for each question. Fold its resolved decisions into the bundle below; skip the bundle if grilling fully resolves scope.

2. Interview Bundle

Build a compact bundle of questions that can derive every outcome fact. Infer answers already clear from the request, conversation, or codebase. Only ask where the user's judgment is needed. Prefer fewer, higher-leverage questions over exhaustive confirmation.

What the feature/change is
Who it's for
What problem it solves
What behavior changes
What success looks like
What's in and out of scope (The most important area to determine facts)
What edge cases to consider
What constraints or precedent apply

If a question can be answered by exploring the codebase, explore the codebase instead of asking.

Write goals/<slug>/interview.json before showing it to the user:

json

{
  "stage": "interview",
  "title": "Short human-readable title",
  "goalSlug": "<slug>",
  "questions": [
    {
      "id": "scope",
      "prompt": "What should be in scope?",
      "description": "Optional clarification.",
      "answerMode": "multi-custom",
      "recommendedAnswer": "Your recommended answer.",
      "recommendedOptionIds": ["ui", "server"],
      "options": [
        { "id": "ui", "label": "UI" },
        { "id": "server", "label": "Server" }
      ],
      "required": true
    }
  ]
}

Supported answerMode values: text, single, multi, custom, single-custom, multi-custom.

Run as a monitored foreground process. Save the exact submitted JSON before continuing:

bash

plannotator setup-goal interview goals/<slug>/interview.json --json > goals/<slug>/interview-result.json

Check the command's exit status and read the result. If dismissed, stop and report that the session was closed. Address questions, uncertainty, or skipped-question notes in chat before proceeding. A skipped question without a note is safe to omit only when non-blocking. For revisions, update interview.json and rerun after the previous session ends.

Show full SKILL.md (282 more words)Show less

3. Fact Sheet

A fact is a simple description of each outcome of a goal. It should be easily testable and verifiable. A fact may describe the function of a specific feature or aspect of a system. A fact may determine specific UI and UX. Again, a fact is literally anything that can be tested and verified in automated or manual testing. Keep fact language simple. In a way, a fact sheet is a design spec, but less verbose & using language the human user can easily visualize & rationalize.

Prepare goals/<slug>/facts-review.json from the submitted interview. When revising, start from the existing review and result files, preserve accepted facts with "accepted": true, and retain their verification selections.

json

{
  "stage": "facts",
  "title": "Short human-readable title",
  "goalSlug": "<slug>",
  "facts": [
    {
      "id": "fact-1",
      "text": "The accepted fact text.",
      "accepted": false,
      "removed": false,
      "recommendedAutomatedVerification": true,
      "automatedVerification": true
    }
  ]
}

Run as a monitored foreground process and save the exact result:

bash

plannotator setup-goal facts goals/<slug>/facts-review.json --json > goals/<slug>/facts-result.json

Check the exit status. Apply accepted, edited, and removed facts directly. If dismissed, stop. Write facts.md as a flat list of accepted facts, one per line. Write facts.meta.json preserving each accepted fact's id, final text, comment, recommendedAutomatedVerification, and automatedVerification value.

4. Plan

Explore the codebase. Discover and validate implementation paths toward each fact. Trace through code, identify files and systems involved, surface risks and unknowns. Refine until you have a confident order of operations.

Facts with automatedVerification: true require concrete automated checks unless a blocker is documented.

Write goals/<slug>/plan.md:

Solution approach (brief)
Ordered steps with the files/systems each touches
Verification for each step (concrete commands or checks)
Risks or open questions worth flagging

Gate the plan with Plannotator:

bash

plannotator annotate goals/<slug>/plan.md --gate

If denied, revise from feedback and re-gate until approved.

5. Goal Output

Write goals/<slug>/goal.md:

The articulated goal (1-3 sentences)
Reference to facts.md as the shared understanding
Reference to plan.md as the execution plan
Done condition

Tell the user:

Done! Launch a goal with `/goal goals/<slug>/goal.md`

Files

Just SKILL.md in skills/plannotator-setup-goal of jellydn/my-ai-tools.

Open the folder on GitHubat commit 62c9227

Compare with similar skills

Plannotator Setup Goal 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.

Plannotator Setup Goal compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Plannotator Setup Goal this skilljellydn/my-ai-tools	123	—	~1.6k	Automated safety check: Pass	MIT	today
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything	86k	—	~1.2k	Automated safety check: Pass	MIT	today
Understand ExplainEgonex-AI/Understand-Anything	86k	—	~1.3k	Automated safety check: Pass	MIT	today
Project Onboarding Guide from Knowledge GraphEgonex-AI/Understand-Anything	86k	—	~1.2k	Automated safety check: Pass	MIT	today
GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram	18k	—	~427	Automated safety check: Pass	MIT	today
Deepwiki Rssopaco/deepwiki-rs	3.1k	—	~748	Automated safety check: Pass	MIT	25 days ago

Similar skills

Codebase Knowledge Graph Q&A
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
86k GitHub stars~1.2k tokensUpdated today
DevelopmentAuto-check passed
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
86k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Project Onboarding Guide from Knowledge Graph
Egonex-AI/Understand-Anything
Writes an onboarding guide for new team members from a project's existing knowledge graph, after checking that the graph still matches the current commit.
86k GitHub stars~1.2k tokensUpdated today
DevelopmentAuto-check passed
GitDiagram Repository Overview
ahmedkhaleel2004/gitdiagram
Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.
18k GitHub stars~427 tokensUpdated today
DevelopmentAuto-check passed
Deepwiki Rs
sopaco/deepwiki-rs
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation.
3.1k GitHub stars~748 tokensUpdated 25 days ago
DevelopmentAuto-check passed
Explore Codebase with Graph
tirth8205/code-review-graph
Navigates a codebase through the code-review-graph MCP tools: architecture overview, symbol search, caller and callee tracing, flows and oversized functions.
32k GitHub starsUsed in 1 repo~335 tokens
DevelopmentAuto-check passed

Questions about Plannotator Setup Goal

What does Plannotator Setup Goal do?

Turn ideas into executable goal packages with guided interviews and codebase analysis. Plannotator Setup Goal is an agent skill from jellydn/my-ai-tools.

When should I use Plannotator Setup Goal?

Plannotator Setup Goal fits situations like: tasks that involve Codebase onboarding.

How do I install Plannotator Setup Goal in Claude Code?

Run `npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a claude-code`. Or copy the skill folder (skills/plannotator-setup-goal in jellydn/my-ai-tools) into .claude/skills/plannotator-setup-goal in your project. Claude Code loads it when a task matches its description.

How do I install Plannotator Setup Goal in Codex?

Run `npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal -a codex`. Or copy the skill folder (skills/plannotator-setup-goal in jellydn/my-ai-tools) into .agents/skills/plannotator-setup-goal in your project. Codex loads it when a task matches its description.

Can I use Plannotator Setup Goal 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 jellydn/my-ai-tools --skill plannotator-setup-goal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plannotator-setup-goal, .gemini/skills/plannotator-setup-goal, .github/skills/plannotator-setup-goal and .opencode/skills/plannotator-setup-goal in your project.

What does Plannotator Setup Goal need to run?

SKILL.md names no scripts, command-line tools or credentials: Plannotator Setup Goal is instructions for the agent only. Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.

Does Plannotator Setup Goal 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 Plannotator Setup Goal 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 Plannotator Setup Goal use?

Plannotator Setup Goal is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plannotator Setup Goal use?

About 1.6k tokens (SKILL.md is roughly 6.3k 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 Plannotator Setup Goal?

Skills that share tags, products or a category with Plannotator Setup Goal: Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars), Understand Explain (Egonex-AI/Understand-Anything, 86k stars), Project Onboarding Guide from Knowledge Graph (Egonex-AI/Understand-Anything, 86k stars) and GitDiagram Repository Overview (ahmedkhaleel2004/gitdiagram, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plannotator Setup Goal?

jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.

Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Plannotator Setup Goal

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Setup Goal

Phases

1. Rearticulate

2. Interview Bundle

3. Fact Sheet

4. Plan

5. Goal Output

Files

Compare with similar skills

Similar skills

More from jellydn/my-ai-tools

Related

Questions about Plannotator Setup Goal