name	dots-workstation-planning
description	WHAT - Planning, estimation, task breakdown, and iteration capacity fallback based on agentic-workstation Best Practices. Use before finalizing backlog scope, story/task estimates, or iteration commitments.

Planning and Estimation (WHAT)

Use this skill when work needs planning, breakdown, estimation, or capacity validation before it becomes final backlog content.

Apply dots-workstation-output-handshake before producing any final planning artifact: ask where it should live and confirm human review.
Prefer project-specific planning rules if the repo, ticket system, or engagement pack defines them. Otherwise use this default.
If a work item is being created or refined, pair this with dots-workstation-work-item and the relevant atomic skill.

Scope and goal are clear.
Work is broken down into manageable items; anything estimated at 5+ points should be considered for splitting.
Acceptance criteria and dependencies are known enough for estimation.
Estimation technique is explicit: planning poker, T-shirt sizing, Fibonacci, or the team override.
Capacity considers availability, holidays, meetings, focus factor, dependencies, and historical velocity.

references/default-template.md - default planning and capacity template
references/example-sprint-planning.md — example sprint planning with work item breakdown, capacity, and risk assessment
dots-workstation-work-item - work item hierarchy and creation
clickup-cli - task updates after user approval

name	dots-workstation-planning
description	WHAT - Planning, estimation, task breakdown, and iteration capacity fallback based on agentic-workstation Best Practices. Use before finalizing backlog scope, story/task estimates, or iteration commitments.

Use this skill when work needs planning, breakdown, estimation, or capacity validation before it becomes final backlog content.

Apply dots-workstation-output-handshake before producing any final planning artifact: ask where it should live and confirm human review.
Prefer project-specific planning rules if the repo, ticket system, or engagement pack defines them. Otherwise use this default.
If a work item is being created or refined, pair this with dots-workstation-work-item and the relevant atomic skill.

Scope and goal are clear.
Work is broken down into manageable items; anything estimated at 5+ points should be considered for splitting.
Acceptance criteria and dependencies are known enough for estimation.
Estimation technique is explicit: planning poker, T-shirt sizing, Fibonacci, or the team override.
Capacity considers availability, holidays, meetings, focus factor, dependencies, and historical velocity.

references/default-template.md - default planning and capacity template
references/example-sprint-planning.md — example sprint planning with work item breakdown, capacity, and risk assessment
dots-workstation-work-item - work item hierarchy and creation
clickup-cli - task updates after user approval

dots-workstation-planning