writing-plan

Generate a structured Markdown implementation plan saved to ./plan/<plan-name>.md.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/andrelucassvt/verify_local_purchase --skill writing-plan-andrelucassvt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plan
Source: https://github.com/andrelucassvt/verify_local_purchase/tree/main/.agents/skills/writing-plan
Command: npx skills add https://github.com/andrelucassvt/verify_local_purchase --skill writing-plan-andrelucassvt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a structured Markdown implementation plan and saves it to the plan folder, enabling teams to capture multi-step approaches as repeatable documents.

Core Features & Use Cases

  • Plan generation: Creates a Markdown plan with a clear objective, phased steps, checklists, and success criteria.
  • Reuse and sharing: Produces a shareable, reusable plan doc that can be revisited and updated.
  • Flexible scope: Works for features, refactors, bugs, or research tasks, and saves to ./plan/<plan-name>.md.

Quick Start

Ask the AI to generate a complete plan document for the described feature or task and save it to ./plan/<plan-name>.md.

Frequently Asked Questions about writing-plan

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

FAQPage Schema
How do I generate a structured plan document in Markdown for a new software feature?

Generating a Markdown plan document involves providing the feature details to the AI, which produces a file with objectives, phased actionable steps, and success criteria, saving it to ./plan/<plan-name>.md.

What should be included in a software engineering implementation plan?

An implementation plan should include an objective, context, architecture scope, phases with actionable steps, and success criteria to guide future development and ensure structured execution.

Can I save and reuse Markdown plan documents for software refactoring tasks?

Yes, you can save and reuse the generated Markdown plan documents. They are stored locally under ./plan/<plan-name>.md, capturing multi-step refactoring approaches as repeatable, shareable documents.

Does this planning workflow support bug fixes and research tasks or only new features?

This planning workflow supports flexible scopes, working for features, refactors, bugs, or research tasks. It generates a structured Markdown plan saved locally to guide any software engineering objective.

What is the best way to create a shareable plan document with checklists and success criteria?

The best way to create a shareable plan document is to generate a Markdown file with phased steps, checklists, and success criteria. This produces a reusable plan stored under ./plan/<plan-name>.md.