planera

Create structured PLAN.md files with tasks, constraints, and acceptance criteria.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/jgabor/agentera --skill planera
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planera
Source: https://github.com/jgabor/agentera/tree/main/skills/planera
Command: npx skills add https://github.com/jgabor/agentera --skill planera

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning large, multi-module work requires explicit structure and guardrails to avoid scope creep and miscommunication.

Core Features & Use Cases

  • Structured WHAT/WHY planning with acceptance criteria.
  • Task decomposition into implementable cycles.
  • Freshness checkpoint for plan progress and artifact updates.

Quick Start

Create a PLAN.md that outlines WHAT, WHY, constraints, scope, design, tasks, and a freshness checkpoint for the next multi-cycle feature.

Frequently Asked Questions about planera

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

FAQPage Schema
How do I plan complex multi-module work to avoid scope creep?

Planning complex multi-module work requires a structured PLAN.md with explicit WHAT/WHY, constraints, scope, design, tasks, and freshness checkpoints. This approach enforces artifact contracts, task dependencies, and standard planning templates to ensure reproducible, auditable plans.

What is task decomposition with acceptance criteria in project management?

Task decomposition with acceptance criteria breaks large multi-module features into implementable cycles. It defines explicit artifact contracts and standard planning templates to ensure work is reproducible and auditable before actual implementation begins.

How do I create a structured PLAN.md for project planning?

Create a PLAN.md outlining WHAT, WHY, constraints, scope, design, tasks, and a freshness checkpoint. Use standard planning templates defined in references to enforce artifact contracts and task dependencies for multi-cycle features.

When do I need explicit acceptance criteria before implementation begins?

Explicit acceptance criteria are needed when work spans multiple modules, requires task decomposition, and benefits from structured planning templates. This prevents miscommunication and scope creep by enforcing artifact contracts before implementation.

What is the best way to manage task dependencies in multi-cycle features?

Managing task dependencies in multi-cycle features requires standard planning templates that enforce artifact contracts. A structured PLAN.md with explicit WHAT/WHY, scope, design, and tasks ensures reproducible, auditable plans across modules.

Do I need prior planning templates to decompose tasks into implementable cycles?

Prior planning templates are not required but standard templates defined in references are applied during the planning process. The Skill enforces artifact contracts and task dependencies automatically to ensure reproducible, auditable plans.