Individual skill
plannotator-setup-goal
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
apps/skills/extra/plannotator-setup-goal/SKILL.md
Source commit 748c27a7de085444de509ad8c1f8a9cd0859e3a2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 9,888
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- opencode Repository topic
- obsidian Repository topic
- pi-mono Repository topic
- plan-mode Repository topic
- codex Repository topic
- agents Repository topic
- code-review Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,602 bytesSKILL.mdcore · 9,602 bytesSKILL.mdcore · 9,602 bytesSKILL.mdcore · 9,602 bytesSKILL.mdcore · 9,602 bytesSKILL.mdcore · 9,602 bytesSKILL.mdcore · 9,602 bytesSKILL.test.tsruns · 2,021 bytesagents/openai.yamlasset · 193 bytes
Read excerpt
# 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 the goal directory once the slug is clear:
```bash
mkdir -p goals/<slug>