Agent skill

df:research-objective

Research how to implement an objective before planning. Use when the user wants to investigate, research, or explore options before planning an objective. Triggers on: "research objective", "investigate before planning", "look into how to build", "what's the best approach for objective"

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill df-research-objective --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Allowed tools: -Read-Bash-Task
Path: skills/analysis/df-research-objective/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<objective> Research how to implement an objective. Spawns df-objective-researcher agent with objective context. **Note:** This is a standalone research command. For most workflows, use `/df:plan-objective` which integrates research automatically. **Use this command when:** - You want to research without planning yet - You want to re-research after planning is complete - You need to investigate before deciding if an objective is feasible **Orchestrator role:** Parse objective, validate against roadmap, check existing research, gather context, spawn researcher agent, present results. **Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction. </objective> <context> Objective number: $ARGUMENTS (required) Normalize objective input in step 1 before any directory lookups. </context> <process> ## 0. Initialize Context ```bash INIT=$(node ~/.claude/devflow/bin/df-tools.cjs init objective-op "$ARGUMENTS") ``` Extract from init JSON: `objective_dir`, `objective_number`, `objective_name`, `objective_found`, `commit_docs`, `has_research`. Resolve researcher model: ```bash

What's inside
Steps it walks through
  1. 0. Initialize Context
  2. 1. Validate Objective
  3. 2. Check Existing Research
  4. 3. Gather Objective Context
  5. 4. Spawn df-objective-researcher Agent
  6. 5. Handle Agent Return
  7. 6. Spawn Continuation Agent
Ships with 1 file
  • metadata.json
Commands it runs
ls .planning/objectives/${OBJECTIVE}-*/RESEARCH.md 2>/dev/null
Objective section already loaded in OBJECTIVE_INFO
echo "$OBJECTIVE_INFO" | jq -r '.section'
cat .planning/REQUIREMENTS.md 2>/dev/null
cat .planning/objectives/${OBJECTIVE}-*/*-CONTEXT.md 2>/dev/null
grep -A30 "### Decisions Made" .planning/STATE.md 2>/dev/null
More from claude-skill-registry
All skills →
About this skill
What does the df:research-objective skill do?

Research how to implement an objective before planning. Use when the user wants to investigate, research, or explore options before planning an objective. Triggers on: "research objective", "investigate before planning", "look into how to build", "what's the best approach for objective"

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill df-research-objective --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going