decision
Use when the quest needs an explicit go, stop, branch, reuse-baseline, write, finalize, reset, or user-decision transition with reasons and evidence.
Best for Complex development workflo…Works with GitHub
⌘source
- author
@ResearAI- language
- TypeScript
★2.3kstars
245forks
Apr 19, 2026
✦overview.md
Key Features
- ·Makes explicit go/stop/branch decisions for quest continuation
- ·Uses durable evidence and reasoning for route judgments
- ·Follows shared interaction contract from system prompt
- ·Avoids repeating decisions without new evidence
- ·Records decisions as milestones with evidence and next checkpoints
- ·Gathers shell/environment evidence through bashexec or artifact.git
Use Cases
- →Determining whether to proceed with a development task after gathering evidence
- →Choosing between multiple implementation paths based on code analysis
- →Deciding to stop or reset a quest when requirements cannot be met
- →Making branch decisions in complex workflows with ambiguous next steps
Best for
- ✓Complex development workflows
- ✓Multi-step automation pipelines
- ✓Evidence-based decision points
Not ideal for
- !Simple linear tasks
- !One-off commands
- !Direct code execution
FAQs
name
decision
description
Use when the quest needs an explicit go, stop, branch, reuse-baseline, write, finalize, reset, or user-decision transition with reasons and evidence.
skill_role:stage
Decision
Use this skill whenever continuation is non-trivial. Use it to make one route judgment from durable evidence and then get the quest moving again.
Interaction discipline
Follow the shared interaction contract injected by the system prompt.
Avoid repeating the same decision without new evidence, and use blocking requests only when the user truly must choose.
When a decision materially resolves ambiguity and the quest can continue automatically, follow the durable record with artifact.interact(kind='milestone', reply_mode='threaded', ...) so the user can see the chosen route, the decisive evidence, and the next checkpoint.
Tool discipline
- Do not use native
shell_command/command_executionin this skill. - If decision-making needs shell, CLI, Python, bash, node, git, npm, uv, or environment evidence, gather it through
bash_exec(...). - For git state inside the current quest repository or worktree, prefer
artifact.git(...)before raw shell git commands. - Use
decisionto judge the route, not as an excuse to bypass thebash_exec(...)/artifact.git(...)tool contract.
Planning note
$install
1-click copynpx skills add ResearAI/DeepScientist --skill decisionSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.