plan

Generate timestamped Markdown plans with task breakdowns under .kilo/plans/.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill plan-vtgiang-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/plan
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill plan-vtgiang-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps planners produce concrete, trackable plans instead of immediate code execution, keeping work organized and auditable.

Core Features & Use Cases

  • Plan-mode isolation: writes a markdown plan document under .kilo/plans/ with timestamped filename.
  • Task breakdown: translates goals into bite-sized steps with clear success criteria.
  • Non-destructive: does not modify repository files beyond plan generation.

Quick Start

Save a concrete markdown plan under .kilo/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 markdown project plan without modifying my codebase?

Generate a markdown project plan by running plan mode, which creates a timestamped plan file under .kilo/plans/ without modifying any existing repository files or executing code.

Can I break down project goals into actionable task steps with success criteria?

Yes, you can break down project goals into actionable task steps with measurable milestones and clear success criteria, translating broad objectives into bite-sized structured roadmaps.

Does plan mode require any external dependencies to create task breakdowns?

No, plan mode requires no external dependencies beyond the skill tool itself to generate trackable task breakdowns and structured roadmaps for solo developers and teams.

What is the best way to create non-destructive workflow planning documents?

The best way to create non-destructive workflow planning documents is using plan mode, which writes concrete markdown plans to an isolated directory while keeping repository files untouched.

Where are generated markdown plans saved when using this planning tool?

Generated markdown plans are saved as timestamped files under the .kilo/plans/ directory, ensuring work remains organized, trackable, and auditable without altering source code.

When should I not use automated plan generation for project management?

You should not use automated plan generation when you need immediate code execution or file modifications, as this planning tool strictly outputs markdown documents without performing task execution.