plan

Generate a deterministic markdown plan and save it to .xerxes/plans/.

27|2|Updated Jan 15, 2024
One-click install
npx skills add https://github.com/erfanzar/Xerxes-Agents --skill plan-erfanzar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/erfanzar/Xerxes-Agents/tree/main/src/python/xerxes/skills/plan
Command: npx skills add https://github.com/erfanzar/Xerxes-Agents --skill plan-erfanzar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode provides a safe, deterministic way to outline steps and expected changes without mutating the workspace or executing code.

Core Features & Use Cases

  • Inspect the active context and constraints
  • Write a markdown plan into the active workspace at .xerxes/plans/
  • Save, timestamp, and version plans for review and audit

Quick Start

Describe the task in a concrete markdown plan and save it to .xerxes/plans/.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a markdown plan without executing code in my workspace?

To generate a markdown plan without executing code, describe your task and the system will output a deterministic, non-executing plan. It saves the plan directly into your workspace at .xerxes/plans/ for safe review.

What is the best way to outline project steps without mutating files?

The best way to outline project steps without mutating files is to use a deferral mechanism that inspects context and generates a timestamped markdown plan. This approach ensures your workspace remains unchanged during the assessment phase.

Can I save and timestamp planning documents automatically in a project workspace?

Yes, you can save and timestamp planning documents automatically. The system writes your markdown plan into the active workspace at .xerxes/plans/ using a timestamped filename, ensuring every plan is versioned for audit.

Does plan generation require any external dependencies or specific components?

No, plan generation requires no external dependencies or specific components. It operates independently to inspect active context and write markdown plans into the .xerxes/plans/ directory.

When should I use a non-executing plan instead of running tasks directly?

You should use a non-executing plan when you need to safely assess context, outline expected changes, or defer execution across projects. It provides a deterministic markdown document for review without risking workspace mutations.