plan

Write a concrete markdown plan without executing code.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matlee0409/cronus --skill plan-matlee0409
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/matlee0409/cronus/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/matlee0409/cronus --skill plan-matlee0409

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables users to generate a detailed, executable-free plan for any task, ensuring alignment before implementation.

Core Features & Use Cases

  • Non-executable planning: Produces a concrete plan without writing or mutating code.
  • Structured output: Saves the plan as a markdown file under .cronus/plans/ with a timestamped filename.
  • Reproducible documentation: Keeps plans organized and traceable across sessions.

Quick Start

Generate a concrete plan for the requested task and save it as a markdown file under .cronus/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 a structured markdown plan without executing any code?

To generate a structured markdown plan without executing code, this Skill analyzes your task and writes a concrete, non-mutating plan. It saves the output directly as a timestamped markdown file under .cronus/plans/ for review.

What is plan mode for software development and research workflows?

Plan mode is a documentation-first approach that outlines steps to complete a task before implementation begins. It produces a structured markdown file to ensure human alignment and traceability across sessions without mutating code.

Where are markdown planning documents saved in the workspace?

Markdown planning documents are saved in the .cronus/plans/ directory within your workspace. Each file is named with a timestamp and slug format (YYYY-MM-DD_HHMMSS-slug.md) for reproducible documentation.

Can I create non-executing task plans for operations and software engineering?

Yes, you can create non-executing task plans for operations, software engineering, and research. The Skill documents the approach for any workflow needing a structured plan before implementation, enforcing strictly non-mutating behavior.

Does this planning workflow enforce non-mutating behavior on existing files?

Yes, this planning workflow enforces strictly non-mutating behavior on existing files. It focuses entirely on generating actionable documentation and will not write, alter, or execute any code during the planning phase.