Verified:GitHub

plan

Generate a timestamped markdown execution plan under .gengar/plans/ without modifying the repository.

Updated May 4, 2026

Search Tags:#workflow #planning #software development #markdown output #workspace files #implementation guardrails #tests validation

Ready to run

npx skills add https://github.com/JamesFincher/gengar --skill plan-jamesfincher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/JamesFincher/gengar/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/JamesFincher/gengar --skill plan-jamesfincher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert an ambiguous or code-heavy task into a clear, step-by-step execution plan without actually implementing or modifying the project during the planning phase.

Core Features & Use Cases

Plan-only workflow: Produces a markdown plan while preventing implementation and any mutating actions.
Actionable, file-aware output: Encourages concrete steps, likely file changes, tests/validation, and risks/open questions for code-related tasks.
Workspace persistence: Saves the plan into .gengar/plans/ with a timestamped filename so it can be reviewed and reused later.

Quick Start

Use plan mode to generate a concrete markdown execution plan for your requested change and save it under .gengar/plans/.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I create a software development plan without modifying my repository?▼

To create a software development plan without modifying your repository, use a planning workflow that generates a markdown execution plan detailing goals, assumptions, approaches, and validation steps while prohibiting code edits or commits.

What is a markdown execution plan for software engineering tasks?▼

A markdown execution plan for software engineering tasks is a structured document outlining concrete next steps, likely file touchpoints, and test validation procedures, generated without performing actual implementation work.

How do I generate actionable implementation guardrails for a new feature?▼

You generate actionable implementation guardrails for a new feature by producing a structured plan that defines the approach, file touchpoints, and validation steps, ensuring no mutating terminal commands or external actions occur during planning.

Can I save a project planning workflow file to my workspace for later review?▼

Yes, you can save a project planning workflow file to your workspace. The plan is persisted as a timestamped markdown file under the .gengar/plans/ directory so it can be reviewed and reused later.

Does the planning workflow support tests validation for code-related tasks?▼

Yes, the planning workflow supports tests validation for code-related tasks by explicitly including validation steps and identifying risks or open questions within the generated markdown plan.

What are the limitations of plan-mode constraints for software development?▼

The limitations of plan-mode constraints for software development include prohibiting code edits, mutating terminal commands, repository commits, or external actions, strictly limiting the output to generating a markdown plan file.