project-planner

Automate project planning by generating kanban backlog items, subitems, and plan documents without executing implementation. This creates all necessary planning artifacts and enforces a formal handoff checkpoint before development begins.

Project planning strictly generates documentation and kanban artifacts without executing implementation. It enforces a mandatory handoff checkpoint, ensuring phased subitems are planned and delegated before any coding work begins.

The best way to structure kanban subitems is by generating them as phased implementation steps with explicit handoff rules. This ensures team-specific storage paths and structured workflows are established before execution.

Yes, you can coordinate multi-team project scoping by generating planning artifacts with team-specific storage paths. It supports clear delegation by creating structured subitems and plan documents for each team's kanban directory.

Yes, you need a kanban board system and kanban-helpers.sh dependencies to manage generated backlog items. The skill integrates with the Kanban Manager skill to store plan documents and structured subitems correctly.

You should not use automated planning when you intend to execute implementation simultaneously. This approach prevents code execution entirely, making it unsuitable if your workflow lacks a mandatory handoff checkpoint before development.