planejamento-diario

Create daily markdown plans, task briefs, and audit indexes for agent teams.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill planejamento-diario
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planejamento-diario
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/skills/operacao/planejamento-diario
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill planejamento-diario

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It solves the loss of context, duplicated work, and weak auditability that happen when multiple AI agents operate without a shared daily operating system.

Core Features & Use Cases

  • Daily planning workflow: Creates a structured plan with waves, priorities, dependencies, and per-task files for each day.
  • Approval and delegation controls: Separates planning from delegation, requiring explicit authorization before tasks are sent out.
  • Execution and audit trail: Tracks task completion, commit hashes, checkboxes, and audit status in PLANO.md and INDICE.md.
  • Operational safeguards: Enforces engine hierarchy, thread discipline, update timing, and correction rules for production use.
  • Use Case: A team lead asks for the day’s plan, reviews the generated markdown files, delegates approved tasks to agents, and later audits results into a consolidated report.

Quick Start

Ask the assistant to create today’s planning directory, generate the daily plan and task files, and prepare the index for a multi-agent workday.

Frequently Asked Questions about planejamento-diario

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

FAQPage Schema
How do I coordinate daily planning across multiple AI agents to prevent duplicated work?

Daily planning across multiple AI agents is coordinated by orchestrating a structured loop that generates shared markdown plans, task briefs, and audit indexes. This enforces strict file generation, approval gating, and synchronized updates to prevent duplicated work.

What's the best way to maintain an audit trail for task delegation in a multi-agent workflow?

Maintaining an audit trail for task delegation requires tracking task completion, commit hashes, and checkboxes within consolidated markdown files. The workflow separates planning from delegation, requiring explicit authorization before tasks are sent to agents.

How does approval gating work in markdown-based task delegation?

Approval gating in markdown-based task delegation works by separating the planning phase from the execution phase. Team leads review the generated daily plan files and must provide explicit authorization before any tasks are delegated to the agent team.

Can I track execution and commit traceability using markdown files for production planning?

You can track execution and commit traceability using markdown files by recording task completion, commit hashes, and audit status in dedicated index files. This enforces engine hierarchy, thread discipline, and correction rules for production use.

Do I need any external dependencies to run a multi-agent daily planning workflow with audit indexes?

No external dependencies are required to run a multi-agent daily planning workflow with audit indexes. The system operates independently using internal scripts and references to generate structured markdown plans and track task completion.