Rebalance

Set the project's current priorities around the user's goal. Review the whole open backlog, identify the unfinished work needed for that outcome, and make its essential delivery path urgent so next can pick it up. Reassess everything else by its current importance. These are the new priorities: no saved priority snapshot, expiry, restoration mechanism or extra tracking system.

Use the named project, or infer it from the current repository and conversation. Accept a goal and optional deadline in ordinary language, for example: “prepare the guided design flow for tomorrow's demo.” Resolve relative dates using the user's timezone. Announce the project, concrete outcome and deadline in one short sentence. Ask only when the target or a decision affecting scope cannot be established from available evidence. Do not invent a deadline or treat an example as an instruction to edit that project's tracker.

Use the relevant parts of Ask Matt

This skill follows ask-matt's routing principles. Read the installed router when available, and invoke its supporting skills only when a specific gap needs them. The essentials below apply independently; installing the whole collection or running its setup flow is not a prerequisite.

• Clarify the outcome: use grilling for a decision the user must make, after gathering facts yourself. A stated, testable goal needs no interview.
• Make work buildable: use to-spec when the intended behaviour is missing, then to-tickets when it needs several independent deliveries. Prefer small end-to-end increments with testable acceptance and explicit blocking relationships. Improve existing items before creating new ones.
• Handle raw incoming reports: use triage when a report needs investigation or clarification. Already specified items do not need another triage cycle merely because their priority changes.
• Recognise unresolved decisions: reserve wayfinder for a large effort whose route cannot yet be determined. Identify that gap and keep the independently actionable work moving; do not replace a bounded rebalance with a design programme.
• Hand off to delivery: leave self-contained items for fresh next tasks. Do not invoke implement, start coding, or automatically open another task.

Store specs, decisions and dependency evidence in the project's configured tracker. Follow its documentation policy; do not create ticket files, handoff documents or ADRs merely because another skill uses those defaults.

Read the actual backlog and delivery state