granary-initiative-planner

Plan cross-project initiatives by defining a central initiative, breaking it into independently implementable projects, and spawning sub-agents to coordinate planning while maintaining an integrated architectural view across teams.

Manage multi-team dependencies by orchestrating and enforcing inter-project relationships within a centralized initiative, ensuring that scope and architecture remain aligned and work flows sequentially across repositories.

Yes, you can break down large initiatives by creating individual projects for each team or service, then adding them to the parent initiative to maintain scope alignment while enabling independent implementation.

Start by creating an initiative, defining its description, creating individual projects for each service, and adding those projects to the initiative to trigger sub-agents for detailed cross-project planning.

Yes, cross-project planning is specifically designed for efforts spanning multiple services or repositories, helping you align scope, timelines, and architecture across distributed teams and codebases.

You need centralized initiative planning when an effort spans multiple services, repositories, or teams, requiring cross-project dependency orchestration and architectural alignment that standard project management cannot provide.