skills.rest
Gitnapp
GitnappCOMMUNITY
Explore all skills by this author →
GitHub

plan

Create structured markdown implementation plans for software change requests.

Updated Feb 21, 2026
Search Tags:#workflow#planning#markdown#software development#implementation#repository
One-click install
npx skills add https://github.com/Gitnapp/Skills --skill plan-gitnapp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Gitnapp/Skills/tree/main/software-development/plan
Command: npx skills add https://github.com/Gitnapp/Skills --skill plan-gitnapp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users convert development requests into structured implementation plans while preventing unintended code changes or execution during planning.

Core Features & Use Cases

  • Planning Workflow: Creates detailed markdown plans with goals, context, approaches, file changes, tests, risks, and open questions.
  • Safe Plan-Only Mode: Restricts the workflow to read-only inspection and plan creation without implementing changes or running mutating actions.
  • Use Case: A developer preparing a feature change can use this Skill to generate a concrete roadmap before writing code.

Quick Start

Use the plan skill to create an implementation plan for the requested software change and save it in the workspace plans directory.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an implementation plan for software development without writing code?▼

Implementation plans are generated as structured markdown files documenting goals, approaches, file changes, and risks, using read-only analysis to prevent unintended code execution during the planning phase.

What is the best way to plan code changes for a repository before execution?▼

Repository planning workflows convert development requests into concrete roadmaps, performing read-only inspection to map out file changes, tests, and validation considerations without applying the modifications.

Can I generate a markdown plan for a feature request without mutating my workspace?▼

Yes, a safe plan-only mode restricts the workflow to read-only inspection, generating markdown plans with workspace-relative storage while preventing any code changes or mutating actions.

What should an implementation plan include for a software development workflow?▼

An implementation plan should include goals, context, approaches, file changes, tests, risks, and open questions to provide a concrete roadmap before writing code.

Does the plan skill require any dependencies to analyze repository changes?▼

No dependencies are required; the workflow analyzes repository changes using read-only inspection and saves the generated markdown plans directly in the workspace plans directory.

When should I use a planning workflow instead of directly implementing code?▼

Use a planning workflow when preparing a feature change requires a documented roadmap of risks, file changes, and validation considerations before any code is written or executed.

Related Skills

Explore More Software Engineering Skills→
johnlindquistjohnlindquist
24

repo

Generate repository context bundles and code maps for a codebase.

Community
Intermediate
afel6afel6

writing-plans

Generate task-level implementation plans with file paths, tests, and verification steps.

Community
Advanced
ThiagoVitaleThiagoVitale

gsd-complete-milestone

Archive completed milestones and update project documentation for the next version.

Community
Advanced
afel6afel6

plan

Generate timestamped Markdown implementation plans without modifying repository files.

Community
Intermediate