Claude project prompt

Claude prompt for sprint planning

Have Claude inspect the current backlog and recent delivery history, then propose a sprint plan that makes constraints and tradeoffs visible.

Best for: Sprint preparation, backlog review, carryover analysis, and team planning before the meeting.

Claude prompt

You are helping me prepare a sprint plan using live Kanera project data through MCP.

Board or project: [NAME]
Sprint dates: [START DATE TO END DATE]
Sprint goal: [GOAL]
Team members and known availability: [DETAILS OR "READ ASSIGNMENTS, ASK FOR CAPACITY"]
Hard commitments: [CARD KEYS OR OUTCOMES]
Planning rule: [WIP LIMITS, POINT LIMIT, OR OTHER CONSTRAINTS]

Before proposing work:
1. Resolve the correct Kanera board.
2. Review the active backlog, ranked priorities, carryover, blocked work, due dates, and dependencies.
3. Review recent completion history only as supporting context. Do not invent velocity from incomplete data.
4. Identify missing estimates, owners, acceptance criteria, or dependency details that make a card unsafe to commit.

Prepare a sprint planning brief with:
- Recommended sprint goal.
- Proposed committed work, ordered by dependency and priority.
- Stretch work that should enter only if capacity becomes available.
- Carryover that needs an explicit decision.
- Dependencies and blockers to resolve before or during the sprint.
- Capacity or workload concerns by assignee.
- Cards that need refinement before commitment.
- Three tradeoff decisions for the planning meeting.
- Kanera card keys beside every recommendation.

Explain why each proposed item supports the sprint goal. Keep analysis separate from board changes. Do not move, assign, create, or edit cards until I review the proposal and explicitly approve the exact changes.

Worked example output

Example result after Claude reviews a product team backlog, current assignments, priorities, and the previous sprint through Kanera MCP.

Example result

Sprint planning brief: Account activation
Sprint dates: 22 September to 3 October

Recommended sprint goal
Complete the invitation and activation path so a new workspace can invite and activate its first external collaborator in staging.

Proposed committed work
1. ACT-141 | Fix external-domain invitation delivery
Why: Removes the primary blocker to end-to-end activation testing.
Dependency: Email provider response analysis in ACT-139.

2. ACT-132 | Complete invitation error states
Why: Required for a supportable invitation flow and ready for review once copy is confirmed.
Dependency: Final permissions wording.

3. ACT-146 | Add activation event tracking
Why: Enables the team to verify the full journey during staging QA.
Dependency: ACT-141 must be testable.

4. ACT-148 | Run collaborator activation QA
Why: Proves the sprint goal after delivery and tracking work are complete.
Dependency: ACT-132, ACT-141, ACT-146.

Stretch work
- ACT-151 | Improve invitation resend guidance. Useful, but not required to prove the sprint goal.

Carryover decision
- ACT-128 has carried over twice and is not tied to the sprint goal. Decide whether to remove it from the sprint or replace ACT-151.

Refinement needed
- ACT-153 has no owner or acceptance criteria and should not be committed yet.

Planning decisions
- Confirm whether permissions copy will arrive before sprint day two.
- Decide whether ACT-128 remains a commitment.
- Confirm that Mei has capacity for both ACT-132 and ACT-146.

Get a more reliable result

Supply actual availability because assignments alone do not describe team capacity.
Ask Claude to separate committed and stretch work so the proposal exposes tradeoffs.
Require explicit approval before Claude changes cards, assignments, or priorities.

Prompt questions

Will Claude commit the sprint on the board?

No. It prepares a proposal with committed work, stretch work, and tradeoffs. Cards move only after you approve the exact changes.

Does this work for agency retainers?

It is built for sprint-shaped backlogs. For retainer reporting, use the monthly retainer or weekly client status prompts instead.

What does Claude need besides the board?

Actual availability. Assignments alone do not describe capacity, so supply known time off or reduced days.

Go from live Kanera work to a finished update.

Connect Claude to Kanera so it can read the live backlog, assignments, priorities, dependencies, and recent work before proposing a sprint.

Explore Kanera's AI workflow

Start free

30-day Pro trial. No card required.