Install
$ agentstack add skill-vlting-claude-skills-think ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Think
One command from goal to execution. Plans read-only, approval gates the handoff, then executes via /run.
/think {goal}
No flags. No modes. One input, one approval gate.
Flow
/think {goal}
|
EXPLORE — Explore agents research codebase (read-only)
|
PLAN — /council {goal} --subroutine (multi-persona deliberation)
|
PRESENT — Review card + plan summary
| User: approve / reject / refine (loop on refine)
|
EXECUTE — /run spawns parallel agents, serializes merges
Phase 1: EXPLORE
Launch one Explore agent (subagent_type: "Explore", thoroughness: "very thorough"):
Explore the codebase for this task: {goal}
Produce: 1) Affected files/modules 2) Existing patterns 3) Constraints
4) Prior art 5) Open questions. Check tests, types, and usage sites.
Output: structured context brief. Stored for PLAN phase.
Read-only. No edits, no file creation.
Phase 2: PLAN
Invoke /council as a subroutine:
Skill: council
Args: {goal} --subroutine
Council runs its full EXPLORE → DELIBERATE → RECONCILE → PRESENT pipeline with --subroutine semantics:
- No plan mode entry
- All tensions resolved via domain authority
- Returns reconciled plan directly
Feed the EXPLORE context brief into the council invocation so it doesn't duplicate exploration work. Prepend to the goal:
/council "Context from exploration:\n{explore_brief}\n\nGoal: {goal}" --subroutine
Output: reconciled council plan.
⚠️ STOP. Do NOT proceed to ENQUEUE. The next step is PRESENT.
Phase 3: PRESENT — MANDATORY APPROVAL GATE
This phase is NON-NEGOTIABLE. Skipping it is a contract violation.
STEP 1 — RECALL (hard gate, do this FIRST, before anything else in this phase):
recall-constraints: query "think PRESENT gate AskUserQuestion approval", type: "feedback", limit: 5
Read the recalled feedback carefully. It will remind you of the approval gate requirement.
STEP 2 — FORMAT the review card below.
STEP 3 — CALL AskUserQuestion with approve / reject / refine options.
STEP 4 — WAIT for the user's response before doing anything else.
⚠️ Informal approval does NOT satisfy this gate. If the user said "looks good" or "implement it" in a normal message — that does NOT count. You MUST still call AskUserQuestion and receive a response through it. The gate requires a formal AskUserQuestion → user response round-trip. No exceptions, no rationalization.
Display the plan as a review card:
# Think: {goal_summary}
## Exploration Summary
{Key findings from EXPLORE — 3-5 bullets}
## Plan
{Numbered actionable steps from council output}
## Key Decisions
{From council reconciliation}
## Risk Summary
{Top 3-5 risks}
---
**approve** — start executing via /run
**reject** — abort, return to conversation
**refine: {feedback}** — re-run PLAN with feedback incorporated
IMMEDIATELY call AskUserQuestion — no additional text, no delay:
Review the plan above. Reply: approve, reject, or refine: {your feedback}
If you are about to invoke /run or write any files and have NOT yet called AskUserQuestion in this conversation — STOP. You skipped PRESENT. Go back and call it now.
Refinement Loop
On refine: {feedback}:
- Re-invoke
/council "{goal}. Additional constraint: {feedback}" --subroutine - Re-present updated plan
- Ask again
Loop until approve or reject. No limit on refinement rounds.
On reject: print "Aborted." and return to normal conversation.
Phase 4: EXECUTE
PREREQUISITE: User MUST have responded "approve" to an AskUserQuestion call. Informal approval via normal message does NOT count. If you have not called AskUserQuestion and received a response through it, STOP — go back to Phase 3.
On approve:
Invoke /run with the full plan text:
Skill: run
Args: Implement the following plan:\n\n{full_plan_text}\n\nGoal: {goal}
/run handles everything:
- Splits plan into file-disjoint tasks
- Spawns parallel agents in worktrees
- Serializes merges (rebase before each merge — no race conditions)
- Cleans up worktrees
- Reports results
No queue files. No relay. No drain loop. /run is ephemeral and self-contained.
Memory Integration
Read ~/.claude/skills/memory/MEMORY_OPS.md for tool call templates.
| Point | Action | |-------|--------| | PRESENT phase, Step 1 (before formatting card) | recall-constraints with "think PRESENT gate AskUserQuestion approval" (feedback, global). Hard gate — do this before anything else in PRESENT. Read results before formatting or calling AskUserQuestion. | | After user approves | store-decision if non-obvious plan choices were made | | After user refines | store-feedback with the refinement reasoning |
Why recall at PRESENT entry? This is the exact failure point. Council output is long and can push skill instructions out of working memory. The recall restores the approval-gate constraint right when it matters — before the agent decides whether to ask or skip.
Rules
- No plan mode. Never call
EnterPlanMode. The skill is read-only by convention during EXPLORE/PLAN/PRESENT. Code changes only happen in EXECUTE (via/run). - Always council. Every task gets
/council --subroutine. No complexity branching, no "too simple to council" shortcut. - Single approval gate. One
approvefrom user triggers execute. No intermediate confirmations. - Lightweight. No roadmap files, no saga/epic hierarchy, no GitHub integration, no queue files. That's
/scope's job. - No edits before approval. EXPLORE and PLAN phases are strictly read-only. Code changes only happen via
/runagents in EXECUTE.
Role Boundary
/think= plan → approve → hand off to/run/council= deliberation engine (called as--subroutine)/run= ephemeral parallel execution with serialized merges/scope= full saga/epic lifecycle (not involved here)
/think is NOT an orchestrator in the /scope sense. It doesn't manage epics, stages, or GitHub tracking. It's a convenience pipeline: plan once, approve once, execute via /run.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: vlting
- Source: vlting/claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.