skills.rest
hugo-berendi
hugo-berendiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate detailed implementation plans with tasks, tests, and commit commands.

3|Updated May 31, 2024
Search Tags:#planning#documentation#implementation#software-development#task-management#planning-docs
One-click install
npx skills add https://github.com/hugo-berendi/yomi --skill writing-plans-hugo-berendi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/hugo-berendi/yomi/tree/main/.opencode/skills/writing-plans
Command: npx skills add https://github.com/hugo-berendi/yomi --skill writing-plans-hugo-berendi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate comprehensive, implementation-level plans for complex tasks before starting code, ensuring clear scope, steps, and testing criteria.

Core Features & Use Cases

  • Plan generation: Create bite-sized tasks, with file touchpoints, tests, docs, and commits.
  • Consistent plan structure: Provides a standard header and a repeatable layout for every feature.
  • Use Case: When a product spec exists but code is not yet written, run this skill to produce a plan that guides engineers through tasks and verification.

Quick Start

Use the writing-plans skill to draft an implementation plan for the new feature, saving it to docs/plans/YYYY-MM-DD-<feature-name>.md and outlining steps for tests, code changes, and docs.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I draft a step-by-step implementation plan for software development?▼

Generate a step-by-step implementation plan by processing an existing product spec into a standardized document featuring task-oriented steps, testing criteria, and commit-ready commands.

What is an implementation plan document and when do I need one?▼

An implementation plan document defines clear scope, tasks, and testing criteria for complex features. You need one when a product spec exists but code is not yet written.

Can I generate implementation plans for tasks without existing product specs?▼

No, generating detailed implementation plans requires an existing product spec as input. The tool processes specifications to produce structured engineering tasks and verification steps.

What's the best way to structure feature plans for engineering teams?▼

Structure feature plans using a standardized header and repeatable layout that breaks complex features into bite-sized tasks, file touchpoints, tests, and commit-ready commands for engineering teams.

How do I create a plan file with tests and commit commands for a new feature?▼

Create a plan file by generating a markdown document saved to docs/plans/YYYY-MM-DD-<feature-name>.md that systematically outlines required steps for tests, code changes, and documentation.

Related Skills

Explore More Content & Communication Skills→
lionbenjaminlionbenjamin
15

specify

Draft product specifications with problem, goals, user stories, and acceptance criteria.

Community
Intermediate
mappa-aimappa-ai
1

do-work

Plan, implement, validate with typecheck and tests, and commit code changes.

Official
Advanced
caitengweicaitengwei
6

writing-plans

Convert feature specifications into test-driven implementation plans with file paths and execution steps.

Community
Intermediate
Jia-Hong-PengJia-Hong-Peng

speckit-plan

Generate structured implementation plans from spec.md files using spec-kit workflows.

Community
Intermediate