---
name: quarter-planning
description: Prepare or assess time-bound work commitments using the consumer's planning horizon, capacity evidence, and milestone conventions.
---

# Quarter Planning

Establish the intended period, outcomes, stated capacity and candidate work
from current consumer records. Use supplied dates and commitments; do not infer
staffing, deadlines or a planning calendar. Missing capacity is an uncertainty
to expose, not a license to invent estimates.

Separate explicit commitments from tentative options. Show each candidate's
outcome, prerequisites, evidence of feasibility and reason for inclusion or
deferral. Sequence dependency-ready slices and learning gates before costly
commitments where appropriate. Technical owners decide implementation
feasibility; product and consumer owners decide priorities and commitments.

Follow consumer conventions for milestones, dates, fields, hierarchy and
ownership. Time windows and work hierarchy describe different relationships;
do not substitute a milestone for a parent unless the consumer's policy does
so. Identify unresolved dependencies, date contradictions and scope exceeding
stated capacity. Discuss alternatives without silently rewriting commitments.

Return the proposed period plan with committed and tentative work, dependency
order, capacity assumptions, unresolved choices and expected record changes.
A plan can be useful locally even when live tracker state is unavailable.

Use `gh-steward` to compose and validate coordinated GitHub changes across
milestones, issues or project fields. The existing connector or native `gh`
may handle ordinary single-record work under repository policy. Keep proposals
reviewable, apply within existing authorization, and verify the resulting dates,
relationships and fields. Do not request repeated approval for an unchanged
authorized scope.

Complete with a supported commitment plan or a clear decision gap. Follow the
[decision rubric](../_shared/references/agent-decision-rubric.md).