agentsclimarketplace
Sign in

Plan delivery collaboration

Skill alexe-ev/product-plugins/product-planning/skills/plan-delivery-collaboration

Structure delivery planning, cross-functional alignment, and sprint or milestone planning. Use this skill when a team needs to coordinate execution across product, engineering, and design.From its SKILL.md

Install
npx -y skills add alexe-ev/product-plugins --skill plan-delivery-collaboration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 430 tokens by cl100k_base, as published. Nobody here has run it

Plan Delivery & Collaboration

Purpose

Help teams structure the delivery process: milestones, dependencies, cross-functional coordination, and sprint/cycle planning.

Skill type

Conceptual skill

Use this skill when

  • A team is ready to move from planning to execution and needs delivery structure
  • Cross-functional alignment (product, engineering, design, QA) is breaking down
  • A project has complex dependencies that need to be sequenced
  • Sprint or milestone planning needs to account for capacity and risk

Do not use this skill when

  • Requirements aren't defined yet (use write-requirements-prd first)
  • The goal is roadmap prioritization (use build-roadmap-prioritization)

Required inputs

  • Prioritized initiative or feature
  • Team structure (rough: how many engineers, designers)
  • Rough timeline or deadline

Optional inputs

  • Requirements or PRD
  • Technical dependencies or architecture notes
  • Risk factors
  • Current sprint or planning cycle

Upstream context

Works best when:

  • Requirements are defined
  • Team capacity is known
  • Dependencies are mapped

If upstream context is missing

Produce a delivery structure framework with placeholders and flag what needs to be confirmed.

Downstream handoff

Output can feed:

  • plan-product-launch (once delivery is complete)
  • validate-experiment-quality (if delivery includes an A/B test)

Instructions

  1. Break the initiative into delivery phases or milestones.
  2. Identify cross-functional dependencies (design handoff, data instrumentation, QA).
  3. Map sequencing constraints.
  4. Identify risks and mitigation steps.
  5. Define checkpoints for alignment and go/no-go decisions.
  6. Produce a lightweight delivery plan.

Output

Provide:

  • Delivery phases / milestones
  • Cross-functional dependencies and owners
  • Sequencing and critical path
  • Risk factors and mitigation
  • Alignment checkpoints
  • Open questions before execution starts

Risks / caveats

  • Do not create delivery plans without requirements
  • Always make dependencies visible — hidden dependencies cause delivery failures
  • Build checkpoints into the plan, not just at the end

What ships with it: 4 files

6.6 KB alongside SKILL.md

examples/

Keep looking

Skills are one crate of 326,782. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.