writing-plans

Generate engineering implementation plans with file paths, code samples, and verification steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate comprehensive implementation plans for engineering tasks, enabling teams to begin work with zero context by providing exact file paths, code examples, and verification steps.

Core Features & Use Cases

  • Generate end-to-end task breakdowns for features with precise file paths and concrete code examples.
  • Produce bite-sized tasks suitable for incremental development and frequent commits.
  • Save plans to a versioned docs path (docs/plans/YYYY-MM-DD-<feature-name>.md) for traceability.

Quick Start

Create the initial implementation plan for the feature and save it 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 create implementation plans for engineering tasks in an unfamiliar codebase?

Implementation plans for unfamiliar codebases are generated with exact file paths, complete code samples, and verification steps. This provides the full context needed to start feature development or refactoring immediately without prior codebase knowledge.

What is the best way to structure implementation plans for incremental development?

Structuring implementation plans involves producing bite-sized tasks suitable for incremental development and frequent commits. Plans are broken down into step-by-step instructions with concrete code examples to ensure smooth, traceable workflows.

How does generating an implementation plan help engineers with zero codebase context?

Generating an implementation plan helps zero-context engineers by providing exact file paths and complete code samples. This removes the need for prior codebase exploration, allowing teams to begin work immediately and accurately.

Do I need a dedicated worktree to generate task breakdowns for feature refactoring?

Yes, a dedicated worktree is required to generate task breakdowns for feature refactoring. The workflow strictly formats and stores plans in versioned markdown paths like docs/plans/YYYY-MM-DD-feature-name.md for traceability.

Where are generated implementation plan documents saved for version control traceability?

Generated implementation plan documents are saved to a versioned path at docs/plans/YYYY-MM-DD-feature-name.md. This ensures all task breakdowns and code samples remain traceable within the project's documentation structure.

What limitations exist when formatting implementation plans for complex engineering workflows?

Limitations include the requirement for a dedicated worktree and strict plan formatting. Plans must be stored at specific docs/plans/ paths, meaning deviations from this structure are not supported by the workflow.