writing-plans

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, step-by-step implementation plans for engineers, ensuring clarity and reducing ambiguity even with minimal codebase context.

Core Features & Use Cases

  • Comprehensive Task Breakdown: Generates bite-sized tasks, each with specific file paths, code examples, and verification steps.
  • Context-Aware Planning: Assumes engineers have limited domain knowledge but are skilled developers.
  • Use Case: When a new feature is designed, this Skill can produce a complete roadmap for its implementation, including all necessary code modifications and testing procedures, ready for an engineer to execute.

Quick Start

Use the writing-plans skill to generate an implementation plan for the new user authentication feature.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan with zero codebase context?

You can generate an implementation plan with zero codebase context by producing bite-sized tasks that include exact file paths, code snippets, and verification steps. This approach assumes limited domain knowledge but strong engineering skills.

What is task breakdown in software development planning?

Task breakdown in software development planning is dividing a feature into bite-sized, actionable steps. Each step provides specific file paths, code examples, and verification procedures to ensure comprehensive documentation for engineers.

How to write implementation plans that promote TDD and frequent commits?

Implementation plans that promote TDD and frequent commits are generated by structuring each task with exact code modifications and testing procedures. This ensures engineers execute changes in small, verifiable increments with comprehensive documentation.

Can I use automated planning for engineers with minimal domain knowledge?

Automated planning for engineers with minimal domain knowledge is possible by generating context-aware roadmaps. These plans provide exact file paths, code snippets, and verification steps, ensuring clarity and reducing ambiguity for skilled developers.

What's the best way to document a new feature roadmap for implementation?

The best way to document a new feature roadmap for implementation is generating a complete plan with exact file paths, code modifications, and testing procedures. This creates a ready-to-execute roadmap promoting TDD and frequent commits.

Does implementation planning work without existing codebase documentation?

Implementation planning works without existing codebase documentation by generating actionable plans with zero context. It provides exact file paths, code snippets, and verification steps for each task, ensuring clarity even with minimal domain knowledge.