plan

Writes actionable markdown implementation plans with bite-sized tasks to .voiceos/plans/ without executing code.

5|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AjayRajan05/VoiceOS --skill plan-ajayrajan05
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/AjayRajan05/VoiceOS/tree/main/skills/bundled/community/software-development/plan
Command: npx skills add https://github.com/AjayRajan05/VoiceOS --skill plan-ajayrajan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding a multi-step feature often leads to missed requirements, vague tasks, and rework. This Skill enforces a plan-only mode that produces a concrete, step-by-step implementation plan before any code is written. ## Core Features & Use Cases - Plan-Only Mode: Guarantees no code edits, commits, or mutating commands during the planning turn; only read-only inspection is allowed. - Structured Plan Documents: Generates plans with exact file paths, complete copy-pasteable code, TDD steps, verification commands, and frequent commits, saved to .voiceos/plans/ with a timestamped filename. - Execution Handoff: Connects the finished plan to subagent-driven-development for task-by-task implementation with two-stage review. - Use Case: Before building a new authentication feature, invoke plan mode to get a markdown plan breaking the work into 2-5 minute tasks with failing tests, minimal implementations, and commit steps. ## Quick Start Ask the assistant to enter plan mode and write an implementation plan for your feature, saved under .voiceos/plans/.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I write an implementation plan before coding a feature?▼

Invoke plan mode and describe the feature or let it infer the task from conversation context. It inspects the codebase read-only, then saves a markdown plan under .voiceos/plans/ with bite-sized tasks, exact file paths, complete code, and verification steps.

What should a good software implementation plan include?▼

A good plan includes a goal, architecture summary, tech stack, and sequential tasks of 2-5 minutes each. Every task lists exact files to create or modify, failing tests, minimal implementations, run commands with expected output, and a commit step.

Does plan mode modify or execute any code in my project?▼

No. Plan mode forbids editing project files, running mutating commands, committing, or pushing. It only permits read-only inspection and writes a single markdown plan file under .voiceos/plans/.

Where are plan files saved and how are they named?▼

Plans are saved with write_file under .voiceos/plans/ relative to the active workspace, using a timestamped filename like YYYY-MM-DD_HHMMSS-slug.md. If the runtime provides a specific target path, that exact path is used instead.

When should I not use plan mode?▼

Skip plan mode for trivial single-step changes where planning overhead exceeds the work. It is designed for multi-step features, complex requirements, and tasks delegated to subagents where assumptions cause bugs.

How do I execute a plan after it is written?▼

After saving, the plan offers handoff to the subagent-driven-development skill. That workflow dispatches a fresh subagent per task with spec compliance review followed by code quality review before proceeding.