team-meeting

Turn a goal into a sprint-ready team plan with assigned tasks.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/supertyrelle/pelley --skill team-meeting-supertyrelle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-meeting
Source: https://github.com/supertyrelle/pelley/tree/main/skills/team-meeting
Command: npx skills add https://github.com/supertyrelle/pelley --skill team-meeting-supertyrelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a stated goal into a concrete, collaborative execution plan by using the real team’s roles, ownership, learnings, and constraints instead of generic brainstorming.

Core Features & Use Cases

  • Team-aware planning: Reads the team manifest, member learnings, and prior decisions to plan work within actual ownership boundaries.
  • Dependency mapping: Identifies cross-team blockers, overlaps, and handoffs so tasks are sequenced correctly.
  • Sprint-ready output: Breaks a goal into assignable tasks with scope, risks, dependencies, and acceptance criteria.
  • Use case: A product or engineering lead can ask the team to plan a feature rollout, bugfix initiative, or refactor and get a structured task plan ready for execution.

Quick Start

Ask the team-meeting skill to plan a specific goal for your current team and use the resulting task breakdown to prepare for execution.

Frequently Asked Questions about team-meeting

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

FAQPage Schema
How do I create sprint-ready team plans from a specific goal?

To create sprint-ready team plans, you need a team manifest, member learnings, prior decisions, and backlog awareness. This process turns a specific goal into structured, assignable tasks with scope, risks, dependencies, and acceptance criteria for execution.

What is task decomposition with dependency mapping for team coordination?

Task decomposition with dependency mapping breaks a goal into sequenced assignments by identifying cross-team blockers, overlaps, and handoffs. It uses actual team ownership boundaries to ensure tasks are structured correctly for collaborative execution.

How do I plan a feature rollout using real team ownership boundaries?

Planning a feature rollout requires reading the team manifest and member learnings to assign work within actual ownership boundaries. This ensures the execution plan respects real roles and constraints instead of using generic brainstorming.

Do I need a team manifest to generate execution plans for cross-functional work?

Yes, a team manifest is required to generate execution plans. You also need member learnings, prior decisions, and backlog awareness to produce actionable assignments that correctly sequence dependencies for cross-functional work.

What's the best way to sequence cross-team blockers and handoffs during sprint planning?

The best way to sequence cross-team blockers and handoffs is using team-aware planning that maps dependencies. This identifies overlaps and ensures sprint-ready output breaks goals into correctly sequenced, assignable tasks with clear acceptance criteria.