writing-plans

Convert a spec or requirements document into a timestamped Markdown implementation plan.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kitfunso/omniskill --skill writing-plans-kitfunso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/kitfunso/omniskill/tree/main/skills/writing-plans
Command: npx skills add https://github.com/kitfunso/omniskill --skill writing-plans-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a spec or requirements document into a concrete, end-to-end implementation plan that engineers can execute, ensuring alignment and reproducibility.

Core Features & Use Cases

  • Generates a complete, task-by-task implementation plan with clearly defined steps, tests, and commit notes.
  • Saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md, providing a consistent, auditable record.
  • Supports varying scopes from small enhancements to large features and includes edge-case considerations.

Quick Start

Provide a clear spec and ask me to generate a full implementation plan saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a spec or requirements document into an implementation plan?

To turn a spec into an implementation plan, provide the requirements document to generate a concrete, multi-step plan. The output includes an execution plan, task list, testing steps, and commit notes.

How do I generate a task list with testing steps from a feature spec?

You can generate a task list with testing steps by processing your feature spec. The system creates a complete, task-by-task implementation plan that includes clearly defined steps, tests, and commit notes.

Does the generated implementation plan include commit notes for version control?

Yes, the generated implementation plan includes commit notes for version control. It provides a complete, task-by-task execution plan with clearly defined steps and tests to ensure alignment and reproducibility.

What is the best way to save an end-to-end implementation plan for a new feature?

The best way to save an implementation plan is to output it as a timestamped Markdown file. The plan is saved under docs/plans in a file named YYYY-MM-DD-<feature-name>.md, providing a consistent, auditable record.

Can I use this spec-to-plan approach for both small enhancements and large features?

Yes, you can use this spec-to-plan approach for varying scopes from small enhancements to large features. The generated implementation plans also include edge-case considerations to support different project sizes.