agent-planner

Generate validated WORK_PACKET V2 envelopes and classify work into database, UI, container, or documentation lanes.

1|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/djb258/imo-creator --skill agent-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-planner
Source: https://github.com/djb258/imo-creator/tree/main/skills/agent-planner
Command: npx skills add https://github.com/djb258/imo-creator --skill agent-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill translates user intent into structured work packets that guide other AI agents, ensuring tasks are correctly defined, scoped, and routed for execution.

Core Features & Use Cases

  • WORK_PACKET Generation: Creates validated V2 work packet envelopes.
  • Lane Classification: Determines if work requires database, UI, container, or documentation processing.
  • Scope Definition: Sets boundaries for the work to be performed.
  • Use Case: When a user requests to "update the user profile page and ensure the database schema is compatible," this agent will generate a WORK_PACKET that specifies UI and DB requirements, routing it to the appropriate downstream agents.

Quick Start

Use the agent-planner skill to generate a work packet for updating the user authentication flow.

Frequently Asked Questions about agent-planner

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

FAQPage Schema
How do I structure user intent for AI agent orchestration?

AI agent orchestration relies on validated WORK_PACKET V2 envelopes to translate raw user intent into structured formats. This process classifies work into database, UI, container, or documentation lanes while validating target repositories and defining strict scope boundaries for downstream execution.

How do I generate work packets for AI-driven development pipelines?

To generate work packets for AI-driven development pipelines, input raw user intent to create validated V2 envelopes. The system classifies tasks into database, UI, container, or documentation lanes, validating repositories and branches to route execution correctly.

What is the best way to route tasks across database and UI lanes for AI agents?

Routing tasks across database and UI lanes requires classifying work into specific processing categories. By generating a WORK_PACKET, the system specifies requirements for each lane, ensuring downstream agents receive correctly scoped database, UI, container, or documentation tasks.

Can I use work packets to scope updates across multiple target repositories?

Work packets validate target repositories and branches to scope updates across multiple targets. The generated WORK_PACKET V2 envelope defines explicit scope boundaries, ensuring that complex operations like database schema changes and UI updates remain isolated and correctly routed.

When do I need a work packet for task routing?

You need a work packet for task routing when translating complex user requests into structured AI agent execution. If a request involves multiple domains like updating a user profile page and ensuring database schema compatibility, a WORK_PACKET defines and routes the required UI and DB work.