Loading…
Use when planning or structuring work in OpenProject rather than just recording it — setting up a new project, scoping an initiative, breaking an epic or feature down into phases, milestones, and tasks, building a work breakdown structure, sequencing work and defining dependencies, estimating effort, laying out a roadmap or release plan, restructuring a project whose hierarchy has gone wrong, or reviewing an existing plan before work starts. Applies equally to work projects and to personal, side, or hobby projects worked on in whatever time is available. Triggers on "plan a project", "scope this work", "break this down", "create a WBS", "set up phases and milestones", "what should the tasks be", "build a roadmap", "plan the sprints", "plan my side project", "organise this personal project", "review the plan", "is anything missing from the plan", "check these tasks before we start". For executing and reporting on work that is already structured, use the openproject skill instead.
project-planning is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Planning work in OpenProject Creating tickets is easy; creating a structure people can actually run a project from is not. A plan is wrong in ways that only s. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding project-planning to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install zilligm/openproject-mcpReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Planning work in OpenProject Creating tickets is easy; creating a structure people can actually run a project from is not. A plan is wrong in ways that only surface weeks later: