plan

Coordinate planning and approval workflows before coding.

645|73|Updated Mar 24, 2025
One-click install
npx skills add https://github.com/truffle-ai/dexto --skill plan-truffle-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/truffle-ai/dexto/tree/main/packages/tools-plan/skills/plan
Command: npx skills add https://github.com/truffle-ai/dexto --skill plan-truffle-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and coordinating pre-implementation work to prevent scope creep and wasted effort.

Core Features & Use Cases

  • Structured research: Use the explore agent to understand the codebase and context.
  • Plan lifecycle: Create, read, update, and review plans with explicit approval steps.
  • Controlled implementation: WAIT for user approval before coding or changing code.

Quick Start

Research the codebase with the explore agent, check for an existing plan with plan_read, then create a comprehensive plan with plan_create and request approval using plan_review.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I prevent scope creep when planning software changes?

Prevent scope creep by enforcing a structured planning workflow that requires explicit approval before coding. You can coordinate research, plan creation, and reviews to ensure implementation only begins after final approval.

What is the workflow for coordinating approvals before implementation?

The workflow for coordinating approvals involves researching the codebase, checking existing plans, creating a comprehensive plan, and requesting a review. It enforces a mandatory wait-for-approval step before any coding or architecture updates begin.

How to create a comprehensive plan for feature initiatives?

Create a comprehensive plan for feature initiatives by first using an explore agent to research the codebase and context. Then use plan_create to document the proposal and plan_review to request explicit user approval before implementation.

Can I update an existing plan before requesting approval?

Yes, you can update an existing plan before requesting approval using the plan_update action. After reading the current plan with plan_read and making necessary modifications, you must still use plan_review to wait for explicit user approval before coding.

When should I not use a mandatory planning workflow?

You should not use a mandatory planning workflow for trivial changes that do not require scope creep prevention or multi-step coordination. It is designed for preparing software changes, architecture updates, and feature initiatives that need explicit approval gates.