default-planner

Plan executable task sequences from vague cross-domain requests.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/clode-labs/aramb-skills --skill default-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: default-planner
Source: https://github.com/clode-labs/aramb-skills/tree/main/default-planner
Command: npx skills add https://github.com/clode-labs/aramb-skills --skill default-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts ambiguous user requirements into structured, executable task plans that guide multi-domain development efforts.

Core Features & Use Cases

  • Cross-domain planning: Analyzes requests that span frontend, backend, and infrastructure to produce end-to-end task sequences.
  • Architecture-aware routing: Defines task order and dependencies, guided by architectural best practices.
  • Validation-ready outputs: Each task includes inputs, acceptance criteria, and success metrics to ensure reliable delivery.

Quick Start

Input a vague request such as "build an app" and obtain a detailed plan outlining tasks, dependencies, roles, and validation criteria.

Frequently Asked Questions about default-planner

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

FAQPage Schema
How do I turn vague project requests into actionable task plans?

Task planning for vague requests involves analyzing cross-domain needs to produce structured, executable task sequences. This Skill converts ambiguous requirements into ordered tasks with dependencies, inputs, and validation criteria for reliable delivery.

What is the best way to plan multi-domain orchestration across frontend, backend, and infrastructure?

Multi-domain orchestration requires architecture-aware routing to define task order and dependencies. This Skill analyzes requests spanning frontend, backend, and infrastructure to generate end-to-end task sequences guided by architectural best practices.

Can I generate validation criteria and success metrics for cross-domain development tasks?

Yes, generating validation-ready outputs is built into the task planning process. Each task produced includes structured acceptance criteria, inputs, and success metrics to ensure reliable delivery across multi-domain projects.

How does task sequencing work for ambiguous cross-domain development work?

Task sequencing for ambiguous work uses skill discovery and batch task creation to define executable order. This Skill implements search_skills to find relevant capabilities and create_tasks_batch to define structured dependencies for each task.

Do I need existing architecture documentation to use automated task planning?

No, you do not need existing architecture documentation to use automated task planning. You can input a vague request such as "build an app" and obtain a detailed plan outlining tasks, dependencies, roles, and validation criteria.