plan

Generate a timestamped Markdown plan in .io/plans/ without modifying files.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ever-oli/io --skill plan-ever-oli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ever-oli/io/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/ever-oli/io --skill plan-ever-oli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams avoid premature execution by generating a concrete, actionable plan for a given task and saving it as a Markdown document for review and approval.

Core Features & Use Cases

  • Plan generation: Produces a structured, step-by-step plan outlining goals, tasks, owners, and validation criteria.
  • Non-execution guarantee: Ensures no code changes or mutations are performed during planning.
  • Save & traceability: Outputs the plan to the active workspace under .io/plans/ with a timestamped filename for auditability.

Quick Start

Generate a concrete Markdown plan and save it to the active workspace under .io/plans/ with a timestamped filename.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate an actionable task plan in Markdown without modifying my codebase?

To generate an actionable task plan without modifying your codebase, use a non-mutating planning mode that creates a step-by-step Markdown document and saves it directly to your workspace. This enforces a non-execution guarantee, ensuring no repository files are edited or commands run during planning.

What is plan-first execution and when do I need it for software engineering tasks?

Plan-first execution is the process of producing a concrete, actionable plan for a given task before writing any code. You need it when teams must avoid premature execution, allowing a structured Markdown document outlining goals, tasks, and validation criteria to be reviewed and approved first.

Can I save generated Markdown plans to a specific workspace directory for traceability?

Yes, you can save generated Markdown plans to a specific workspace directory for traceability. The planning process outputs timestamped Markdown files directly into the .io/plans/ folder, ensuring every generated plan is auditable and properly archived within the active workspace.

Does plan mode execution guarantee that no commands will run or files will be edited?

Plan mode execution guarantees non-mutating behavior by strictly writing the generated plan to the specified location without editing repository files or running commands. This ensures your workspace remains completely unchanged during the task planning phase.

What is the best way to outline task owners and validation criteria before implementation?

The best way to outline task owners and validation criteria before implementation is to generate a structured Markdown plan. This approach produces a detailed document outlining goals, specific tasks, owners, and validation criteria, providing a clear roadmap for subsequent execution.