writing-plans

Generate end-to-end implementation plans from product specs with frontmatter metadata.

2|1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lagz0ne/prev-cli --skill writing-plans-lagz0ne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/lagz0ne/prev-cli/tree/main/.opencode/skill/writing-plans
Command: npx skills add https://github.com/lagz0ne/prev-cli --skill writing-plans-lagz0ne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams convert vague requirements into a concrete, executable plan that can guide code, tests, docs, and reviews, reducing back-and-forth and missed steps.

Core Features & Use Cases

  • End-to-end planning: generate a complete, task-by-task plan suitable for implementation, testing, and documentation.
  • DRY and TDD oriented: encourages reusable plan patterns and test-first thinking to minimize churn.
  • Plan repository: saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md for versioned traceability and audit trails.

Quick Start

Use the writing-plans skill to generate an implementation plan from a given spec and save it to docs/plans/YYYY-MM-DD-welcome.md

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an actionable implementation plan from a product spec?

An implementation plan converts vague requirements into a concrete, executable roadmap that guides code, tests, and reviews. It ensures clear task breakdowns before coding to reduce back-and-forth and missed steps.

What is the best way to break down multi-step software engineering tasks?

The best way to break down multi-step software tasks is applying DRY, YAGNI, and test-driven development principles. This approach encourages reusable patterns and test-first thinking to minimize churn during implementation.

How does test-driven development integrate into implementation planning?

Test-driven development integrates into implementation planning by encouraging test-first thinking and reusable plan patterns. This minimizes code churn and ensures the final plan covers testing alongside feature implementation.

Where should generated implementation plans be saved for versioned traceability?

Generated implementation plans should be saved to docs/plans/YYYY-MM-DD-<feature-name>.md. This file path structure ensures versioned traceability and creates a reliable audit trail for engineering teams.

Can I use standardized headers and metadata for plan documents across different features?

Yes, you can use standardized headers and metadata for plan documents across different features. This ensures frontmatter metadata with name and description, maintaining consistent documentation standards for implementation plans.