plan

Generate a reviewable execution plan with options and validation steps.

3|Updated Mar 7, 2020
One-click install
npx skills add https://github.com/qsdrqs/dotfiles --skill plan-qsdrqs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/qsdrqs/dotfiles/tree/main/opencode/skills/plan
Command: npx skills add https://github.com/qsdrqs/dotfiles --skill plan-qsdrqs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan Mode helps users produce a clear, reviewable execution plan before taking any action that changes code, files, or external state, reducing risk and misalignment.

Core Features & Use Cases

  • Plan-only workflow: generate a structured plan with goals, constraints, options, and validation steps before execution.
  • Risk and decision handling: surface unknowns, trade-offs, and success criteria to support informed decisions.
  • Approval gate: requires explicit user approval (ACT / start executing) before acting on plans.

Quick Start

Provide a plan outline for a user-specified task and await approval.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate an execution plan before making changes to code or files?

To generate an execution plan, you provide a task outline and the system produces a structured plan with goals, constraints, options, and validation steps before any code changes occur. It enforces a plan-only workflow to reduce risk and misalignment.

What is the best way to handle risks and trade-offs when creating a project roadmap?

Handling risks during roadmap planning involves surfacing unknowns, trade-offs, and success criteria to support informed decisions. The plan presents multiple options and includes a checklist for validation and rollback to manage risk effectively.

Can I require manual approval before a proposal starts executing?

Yes, you can require manual approval before execution by using an approval gate. The system waits for explicit user approval, such as an ACT command, before acting on any generated proposals or plans to ensure safe execution.

How does a plan-only workflow handle missing information for a proposal?

A plan-only workflow handles missing information by asking questions when details are insufficient. Instead of guessing, it pauses to request the missing data needed to present multiple options with accurate trade-offs and validation steps.

What are the limitations of enforcing a plan-only workflow?

The limitation of a plan-only workflow is that it strictly enforces no execution during the planning phase, meaning no code, files, or external state changes occur until the user explicitly provides approval to start executing.