project_management

Define your project goals, scope, constraints, and explicit non-goals in a single PROJECT.md file at the repository root. This Skill provides templates and checklists to structure it as the single source of truth for planning decisions.

Appetite-based planning asks how much time you want to spend on work rather than estimating how long it will take. Teams bet fixed time budgets on shaped pitches, which forces scope prioritization instead of schedule slip.

Cycles are delivery-oriented periods followed by a cool-down phase, rather than back-to-back two-week sprints. Leftover work is re-evaluated instead of automatically rolling into the next cycle, and completed tasks are archived.

Yes, it recommends asynchronous daily check-ins instead of meetings and a triage workflow that moves incoming bugs and feature requests from an inbox to backlog, icebox, or the next cycle. It also covers written architecture decision records.

Avoid heavyweight PROJECT.md planning for trivial one-off scripts or exploratory prototypes where goals change hourly. It adds the most value for multi-week efforts with multiple contributors needing shared alignment.