project-planning

Standardize vision documents, roadmaps, backlogs, and sprint kanban boards.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/faccomichele/open-claw-team --skill project-planning-faccomichele
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-planning
Source: https://github.com/faccomichele/open-claw-team/tree/main/skills/project-planning
Command: npx skills add https://github.com/faccomichele/open-claw-team --skill project-planning-faccomichele

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates fragmented, misaligned project planning across multi-agent teams by providing a single standardized system for managing all core planning artifacts, ensuring every team member has access to consistent, up-to-date context.

Core Features & Use Cases

  • Standardized Document Management: Maintain consistent, structured formats for vision statements, quarterly roadmaps, structured task backlogs, and sprint kanban boards across all projects.
  • Cross-Agent Alignment: Ensure all specialist agents (backend, frontend, infra, testing) can reference up-to-date planning context to prioritize work correctly and avoid duplicated effort.
  • Use Case: A PM agent can use this Skill to add a new epic to the quarterly roadmap, create corresponding high-priority tasks in the backlog, and update the current sprint board to keep the entire team synchronized on new priorities.

Quick Start

Use the project-planning skill to add the new "cost monitoring dashboard" epic to the Q1 2026 section of the project's /docs/roadmap.md file and create corresponding high-priority tasks in the /ops/backlog.json file.

Frequently Asked Questions about project-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize project roadmaps and backlogs for multi-agent teams?

Standardize project roadmaps and backlogs by maintaining consistent formats for vision documents, quarterly roadmaps, task backlogs, and sprint kanban boards. This ensures every specialist agent accesses up-to-date context and prioritizes work correctly without duplicated effort.

What is the best way to manage sprint planning and task dependencies across backend and frontend agents?

Manage sprint planning and task dependencies by enforcing consistent ownership rules and formatting for planning files. Cross-agent alignment is maintained by allowing backend, frontend, infra, and testing agents to reference shared sprint boards and structured backlogs.

How do I add a new epic to a quarterly roadmap and update the task backlog?

Add a new epic to a quarterly roadmap by updating the project's roadmap file, then create corresponding high-priority tasks in the structured backlog. This synchronizes the entire multi-agent team on new priorities during task execution.

Does this project planning approach work without external dependencies?

Yes, this project planning approach works without external dependencies. It relies entirely on standardized formatting and ownership rules for internal planning files like markdown roadmaps and JSON backlogs to reduce cross-team misalignment.

Can I use structured task backlogs and kanban boards for agile project tracking?

Yes, you can use structured task backlogs and kanban boards for agile project tracking. The system supports epic tracking, task dependency management, sprint planning, and priority alignment across multiple development agents.

When should I not use a standardized backlog and roadmap system for project planning?

You should not use a standardized backlog and roadmap system if your multi-agent team does not require strict formatting rules or shared context. It is designed specifically to reduce cross-team misalignment during complex task execution and status reviews.