metaplan

Convert planning artifacts into execution-ready guidance for autonomous coding agents.

1|Updated Apr 13, 2026

Search Tags:#planning #requirements #acceptance-criteria #autonomous-coding #spec-review #execution-ready

Ready to run

npx skills add https://github.com/t-uda/skills --skill metaplan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: metaplan
Source: https://github.com/t-uda/skills/tree/main/skills/metaplan
Command: npx skills add https://github.com/t-uda/skills --skill metaplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review planning artifacts to convert abstract specs, plans, and task breakdowns into an execution-ready package that an autonomous coding agent can run with minimal clarification.

Core Features & Use Cases

Harden specs, plans, and task lists to remove ambiguity before implementation.
Ensure explicit boundaries, dependencies, stop conditions, and acceptance criteria for autonomous execution.
Use case: given a planning brief and task list, produce a ready-to-run execution plan that an agent can follow with minimal supervision.

Quick Start

Provide the planning artifacts to be reviewed and I will produce an execution-ready package with explicit boundaries and criteria.

Frequently Asked Questions about metaplan

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

FAQPage Schema

How do I prepare specs and task lists for autonomous coding agents?▼

Spec review for autonomous coding involves transforming planning artifacts into execution-ready guidance with explicit boundaries, dependencies, and acceptance criteria. This ensures autonomous coding agents receive unambiguous direction and guardrails to execute tasks with minimal supervision.

What is an execution-ready plan for autonomous code execution?▼

An execution-ready plan is a hardened planning artifact containing explicit stop conditions, decision logs, and acceptance criteria. It provides autonomous coding agents with unambiguous direction and guardrails to execute implementation tasks with minimal clarification.

How do I stop scope drift when running autonomous coding tasks?▼

You stop scope drift in autonomous coding tasks by enforcing explicit boundaries and stop conditions within planning artifacts. Reviewing specs to establish decision logs and acceptance criteria prevents rework by keeping the agent within defined guardrails.

Why does my autonomous coding agent keep asking for clarification during implementation?▼

Your autonomous coding agent requests clarification because planning artifacts lack explicit acceptance criteria and boundaries. Hardening specs, task lists, and implementation briefs before coding removes ambiguity and produces execution-ready guidance requiring minimal supervision.

Can I use spec review to add guardrails for autonomous coding across different software projects?▼

Yes, spec review applies to reviewing specs, task lists, and implementation briefs across software projects to ensure unambiguous direction. It enforces explicit boundaries, dependencies, and decision logs to prevent rework and drift in any autonomous coding workflow.

What are the limitations of using planning artifacts for autonomous code execution?▼

Planning artifacts for autonomous code execution require pre-existing specs, plans, or task breakdowns to function effectively. Without initial planning briefs to review and harden, the process cannot produce execution-ready guidance or enforce boundaries and acceptance criteria.