aep-dispatch

Dispatch and orchestrate product features using a scoring system with WIP limits.

Updated May 18, 2026
One-click install
npx skills add https://github.com/memorysaver/project-understanding --skill aep-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aep-dispatch
Source: https://github.com/memorysaver/project-understanding/tree/main/.agents/skills/aep-dispatch
Command: npx skills add https://github.com/memorysaver/project-understanding --skill aep-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires product-context.yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of selecting and dispatching the next feature to be developed in a product lifecycle, reducing manual work and improving efficiency.

Core Features & Use Cases

  • Feature Dispatch: Selects the next feature based on business value, critical path urgency, and other factors.
  • Context Assembly: Assembles all necessary context for the selected feature, including dependencies and related information.
  • Handoff: Hands off the selected feature to the appropriate team or tool for further development.
  • Use Case: For a product manager, use this Skill to automatically determine which feature to develop next, gather all necessary context, and hand it off to the engineering team.

Quick Start

Run the 'aep-dispatch' command to automatically dispatch the next feature in the product lifecycle.

Frequently Asked Questions about aep-dispatch

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

FAQPage Schema
How do I automate feature dispatch in product development?

Automating feature dispatch requires a scoring system to evaluate business value and critical path urgency. This approach automatically selects the next feature, assembles necessary context, and hands it off to engineering teams for development.

What is the best way to determine which product feature to develop next?

Determining the next product feature relies on a scoring system assessing business value and critical path urgency. It automatically selects the most appropriate feature from your product context and orchestrates the handoff to development.

Do I need a product context file to automate feature lifecycle orchestration?

Yes, feature lifecycle orchestration requires a product context file defining features, dependencies, and relevant information. This YAML file provides the necessary structure for the scoring system to evaluate and dispatch features accurately.

Can I batch dispatch product features and apply WIP limits?

Yes, batch dispatch and WIP limits are supported during feature orchestration. This allows you to control the flow of features moving into development simultaneously, preventing team overload while maintaining development efficiency.

How does context assembly work for dispatched product features?

Context assembly for dispatched features gathers all necessary dependencies and related information from your product context file. It automatically packages this data to ensure the receiving engineering team has everything required to begin development immediately.