goal-scoping
Scope a GOAL (release / initiative / major objective) into a few coherent owned LANES — the planning front-end of the epic lifecycle. Convert goals into lanes (not scrap tickets); peers self-select lanes; the planner defines goal+lanes but never assigns a peer. Triggers: before decomposing a release/initiative/major-goal into work; when a goal needs scoping into owned streams; when work is being chased as scattered micro-tickets with no owned lanes; when tempted to skip planning OR to assign peers to lanes.
75
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Goal-Scoping — the planning front-end (goal → owned lanes)
If you are about to decompose a GOAL (a release, initiative, or major objective) into work — or you notice work being chased as scattered micro-tickets with no owned lanes, or you are tempted to assign peers to work — you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/goal-scoping/references/goal-scoping-workflow.md before scoping or assigning anything.
- Repository
- neomjs/neo
- Commit
b4a1b58
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.