# 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.

- Skill: `neomjs/goal-scoping` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add neomjs/goal-scoping`
- Raw SKILL.md: https://api.skillmd.com/api/skills/neomjs/goal-scoping/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: neomjs (https://skillmd.com/u/neomjs)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/neomjs/goal-scoping

---

# 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.